docs: amend manifest authority for [components]/[[network.egress]] (DIR-030)

[Xuepoo]

Priority: P1 | Area: area:package | Labels: docs,P1,area:package | Milestone: v0.1.0 | RFC: DIR-030 | Task: CTX-0067

Closes #126

Commander decision (dated accepted amendment, 2026-10-02): specifications/manifest-capability-authority.md section 6 marked [[network.egress]] as rejected, and the Plugin Platform RFC manifest schema lacked [components], but the accepted DIR-030 Native Component Boundary and the bitty host parser (NetworkEgress in bitty-plugin-host/src/manifest.rs, grant computation in bitty-runtime/src/component/grant.rs) depend on both.

Changes

• specifications/manifest-capability-authority.md: section 6 now accepts [components] (component name [a-z][a-z0-9-]{0,31} -> caret semver requirement) and [[network.egress]] ({host, ports}, exact host no wildcard, bounded ports, fail-closed pairing with network.connect:HOST[:PORT], grant = capability ∩ egress). Added a dated amendment subsection with rationale, updated the authority table, the valid/invalid example corpus, and the SDK/host/template/docs requirement lists.
• specifications/plugin-platform-rfc.md: accepted manifest schema fragment now shows [components] and [[network.egress]]; added validation rule 10 cross-linking the amendment.
• extensibility/package-management.md: cross-links the amendment from the Component packages section and shows the paired [[network.egress]] example.
• sdk/net-request-surface-candidate.md: the Open points item naming this conflict is resolved and removed; Affected contracts updated to point at the amendment. Status stays draft.

Verification

• just check: 0 issues (prettier, markdownlint, links, metadata, language, agents, hygiene, svg, actionlint).
• act -n: all jobs dry-run green.

[Xuepoo]

Superseded by #143 (merged): DIR-030 manifest authority amendment landed from a fresh branch. Closing this stale branch PR.