docs: apply v0.2 writing style to v0.1 Added chapters in CHANGELOG.md

[Copilot]

The v0.1 ### Added chapters in CHANGELOG.md were not updated when prior PRs (#40–#43) applied the v0.2 writing style to the v0.1 Security/Changed/Removed sections.

Changes

• All 10 v0.1 ### Added chapters rewritten with long descriptive, formulated sentences matching the v0.2 writing style — each entry now explains what was added, how it works, and why it improves security or functionality:

Chapter	Style Applied
Core Security Features	Long descriptive sentences with backtick identifiers and security rationale
Network Configuration	Long descriptive sentences explaining deployment approach and purpose
System Hardening	Long descriptive sentences covering scope and effect of each hardening measure
Package Management	Long descriptive sentences with removal rationale and security impact
Service Management	Long descriptive sentences describing scope of service disabling and rationale
Application Security	Long descriptive sentences explaining each Firefox restriction and its purpose
Installation Scripts	Long descriptive sentences summarising each script's full scope of actions
Automated Installation	Long descriptive sentences describing each automation component and its role
Configuration Management	Long descriptive sentences explaining centralised configuration and template processing
Documentation	Long descriptive sentences summarising README.md scope and supporting materials

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[clauspruefer]

@copilot: please adapt the correct writing style to all mentioned chapters, it does not reflect the writing style used in chapter v0.2 (long descriptive, formulated sentences).

[Copilot]

@copilot: please adapt the correct writing style to all mentioned chapters, it does not reflect the writing style used in chapter v0.2 (long descriptive, formulated sentences).

Done in commit 2657c87. All v0.1 ### Added chapters have been rewritten with long descriptive sentences matching the v0.2 writing style — each bullet now explains what was done and why, consistent with the existing Security/Changed/Removed sections.

[Copilot]

Pull request overview

Updates the v0.1 ### Added section in CHANGELOG.md so it matches the more descriptive, rationale-focused writing style used elsewhere (per PRs #40–#43), without changing the underlying meaning of the entries.

Changes:

• Rewrote all v0.1 “### Added” bullets into full descriptive sentences that include identifiers (backticks) and rationale.
• Flattened previously nested bullet structures into clearer single-level bullet entries per subsection.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The changelog entry uses dbus, but elsewhere in the docs the technology is referred to as “D-Bus” (e.g., README.md:206). Consider renaming this bullet to use “D-Bus” for the concept and (optionally) keep dbus in backticks only when referring to the package/service name, to avoid confusing readers.

Suggested change

	- `dbus` service configuration hardened to restrict inter-process communication capabilities and reduce the exposed system bus attack surface
	- D-Bus (`dbus`) service configuration hardened to restrict inter-process communication capabilities and reduce the exposed system bus attack surface