ai-core-framework 0.3.0 → 0.4.0

package/skills/development-implement-task/SKILL.md

@@ -13,9 +13,9 @@ args:
   - name: ticket_id
     required: true
     format: "TICKET-XXX"
-    description: "Ticket ID from docs/runtime/project/tickets/"
+    description: "Ticket ID from docs/runtime/tickets/"
 preconditions:
-  - ticket_exists: "docs/runtime/project/tickets/${ticket_id}.json"
+  - ticket_exists: "docs/runtime/tickets/${ticket_id}.json"
   - ticket_status_in: [READY, IN_PROGRESS]
   - ticket_has_acceptance_criteria: true
   - no_uncommitted_changes_on_main: true
@@ -54,7 +54,7 @@ Before starting, the AI **MUST** check every condition below. If any condition f
 
 ### 1. Ticket exists
 ```bash
-test -f "docs/runtime/project/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
+test -f "docs/runtime/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
 ```
 
 ### 2. Ticket status valid
@@ -99,7 +99,7 @@ Load `rules/07-definition-of-ready.md`. Verify the ticket passes every item. If
 │  → Example: feature/TICKET-123-reset-password   │
 ├─────────────────────────────────────────────────┤
 │  STEP 4: Update ticket status → IN_PROGRESS     │
-│  → Update docs/runtime/project/tickets/${TICKET_ID}.json       │
+│  → Update docs/runtime/tickets/${TICKET_ID}.json       │
 │  → Add started_at timestamp                     │
 │  → Add assignee = "developer-agent"             │
 ├─────────────────────────────────────────────────┤
@@ -251,7 +251,7 @@ Ready for review. Key things to verify:
 
 ## 📊 Metrics Tracked
 
-After each run, log to `docs/runtime/project/metrics/implement-task.jsonl`:
+After each run, log to `docs/runtime/metrics/implement-task.jsonl`:
 
 ```json
 {

package/skills/meta-generate-views/SKILL.md

@@ -16,7 +16,7 @@ postconditions:
 
 # /generate-views
 
-> Generates human-readable views from `docs/runtime/project/` without changing canonical state.
+> Generates human-readable views from `docs/runtime/` without changing canonical state.
 
 ## 🎯 Purpose
 
@@ -24,14 +24,14 @@ Help humans navigate many tickets without making duplicate sources of truth.
 
 ## 🔄 Execution Flow
 
-1. Load `docs/runtime/project/backlog/backlog.json`.
+1. Load `docs/runtime/backlog/backlog.json`.
 2. Load tickets, bugs, sprints, and releases.
-3. Generate `docs/runtime/project/views/backlog.md`.
-4. Generate `docs/runtime/project/views/ready.md`.
-5. Generate `docs/runtime/project/views/blocked.md`.
-6. Generate `docs/runtime/project/views/by-epic.md`.
-7. Generate `docs/runtime/project/views/by-sprint.md`.
-8. Generate `docs/runtime/project/views/release-candidates.md`.
+3. Generate `docs/runtime/views/backlog.md`.
+4. Generate `docs/runtime/views/ready.md`.
+5. Generate `docs/runtime/views/blocked.md`.
+6. Generate `docs/runtime/views/by-epic.md`.
+7. Generate `docs/runtime/views/by-sprint.md`.
+8. Generate `docs/runtime/views/release-candidates.md`.
 9. Include generation timestamp and source files.
 
 ## 🔒 Hard Rules

package/skills/meta-request-log/SKILL.md

@@ -15,14 +15,14 @@ args:
     default: 20
     description: "Number of recent user requests to show"
 preconditions:
-  - user_request_log_exists: "docs/runtime/project/user-requests.jsonl"
+  - user_request_log_exists: "docs/runtime/user-requests.jsonl"
 postconditions:
   - request_log_reported: true
 ---
 
 # /request-log
 
-> Show recent user requests recorded in `docs/runtime/project/user-requests.jsonl`.
+> Show recent user requests recorded in `docs/runtime/user-requests.jsonl`.
 
 ## 🎯 Purpose
 
@@ -37,7 +37,7 @@ Give the user an auditable view of what they asked the AI to do.
 
 ## 🔄 Execution Flow
 
-1. Read `docs/runtime/project/user-requests.jsonl`.
+1. Read `docs/runtime/user-requests.jsonl`.
 2. Show the most recent N entries, default 20.
 3. Include timestamp, agent, detected command, ticket ID, and sanitized request text.
 4. If the log is missing, tell the user to run `/setup-project`.
@@ -48,7 +48,7 @@ Give the user an auditable view of what they asked the AI to do.
 The command **MUST NOT** attempt to reconstruct secrets from `request_hash` or any redacted value.
 
 ### RULE RL-002: Log is append-only
-Existing `docs/runtime/project/user-requests.jsonl` entries **MUST NOT** be edited. Corrections require a new request entry.
+Existing `docs/runtime/user-requests.jsonl` entries **MUST NOT** be edited. Corrections require a new request entry.
 
 ## 📤 Output Format
 

package/skills/meta-sprint-report/SKILL.md

@@ -19,7 +19,7 @@ postconditions:
 
 # /sprint-report
 
-> Produces a factual sprint health and outcome report from `docs/runtime/project/`.
+> Produces a factual sprint health and outcome report from `docs/runtime/`.
 
 ## 🎯 Purpose
 
@@ -33,7 +33,7 @@ Give the team an auditable view of commitment, progress, blockers, carryover, de
 4. List work by state.
 5. Identify aging tickets and unresolved blockers.
 6. Summarize risks, decisions, and recommended next actions.
-7. Save report under `docs/runtime/project/sprints/` or `docs/runtime/project/metrics/` if requested.
+7. Save report under `docs/runtime/sprints/` or `docs/runtime/metrics/` if requested.
 
 ## 🔒 Hard Rules
 

package/skills/meta-ticket-health/SKILL.md

@@ -20,7 +20,7 @@ postconditions:
 
 # /ticket-health
 
-> Finds stale, blocked, inconsistent, or under-specified tickets in `docs/runtime/project/tickets/`.
+> Finds stale, blocked, inconsistent, or under-specified tickets in `docs/runtime/tickets/`.
 
 ## 🎯 Purpose
 

package/skills/meta-validate-audit-log/SKILL.md

@@ -23,7 +23,7 @@ postconditions:
 
 ## Purpose
 
-Detect manual edits to `docs/runtime/project/audit-log.jsonl`. Executable workflow handlers append records with `prev_hash` and `hash`; this command recomputes the chain.
+Detect manual edits to `docs/runtime/audit-log.jsonl`. Executable workflow handlers append records with `prev_hash` and `hash`; this command recomputes the chain.
 
 ## Chat Usage
 

package/skills/meta-validate-permissions/SKILL.md

@@ -24,7 +24,7 @@ postconditions:
 
 ## Purpose
 
-Make role boundaries mechanically enforceable by comparing `docs/runtime/project/tickets/*.json` history entries with `commands/**` command ownership metadata.
+Make role boundaries mechanically enforceable by comparing `docs/runtime/tickets/*.json` history entries with `commands/**` command ownership metadata.
 
 ## Chat Usage
 

package/skills/meta-validate-state/SKILL.md

@@ -19,7 +19,7 @@ postconditions:
 
 # /validate-state
 
-> Validates `docs/runtime/project/` integrity, backlog references, ticket schema, and allowed state transitions.
+> Validates `docs/runtime/` integrity, backlog references, ticket schema, and allowed state transitions.
 
 ## 🎯 Purpose
 
@@ -29,7 +29,7 @@ Catch corrupted backlog data, missing ticket references, skipped transitions, mi
 
 1. Verify `jq` is installed.
 2. In chat, run `/validate-state` with optional ticket ID. The AI may call `scripts/validate-state.sh` internally.
-3. Validate `docs/runtime/project/backlog/backlog.json` references existing tickets when validating all state.
+3. Validate `docs/runtime/backlog/backlog.json` references existing tickets when validating all state.
 4. If available, run JSON schema validation against `docs/config/ticket.schema.json` and `docs/config/backlog.schema.json`.
 5. Report failures with file path, field, and recovery command.
 6. Block workflow if validation fails.

package/skills/planning-analyze-requirements/SKILL.md

@@ -64,7 +64,7 @@ Check before starting. **ABORT** if any check fails.
 
 ### 1. Root-level framework folders initialized
 ```bash
-test -d "docs/runtime/project/tickets" || ABORT "Run /setup-project first"
+test -d "docs/runtime/tickets" || ABORT "Run /setup-project first"
 ```
 
 ### 2. BA agent available
@@ -139,12 +139,12 @@ If empty or < 10 chars → ABORT and ask for the actual requirement.
 │   - External dependencies (3rd party API)?               │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 8: Generate ticket ID                               │
-│   - Read docs/runtime/project/tickets/                         │
+│   - Read docs/runtime/tickets/                         │
 │   - Find highest TICKET-NNN                              │
 │   - Increment: TICKET-NNN+1                              │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 9: Write ticket JSON                                │
-│   Path: docs/runtime/project/tickets/TICKET-XXX.json           │
+│   Path: docs/runtime/tickets/TICKET-XXX.json           │
 │   Schema: docs/config/ticket.schema.json             │
 │   State: DRAFT                                           │
 │   created_by: "business-analyst-agent"                   │
@@ -194,7 +194,7 @@ SEV-1 bug **MUST** trigger hotfix notification:
 
 ### RULE AR-009: No duplicate tickets
 Before creating, **MUST** search existing tickets for similar work:
-- Grep titles in `docs/runtime/project/tickets/*.json`
+- Grep titles in `docs/runtime/tickets/*.json`
 - If high similarity (>80%) → flag to user, ask if duplicate
 
 ### RULE AR-010: Complete source tracking
@@ -297,7 +297,7 @@ Estimated: 40% support load reduction if self-service reset works.
 - [ ] Email template: existing template system or custom?
 
 ### Ticket File
-Created: `docs/runtime/project/tickets/TICKET-042.json`
+Created: `docs/runtime/tickets/TICKET-042.json`
 
 ---
 HANDOFF → tech-lead
@@ -404,7 +404,7 @@ Then Login fails, no SQL injection possible
 3. **Dev**: Pair with Tech Lead on fix
 
 ### Ticket File
-Created: `docs/runtime/project/tickets/TICKET-101.json`
+Created: `docs/runtime/tickets/TICKET-101.json`
 
 ---
 HANDOFF → scrum-master + tech-lead (URGENT)
@@ -433,7 +433,7 @@ Action needed: /hotfix TICKET-101
 
 ## 📊 Metrics Tracked
 
-Log to `docs/runtime/project/metrics/analyze-requirements.jsonl`:
+Log to `docs/runtime/metrics/analyze-requirements.jsonl`:
 
 ```json
 {

package/skills/planning-backlog-status/SKILL.md

@@ -11,14 +11,14 @@ consults_agents:
 model_preference: sonnet
 args: []
 preconditions:
-  - backlog_exists: "docs/runtime/project/backlog/backlog.json"
+  - backlog_exists: "docs/runtime/backlog/backlog.json"
 postconditions:
   - backlog_report_generated: true
 ---
 
 # /backlog-status
 
-> Reports backlog health from `docs/runtime/project/backlog/backlog.json` and linked ticket files.
+> Reports backlog health from `docs/runtime/backlog/backlog.json` and linked ticket files.
 
 ## 🎯 Purpose
 
@@ -26,8 +26,8 @@ Show whether the backlog is prioritized, actionable, and aligned with ticket sta
 
 ## 🔄 Execution Flow
 
-1. Load `docs/runtime/project/backlog/backlog.json`.
-2. Load referenced `docs/runtime/project/tickets/TICKET-XXX.json` files.
+1. Load `docs/runtime/backlog/backlog.json`.
+2. Load referenced `docs/runtime/tickets/TICKET-XXX.json` files.
 3. Detect missing ticket references.
 4. Detect duplicate ranks or duplicate ticket IDs.
 5. Group by priority, epic, and status.
@@ -36,8 +36,8 @@ Show whether the backlog is prioritized, actionable, and aligned with ticket sta
 
 ## 🔒 Hard Rules
 
-- Backlog ordering source of truth is `docs/runtime/project/backlog/backlog.json`.
-- Ticket detail source of truth is `docs/runtime/project/tickets/TICKET-XXX.json`.
+- Backlog ordering source of truth is `docs/runtime/backlog/backlog.json`.
+- Ticket detail source of truth is `docs/runtime/tickets/TICKET-XXX.json`.
 - MUST NOT duplicate full ticket content in backlog reports.
 - MUST flag backlog items pointing to missing tickets.
 

package/skills/planning-groom-ticket/SKILL.md

@@ -17,7 +17,7 @@ args:
     format: "TICKET-XXX"
     description: "Ticket ID to groom"
 preconditions:
-  - ticket_exists: "docs/runtime/project/tickets/${ticket_id}.json"
+  - ticket_exists: "docs/runtime/tickets/${ticket_id}.json"
   - ticket_status: DRAFT
   - has_user_story: true
   - has_acceptance_criteria: true (min 3 scenarios)
@@ -60,7 +60,7 @@ After BA creates a DRAFT ticket, Tech Lead must:
 
 ### 1. Ticket exists
 ```bash
-test -f "docs/runtime/project/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
+test -f "docs/runtime/tickets/${TICKET_ID}.json" || ABORT "Ticket not found"
 ```
 
 ### 2. Ticket status = DRAFT
@@ -300,7 +300,7 @@ Block transition to GROOMED until ADR created OR explicit decision to defer.
 ### Ticket Update
 
 **State**: DRAFT → GROOMED ✅ (assuming questions minor)
-**Updated**: `docs/runtime/project/tickets/TICKET-042.json`
+**Updated**: `docs/runtime/tickets/TICKET-042.json`
 
 Added fields:
 - `estimate`: `{ story_points: 5, estimated_by: "tech-lead-agent", estimated_at: "..." }`
@@ -420,7 +420,7 @@ State: DRAFT → BLOCKED (pending split)
 
 ## 📊 Metrics Tracked
 
-Log to `docs/runtime/project/metrics/groom-ticket.jsonl`:
+Log to `docs/runtime/metrics/groom-ticket.jsonl`:
 
 ```json
 {

package/skills/planning-mark-ready/SKILL.md

@@ -18,7 +18,7 @@ args:
     format: "TICKET-XXX"
     description: "GROOMED ticket to verify against Definition of Ready"
 preconditions:
-  - ticket_exists: "docs/runtime/project/tickets/${ticket_id}.json"
+  - ticket_exists: "docs/runtime/tickets/${ticket_id}.json"
   - ticket_status: GROOMED
   - has_estimate: true
   - has_acceptance_criteria: true
@@ -46,7 +46,7 @@ Manual only:
 
 ## 📋 Preconditions, STRICT
 
-1. Ticket exists in `docs/runtime/project/tickets/`.
+1. Ticket exists in `docs/runtime/tickets/`.
 2. Ticket status is exactly `GROOMED`.
 3. Ticket has user story, acceptance criteria, estimate, technical approach, risks, and dependencies.
 4. Ticket estimate is one of `1, 2, 3, 5, 8`.

package/skills/planning-plan-refactor/SKILL.md

@@ -37,8 +37,8 @@ Plan large refactors without putting project-specific design into framework sour
 3. Identify current problem, target state, constraints, and risks.
 4. Determine whether ADR is required.
 5. Create `docs/runtime/refactor/<slug>-refactor-plan.md` from `templates/technical/refactor-plan-template.md`.
-6. Propose ticket breakdown for `docs/runtime/project/tickets/`.
-7. Propose backlog entries for `docs/runtime/project/backlog/backlog.json`.
+6. Propose ticket breakdown for `docs/runtime/tickets/`.
+7. Propose backlog entries for `docs/runtime/backlog/backlog.json`.
 8. Define testing, rollout, and rollback plan.
 9. HANDOFF to BA for ticket creation or Tech Lead for ADR.
 

package/skills/planning-plan-sprint/SKILL.md

@@ -35,7 +35,7 @@ postconditions:
 
 ## 🎯 Purpose
 
-Build a realistic sprint commitment. It selects only `READY` tickets, respects configured sprint capacity, checks dependencies, and writes the sprint plan to `docs/runtime/project/sprints/`.
+Build a realistic sprint commitment. It selects only `READY` tickets, respects configured sprint capacity, checks dependencies, and writes the sprint plan to `docs/runtime/sprints/`.
 
 ## 🚦 Trigger
 
@@ -63,9 +63,9 @@ Manual at sprint planning:
 6. Select tickets until capacity is reached.
 7. Reserve capacity for bugs, review, QA, and operational work.
 8. Validate no selected ticket violates DoR.
-9. Write `docs/runtime/project/sprints/SPRINT-XXX.json` with goal, dates, capacity, committed tickets, risks, and assumptions.
+9. Write `docs/runtime/sprints/SPRINT-XXX.json` with goal, dates, capacity, committed tickets, risks, and assumptions.
 10. Update selected tickets with `sprint_id`.
-11. Append planning metrics to `docs/runtime/project/metrics/sprint-planning.jsonl`.
+11. Append planning metrics to `docs/runtime/metrics/sprint-planning.jsonl`.
 12. Output sprint goal, commitment, risks, and handoffs.
 
 ## 🔒 Hard Rules

package/skills/planning-prioritize-backlog/SKILL.md

@@ -16,14 +16,14 @@ args:
     enum: [moscow, rice, manual]
     default: moscow
 preconditions:
-  - backlog_exists: "docs/runtime/project/backlog/backlog.json"
+  - backlog_exists: "docs/runtime/backlog/backlog.json"
 postconditions:
   - backlog_order_updated: true
 ---
 
 # /prioritize-backlog
 
-> Updates backlog ranking in `docs/runtime/project/backlog/backlog.json` using MoSCoW, RICE, dependencies, and stakeholder input.
+> Updates backlog ranking in `docs/runtime/backlog/backlog.json` using MoSCoW, RICE, dependencies, and stakeholder input.
 
 ## 🎯 Purpose
 

package/skills/planning-write-plan/SKILL.md

@@ -42,7 +42,7 @@ Turn a groomed or ready ticket into a concrete execution plan before coding star
 
 ## Execution Flow
 
-1. Read `docs/runtime/project/tickets/TICKET-XXX.json`.
+1. Read `docs/runtime/tickets/TICKET-XXX.json`.
 2. Read `spec_path` if present.
 3. Inspect relevant code/docs just enough to identify affected files and test strategy.
 4. Create `docs/project/plans/TICKET-XXX-<slug>-plan.md`.

package/skills/project-discover-codebase/SKILL.md

@@ -43,7 +43,7 @@ Give AI agents shared context before implementation and review. The output helps
 4. Identify test layout and command coverage.
 5. Identify architecture docs and ADRs.
 6. Identify external integrations and environment assumptions.
-7. Produce `docs/runtime/project/codebase-map.md` or update existing map with timestamp.
+7. Produce `docs/runtime/codebase-map.md` or update existing map with timestamp.
 8. List risks, missing docs, and recommended follow-up tickets.
 
 ## 🔒 Hard Rules

package/skills/project-setup-project/SKILL.md

@@ -44,7 +44,7 @@ Manual after copying root-level framework folders into a project:
 2. `README.md` exists.
 3. `templates/project/project-config.yaml` exists.
 4. `templates/project/project-structure.yaml` exists.
-5. User has permission to create `docs/config/`, `docs/runtime/project/`, `docs/project/`, `docs/runtime/`, `.claude/`, `.cursor/`, `.windsurfrules`, and `CLAUDE.md`.
+5. User has permission to create `docs/config/`, `docs/runtime/`, `docs/project/`, `.claude/`, `.cursor/`, `.windsurfrules`, and `CLAUDE.md`.
 
 ## 🔄 Execution Flow
 
@@ -53,9 +53,9 @@ Manual after copying root-level framework folders into a project:
 3. Copy `templates/project/project-config.yaml` to `docs/config/project-config.yaml` if missing.
 4. Copy `templates/project/project-structure.yaml` to `docs/config/project-structure.yaml` if missing.
 5. Ask for missing project fields or infer with `/detect-stack`.
-6. Create required `docs/runtime/project/` directories: tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, prs.
+6. Create required `docs/runtime/` directories: tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, prs.
 7. Create required docs namespaces: `docs/project/` for project/product requirements and `docs/runtime/` for operational AI Core documentation.
-8. Create `docs/runtime/project/backlog/backlog.json` and `docs/runtime/project/user-requests.jsonl` if missing.
+8. Create `docs/runtime/backlog/backlog.json` and `docs/runtime/user-requests.jsonl` if missing.
 9. Run `bash scripts/setup-project.sh` when shell access is available, or perform steps 2-8 manually.
 10. Confirm `scripts/` contains the portable enforcement scripts.
 11. Install portable `.github/workflows/ai-core-governance.yml` if missing.
@@ -73,16 +73,16 @@ If config values already exist, preserve them unless user confirms change.
 Generated `.claude/`, `.cursor/`, and `.windsurfrules` files are exports. Source changes belong in root-level framework folders.
 
 ### RULE SP-003: No product code changes
-Setup modifies AI runtime/config files only: `docs/config/`, `docs/runtime/project/`, `docs/project/`, `docs/runtime/`, generated platform config, and optional docs scaffolding. It MUST NOT modify production source code.
+Setup modifies AI runtime/config files only: `docs/config/`, `docs/runtime/`, `docs/project/`, generated platform config, and optional docs scaffolding. It MUST NOT modify production source code.
 
 ### RULE SP-004: State directories required
-A project is not ready until `docs/runtime/project/` contains directories for tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, and prs.
+A project is not ready until `docs/runtime/` contains directories for tickets, backlog, bugs, sprints, releases, metrics, views, test-runs, verifications, incidents, and prs.
 
 ### RULE SP-004a: User request log required
-A project is not ready until `docs/runtime/project/user-requests.jsonl` exists. Every AI-handled user request **MUST** be logged there before substantive work begins.
+A project is not ready until `docs/runtime/user-requests.jsonl` exists. Every AI-handled user request **MUST** be logged there before substantive work begins.
 
 ### RULE SP-005: Framework folders remain framework-only
-Project-specific state and config MUST NOT be written under framework source folders. Use `docs/runtime/project/` and `docs/config/`.
+Project-specific state and config MUST NOT be written under framework source folders. Use `docs/runtime/` and `docs/config/`.
 
 ### RULE SP-006: `scripts/` is canonical
 Portable enforcement scripts live under `scripts/`.

package/skills/qa-bug-status/SKILL.md

@@ -24,7 +24,7 @@ Give QA, Scrum Master, and Tech Lead a clear picture of defect health.
 
 ## 🔄 Execution Flow
 
-1. Load `docs/runtime/project/bugs/*.json`.
+1. Load `docs/runtime/bugs/*.json`.
 2. Group bugs by severity and status.
 3. Identify stale bugs and missing owners.
 4. Identify release-blocking bugs.

package/skills/qa-report-bug/SKILL.md

@@ -66,7 +66,7 @@ If not → prompt interactive collection.
 
 ### 2. Not duplicate
 Check existing open bugs for similar:
-- Grep bug titles in `docs/runtime/project/bugs/*.json`
+- Grep bug titles in `docs/runtime/bugs/*.json`
 - If > 80% similarity → flag, ask if linking to existing
 
 ### 3. Has evidence (soft requirement)
@@ -125,7 +125,7 @@ If missing, still accept but flag in bug.
 │   BUG-NNN (separate sequence from TICKET-)               │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 8: Create bug ticket                                │
-│   Path: docs/runtime/project/bugs/BUG-NNN.json                 │
+│   Path: docs/runtime/bugs/BUG-NNN.json                 │
 │   Follow template: templates/qa/bug-report-template.md  │
 │   Initial status: NEW                                    │
 ├──────────────────────────────────────────────────────────┤
@@ -224,7 +224,7 @@ Missing env info = bug 50% harder to fix.
 Don't say "always" if not sure.
 
 ### RULE RB-009: Evidence preservation
-Screenshots, logs, HAR files → save to `docs/runtime/project/bugs/evidence/BUG-NNN/`.
+Screenshots, logs, HAR files → save to `docs/runtime/bugs/evidence/BUG-NNN/`.
 
 Don't paste long logs in bug body → link to file.
 
@@ -304,8 +304,8 @@ Auto assess: Data integrity concern → SEV-1.
 Always (5/5 attempts)
 
 ### Evidence
-- Screenshot: `docs/runtime/project/bugs/evidence/BUG-005/screenshot-1.png`
-- Network trace: `docs/runtime/project/bugs/evidence/BUG-005/har.json`
+- Screenshot: `docs/runtime/bugs/evidence/BUG-005/screenshot-1.png`
+- Network trace: `docs/runtime/bugs/evidence/BUG-005/har.json`
 - Server log excerpt:
   ```
   2026-04-18T18:45:23Z ERROR handler/login.ts:42 
@@ -349,7 +349,7 @@ Likely: URL decoding treating + as space (classic `encodeURIComponent` vs `+` is
 
 ### Ticket File
 
-Created: `docs/runtime/project/bugs/BUG-005.json`
+Created: `docs/runtime/bugs/BUG-005.json`
 
 ### Next Steps
 
@@ -405,7 +405,7 @@ Action: /triage-bug BUG-005
 - [ ] Executive team (if not resolved in 2h)
 
 ### Ticket File
-Created: `docs/runtime/project/bugs/BUG-006.json`
+Created: `docs/runtime/bugs/BUG-006.json`
 
 ---
 HANDOFF → tech-lead + scrum-master (URGENT)

package/skills/qa-smoke-test/SKILL.md

@@ -79,7 +79,7 @@ curl -sf --max-time 10 "$STAGING_URL/health" || ABORT "Staging not responding"
 Check build version matches expected:
 ```bash
 deployed_commit=$(curl -s "$STAGING_URL/version" | jq -r .commit)
-expected_commit=$(cat docs/runtime/project/tickets/${TICKET_ID}.json | jq -r .merge_info.merge_commit_sha)
+expected_commit=$(cat docs/runtime/tickets/${TICKET_ID}.json | jq -r .merge_info.merge_commit_sha)
 # Verify deployed >= expected
 ```
 
@@ -145,7 +145,7 @@ Required test accounts / test data exist. If not, setup before testing.
 │     → File separate regression bug (own ticket)          │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 9: Generate report                                  │
-│   Save to: docs/runtime/project/test-runs/TICKET-XXX-YYYYMMDD.md│
+│   Save to: docs/runtime/test-runs/TICKET-XXX-YYYYMMDD.md│
 ├──────────────────────────────────────────────────────────┤
 │ STEP 10: Handoff                                         │
 │   Pass → scrum-master (ready for release)                │
@@ -261,7 +261,7 @@ None 🎉
 Ticket state: QA → DONE ✅
 
 ### Test Run Record
-Saved to: `docs/runtime/project/test-runs/TICKET-042-20260418.md`
+Saved to: `docs/runtime/test-runs/TICKET-042-20260418.md`
 
 ---
 HANDOFF → scrum-master

package/skills/qa-verify-fix/SKILL.md

@@ -54,7 +54,7 @@ After developer claims the bug is fixed and PR is merged + deployed:
 
 ### 1. Bug exists + in correct state
 ```bash
-bug_status=$(cat docs/runtime/project/bugs/${BUG_ID}.json | jq -r .status)
+bug_status=$(cat docs/runtime/bugs/${BUG_ID}.json | jq -r .status)
 [ "$bug_status" = "FIXED" ] || [ "$bug_status" = "READY_FOR_QA" ] || ABORT
 ```
 
@@ -141,7 +141,7 @@ Check linked PR is merged (not still open).
 │     → HANDOFF → developer                                │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 9: Generate report                                  │
-│   Save to: docs/runtime/project/verifications/BUG-XXX-YYYYMMDD.md│
+│   Save to: docs/runtime/verifications/BUG-XXX-YYYYMMDD.md│
 ├──────────────────────────────────────────────────────────┤
 │ STEP 10: Update bug state + notify                       │
 └──────────────────────────────────────────────────────────┘
@@ -267,7 +267,7 @@ Bug status: FIXED → VERIFIED
 - BUG-004 (email HTML rendering): Still open, separate fix
 
 ### Verification Record
-Saved to: `docs/runtime/project/verifications/BUG-002-20260418.md`
+Saved to: `docs/runtime/verifications/BUG-002-20260418.md`
 
 ---
 HANDOFF → scrum-master

package/skills/release-hotfix/SKILL.md

@@ -56,7 +56,7 @@ Manual:
 ## 🔄 Execution Flow
 
 1. Triage severity and impact.
-2. Create or link `BUG-NNN` in `docs/runtime/project/bugs/`.
+2. Create or link `BUG-NNN` in `docs/runtime/bugs/`.
 3. Create hotfix ticket if needed with minimal AC and status `READY`.
 4. Create branch `hotfix/BUG-NNN-short-slug` or `hotfix/TICKET-NNN-short-slug` from production branch.
 5. Reproduce the issue and write a regression test if feasible.
@@ -69,7 +69,7 @@ Manual:
 12. QA verifies production or pre-prod depending on incident protocol.
 13. Back-merge hotfix into `develop`.
 14. Create follow-up ticket for full DoD, monitoring, and root cause analysis.
-15. Write incident summary in `docs/runtime/project/releases/` or `docs/runtime/project/incidents/`.
+15. Write incident summary in `docs/runtime/releases/` or `docs/runtime/incidents/`.
 
 ## 🔒 Hard Rules
 

package/skills/release-release/SKILL.md

@@ -65,7 +65,7 @@ Manual:
 5. Confirm QA evidence exists for every included ticket.
 6. Check open bugs and known issues.
 7. Generate changelog with ticket IDs, PRs, bug fixes, migrations, and breaking changes.
-8. Create `docs/runtime/project/releases/vX.Y.Z.json` from `templates/release/release-record-template.json` with scope, approvals, risks, deploy plan, rollback plan, and timestamps.
+8. Create `docs/runtime/releases/vX.Y.Z.json` from `templates/release/release-record-template.json` with scope, approvals, risks, deploy plan, rollback plan, and timestamps.
 9. Create or update release branch if configured.
 10. Tag release using `vX.Y.Z`.
 11. Trigger deployment or document manual deployment step.

package/skills/release-rollback/SKILL.md

@@ -38,7 +38,7 @@ Restore service safely, preserve audit trail, and start follow-up remediation.
 4. Notify stakeholders and freeze related deploys.
 5. Execute documented rollback steps.
 6. Verify service health and core flows.
-7. Record rollback result in `docs/runtime/project/releases/`.
+7. Record rollback result in `docs/runtime/releases/`.
 8. Create follow-up bug/ticket and incident notes.
 
 ## 🔒 Hard Rules

package/skills/review-create-pr/SKILL.md

@@ -79,7 +79,7 @@ fi
 Extract TICKET-XXX from branch name, verify:
 ```bash
 TICKET_ID=$(echo "$current_branch" | grep -oE 'TICKET-[0-9]+')
-test -f "docs/runtime/project/tickets/${TICKET_ID}.json" || ABORT
+test -f "docs/runtime/tickets/${TICKET_ID}.json" || ABORT
 ```
 
 ### 3. Ticket in IN_PROGRESS
@@ -203,7 +203,7 @@ fi
 │   - (Optional) Slack notification via webhook            │
 ├──────────────────────────────────────────────────────────┤
 │ STEP 10: Log metrics                                     │
-│   docs/runtime/project/metrics/create-pr.jsonl                 │
+│   docs/runtime/metrics/create-pr.jsonl                 │
 └──────────────────────────────────────────────────────────┘
 ```
 

package/skills/review-merge-pr/SKILL.md

@@ -205,7 +205,7 @@ If branch is `hotfix/*`:
 - Merge commit SHA
 - Strategy used
 
-Store in `docs/runtime/project/audit-log.jsonl`.
+Store in `docs/runtime/audit-log.jsonl`.
 
 ### RULE MP-009: Rollback plan for risky merges
 If PR flagged as `high-risk` (auth changes, DB migration, payment):