docs: align all documentation with the new repo structure

Update agent protocols (.claude/agents, .github/agents), guides, runbooks and READMEs
to the post-restructure layout: .specify/{scripts,tests,security,config,templates,
governance,memory,level5-config} -> packages/casan-harness/...; docs/input +
golden-runs + traceability-map -> apps/okr/domain/...; drop AINative_OKR_CASAN5/ prefix.
Runtime-state paths (.specify/logs, .specify/agentops, .specify/level5/central-governance)
kept as-is. Historical evidence under docs/output/ left untouched (immutable run records).

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

.github/agents/copilot-instructions.md

@@ -8,7 +8,7 @@ You are an expert full-stack developer specializing in NestJS and a **master of
  
 -   **Architecture:** Refer to `docs/technical_architecture.md` for the overall system design, module responsibilities, and technology stack.
  
--   **Requirements:** Refer to `docs/input/okr-requirement.md` for functional requirements, use cases, and UI mockups.
+-   **Requirements:** Refer to `apps/okr/domain/input/okr-requirement.md` for functional requirements, use cases, and UI mockups.
  
 -   **Your Task:** Your role is to translate these designs into code, not to be creative.
  
@@ -63,7 +63,7 @@ You are an expert full-stack developer specializing in NestJS and a **master of
  
 **Design Style: Clean Modern Dashboard (Pure Tailwind CSS)**
  
-This project uses **pure Tailwind CSS** — no external component library (no MUI, no Ant Design). The design is clean, professional, and matches the OKR dashboard wireframes defined in `docs/input/okr-requirement.md`.
+This project uses **pure Tailwind CSS** — no external component library (no MUI, no Ant Design). The design is clean, professional, and matches the OKR dashboard wireframes defined in `apps/okr/domain/input/okr-requirement.md`.
  
 ### Layout Structure (matches OKR wireframes):