spec: consolidate Core draft and adopt agent-hook-unity/0.1

[trend-kyle-huang]

Summary

The Core draft, website, schemas, and examples described conflicting contracts: stale 7 Gate / 11 Observe counts, mixed response guidance, a colliding wire identifier, non-resolving schema IDs, and no minimum cross-handler deny guarantee. This PR establishes one reviewable candidate baseline through RFC 0007.

• Align the registry and consumer guidance on 18 events: 12 Gate / 6 Observe, canonical top-level decisions, and supported legacy nested fallback. Record the provenance of PR spec: elevate control plane decisions to top-level and expand defense… #9 and the remaining proposals in RFCs 0005 and 0006.
• Rename the canonical wire identifier to agent-hook-unity/0.1 across schemas, examples, and fixtures. This intentionally breaks compatibility with the former draft identifier; migration guidance includes pinned old schemas and signature/approval implications.
• Change schema $id values to the existing agent-hook-unity Pages paths and check that canonical and published schema copies match.
• Require Core hosts to preserve an accepted denial for the same pending action across other handlers' allow, timeout, failure, and redelivery. Timeout alone retains baseline fail-open behavior; native policy, approval requirements, and accepted rewrites remain effective. Add host behavioral conformance scenarios.

RFCs remain Draft with review and votes pending. This does not implement or certify a host runtime or external adapter. A telemetry/correlation profile and Responsible AI interoperability adapter remain a subsequent proposal requiring semantic mapping and real conformance evidence.

Website impact

Update introduction, response, capability, conformance, governance, and participation pages; rendered Core and adapter guidance; examples; site branding; and both schema downloads. Add consistency checks for event membership/counts, mirrored Gate tables, schema copies, and Markdown hook envelopes. Publication occurs through the normal Pages deployment after merge.

Validation

• npm run validate — passed: 14 validator regression tests, schema/fixture/Markdown checks, and image parser guards.
• npm run build — passed.
• git diff --check — passed.
• Executable PreToolUse example — five cases passed: allow, deny, ask, reject old identifier, reject wrong event.
• Independent codex exec -p review diff review — Mergeable, zero findings after fixes and re-review.

Behavioral conformance scenarios are requirements for host integration tests; repository validation does not execute a host runtime.

Checklist

• I reviewed website impact and updated all affected content in this PR, or explained why no website change is needed.
• Affected site summaries, examples, event counts, schema copies, and proposal status labels agree with the source changes.
• I ran npm run validate and npm run build.
• Proposed behavior is clearly distinguished from the current specification.

[trend-brian-chuang]

Great work on consolidating the Core draft and cleaning up the inconsistencies across schemas, docs, and event registries.