Add canonical code-family declarations and provenance metadata updates across governance charters

[CAM-Initiative]

Motivation

• Establish source-authoritative canonical declarations for multiple code families used across the governance corpus to remove ambiguity about classification authority and non-execution scope.
• Ensure consistent end-of-instrument metadata, section numbering, and amendment-ledger bookkeeping across affected charters and schedules.
• Propagate registry/index metadata updates so the top-level constitution.index.json reflects the file-level changes and new pinned hashes/timestamps.

Description

• Inserted Canonical Code Status / Canonical Code & Reference Set Declarations sections into multiple charter and schedule Markdown files to declare code families and controlled values (examples include CBR / CPS, HC, M, AV, I, CA, F, R, C, ITZ/ETZ, AC, and DC) and to clarify that these families are classification-only and do not create execution or enforcement authority.
• Renumbered and relocated several provenance and metadata headings (e.g. Provenance & Metadata subsections moved from §17→§18 etc.) to accommodate the new canonical declarations and to maintain structural consistency.
• Updated amendment ledgers in the modified instruments by adding ledger rows noting the added canonical declarations, and adjusted sealing/footer entries and small formatting hygiene (e.g. duplicate numbering fixes, newline fixes).
• Bumped versions and updated registry metadata in Governance/Constitution/constitution.index.json (version, pinned_sha, updated_at, and last_updated_utc) to reflect the changes.

Testing

• Ran the repository linter and markdown/style checks (repo-wide normative-language linter) which passed.
• Executed the amendment-ledger automation lint_amendment_ledger.py to append/normalize ledger rows and it completed successfully.
• Validated constitution.index.json consistency with a JSON/index validator and the index updates passed validation.

---

Codex Task