[codex] Finalize activation runtime alpha.8 candidate

[Nam-Cheol]

Summary

Finalize the Orange Activation Runtime and first-party Codex Host Binding release candidate for 1.1.0-alpha.8.

This PR synchronizes the release candidate with the canonical repository by:

• promoting package, lockfile, Codex plugin, installer defaults, origin metadata, citation metadata, Identity/Sync schema-facing versions, and version-sensitive tests to 1.1.0-alpha.8;
• keeping the Adapter JSON envelope on contract_version: "0.1";
• separating user-scoped Codex Host Binding from repo-scoped Project Activation;
• adding lifecycle freshness semantics based on same-session SessionStart, UserPromptSubmit, and Stop events within a 24-hour freshness window;
• keeping PostToolUse optional for current lifecycle status;
• ensuring different-session lifecycle events cannot be merged into a complete lifecycle;
• reporting Codex install/enable/hook trust as unknown unless a machine-readable Codex surface can prove otherwise;
• making binding remove explicit about partial removal with pending_user_uninstall_or_disable when Codex-side uninstall/disable cannot be verified;
• adding a real Codex UI E2E checklist in docs/27_CODEX_BINDING_E2E.md.

Why

Public main has not yet received the alpha.8 Activation Runtime candidate. The public README/package state therefore does not match this release candidate, and tag/npm/GitHub Release work must wait until this branch lands through PR review and CI.

Release and E2E Notes

The branch head for PR review and real Codex E2E is:

03c6850f4d6e3cfa4f8904b3e5931f144065f75d

Earlier local SHA b9ca2c1 was amended before PR because package-lock.json still referenced 1.1.0-alpha.7 and one README/trust wording path still described the old pending_trust model.

Real Codex /plugins install, plugin enablement, /hooks review, and fresh-thread lifecycle transitions are still not externally verified. Those results should be recorded in docs/27_CODEX_BINDING_E2E.md against this PR head before merge.

Validation

Local validation run against the current PR head:

• npm test -> 160/160 pass
• npm run typecheck -> pass
• npm run check:readme-sync -> pass, README version sync OK: 1.1-doc.8
• git diff --check -> pass
• npm pack --dry-run --cache /private/tmp/orange-hyper-npm-cache -> orange-hyper@1.1.0-alpha.8, 88 files
• node bin/orange.js --version -> 1.1.0-alpha.8
• node bin/orange.js env --json -> version 1.1.0-alpha.8, contract 0.1

External state checked before PR:

• remote branch codex/activation-runtime-alpha8 points at 03c6850f4d6e3cfa4f8904b3e5931f144065f75d
• no tag, npm publish, or GitHub Release was created by this PR preparation step