docs: deploy the ai-constitution with core so the governance pointer resolves

Why: the always-on governance.md told agents to read
docs/ai-constitution.md when a decision is not covered, a path that
exists only in this repo, so the fallback failed in every other project.
(Simplification audit finding 27, second defect.)

Implementation Notes:
- Move docs/ai-constitution.md to core/ai-constitution.md; the existing
  core deploy step now ships it to ~/.claude/core/.
- governance.md line 4 and line 73 name ~/.claude/core/ai-constitution.md;
  the HUMANS.md and CONTROLS.md pointers now say they live in the
  holocron repo.
- Repoint path-qualified citations in AGENTS.md, architecture.md,
  skill-implementation-workflow.md and CONTROLS.md. The vendored
  write-skill example and the audit's historical notes are left as
  records.
- The docs/wiki gitlink is not bumped here; the wiki commit awaits push.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/research/governance_principles/CONTROLS.md

@@ -1,7 +1,7 @@
 # Deterministic Controls
 
 Applies to: any environment, repository, or pipeline where AI tools are used.
-Full governance context: `docs/ai-constitution.md` — principles these controls enforce.
+Full governance context: `core/ai-constitution.md` — principles these controls enforce.
 Human practitioner rules: `docs/wiki/HUMANS.md` | Agent instructions: `core/instructions/governance.md`
 This file specifies the enforcement layer: controls that run mechanically, regardless of human or agent intention.
 
@@ -103,4 +103,4 @@ Human judgment decisions — which AI model to use, whether a specific output is
 ---
 
 *Derived from AI Constitution v1.1 — May 2026.*
-*Counterpart to: `docs/wiki/HUMANS.md` | `core/instructions/governance.md` | Full context: `docs/ai-constitution.md`*
+*Counterpart to: `docs/wiki/HUMANS.md` | `core/instructions/governance.md` | Full context: `core/ai-constitution.md`*