feat(runtime): own managed Chrome closure

[MapleCity1314]

Outcome

• move the inventory Chrome Launch Agent into the signed macOS Runtime closure
• gate install, rollback, and uninstall on the exact maintenance-readiness protocol
• atomically restore Core, Chrome, Extension, Native Host, Runtime pointer, and database state on pre-write failures
• verify the live managed Chrome PID against the closure-owned Profile, Extension, loopback CDP address, and bounded flags
• extend the Doudian acceptance path through retired-product Fact/Dataset/Attention/Delivery and the real Feishu adapter using an isolated fake endpoint

Safety

• existing installs fail closed when the running Core cannot prove exact identity or maintenance readiness
• notification delivery remains disabled unless an explicit owner-only mode-0600 macOS config is supplied
• no production launchd service, Chrome profile, webhook, or business database was touched
• the old inventory-owned Chrome plist is removed; no compatibility fallback is retained

Verification

• Node.js 24.18.0 pnpm verify: 158 files / 1248 tests; schema, repository, architecture, scripts, supply-chain, native, typecheck, build, and docs passed
• macOS package closure: 165 files; migration, socket, CLI, Team Worker, Extension, sensitive-content scan, and package verification passed
• targeted retired-product + operator notification + Feishu: 3 files / 19 tests passed
• managed Chrome install gates: 4 tests passed

Deployment boundary

This PR is a code and package candidate only. Real company-Mac installation, authenticated Chrome canary, Trigger enablement, and Feishu webhook configuration require a separate authorized maintenance window.