docs(getting-started): polish step 2/7/8 for the daemon model

[ALRubinger]

Summary

Three small clarity fixes to `docs/src/content/docs/getting-started.md`. Spotted while evaluating the guide against the comms-daemon work in #484.

• Step 2 title — `(No separate server to start)` → `The Local Daemon`. Define the section by what it is, not by what's absent.
• Step 7 — `send-email` / `create-calendar-event` paragraph — drop "launch comms channel" wording (the pre-feat(comms): move comms + listeners to daemon ownership (#482) #484 mental model). Under the daemon-owned approval surface, every approval lands on the daemon's `/approvals` page, which is the URL already printed in the launch banner above.
• Step 8 — clarify the difference between `aileron status` and `aileron daemon status`. The first is configuration-shaped, the second is process-shaped; they overlap only on vault state. The current bullet list reads redundant without that framing.

No Slack/Discord references introduced (per directive: those listeners are coming out of core in #483).

Test plan

• Visual check: render the docs site and confirm no broken links / formatting.
• No em-dashes added in new prose (per the docs voice rule).

🤖 Generated with Claude Code

[railway-app]

🚅 Deployed to the aileron-pr-485 environment in aileron

Service	Status	Web	Updated (UTC)
docs	✅ Success (View Logs)	Web	May 7, 2026 at 12:00 am

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.18%. Comparing base (16615da) to head (b89cb35).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #485   +/-   ##
=======================================
  Coverage   82.18%   82.18%           
=======================================
  Files         237      237           
  Lines       24134    24134           
=======================================
  Hits        19835    19835           
  Misses       3137     3137           
  Partials     1162     1162           

Flag	Coverage Δ
integration	8.59% <ø> (ø)
unit	78.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.