Adopt canonical governed knowledge content

[adrianwebb]

Outcome

Adopts the canonical governed Knowledge and agent-content contracts in Core while removing repository-owned operational content that now belongs only to TreeDX.

Work authority

• Work item / Issue: Implement the minimal AgentKernel, profile, and workday architecture platform#520
• Proposal / decision: N/A — localized implementation prerequisite for golden acceptance
• Assignment / checkpoint: N/A — authorized local development before live acceptance
• Actor: Codex on dev2
• Human authority: adrian
• Agent / capacity provider: Codex on dev2
• Exact base ref: staging at 030ff18
• Exact head ref: codex/agent-content-schema-cutover at 9cacf06

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Use SDK validation as the single portable contract, keep Core-specific page presentation only in Core, and remove duplicate governed fixtures after their authority moved to TreeDX.

Changes and commits

• Adopt canonical Book, Knowledge, Objective, Question, Proposal, Decision, and discussion content shapes.
• Preserve existing Knowledge presentation fields while removing duplicate governance schemas.
• Remove fixture-owned operational notes, questions, objectives, and agent definitions whose authority is TreeDX.
• Pin SDK 0.13.0-rc.122 and update the fixture submodule to its accepted staging refs.

Verification

• Complete local npm run verify:direct passed at the exact head.

• Core build, package installation smoke, content-schema tests, and fixture-site build passed.

• Hosted verification is the remaining merge gate.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

This is an intentional pre-launch content-authority cutover. Revert this PR before accepting new canonical content if rollback is needed; do not restore repository-owned operational content alongside TreeDX.

Completion summary

Localized Core content-contract integration is complete and locally verified. Managed TreeDX migration/read-back and golden lifecycle evidence remain tracked in Platform #520.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.