macca-method 2.1.1 → 2.1.2

package/.agents/skills/code-review/references/review-checklist.md

@@ -47,6 +47,7 @@ Check CR-01 through CR-27 without skipping. Continue to Phase 2 only after all 2
 - **CR-24 Environment Assumptions**
 
 For **CR-23**, prefer these tags:
+
 - `delete:` dead code or unnecessary flexibility
 - `stdlib:` a standard-library replacement exists
 - `native:` a native platform/framework feature exists
@@ -84,6 +85,7 @@ Check all of these:
 ## Self-Review Before Reporting
 
 Before producing the report:
+
 1. Verify that all 27 CR checks and 10 SEC checks were actually reviewed.
 2. Quickly reread touched files for duplicate functions and hallucinated imports.
 3. Recheck severity proportionality.
@@ -101,12 +103,13 @@ Use this report structure:
 **Status:** [💥 BLOCKER | 🔴 MAJOR | ⚠️ MINOR | ✅ PASS]
 
 ### Summary
-| Category | Count |
-|----------|-------|
-| 💥 Blocker | X |
-| 🔴 Major | X |
-| ⚠️ Minor | X |
-| ℹ️ Info | X |
+
+| Category   | Count |
+| ---------- | ----- |
+| 💥 Blocker | X     |
+| 🔴 Major   | X     |
+| ⚠️ Minor   | X     |
+| ℹ️ Info    | X     |
 ```
 
 Then list findings by severity, followed by the checklist status table.
@@ -115,9 +118,10 @@ Before a report-first gate, retain this fix manifest for actionable findings:
 
 ```markdown
 ### Fix Manifest
-| Finding | Target | Intended change | Validation |
-|---|---|---|---|
-| [ID] | `[path]` | [bounded change] | [targeted check] |
+
+| Finding | Target   | Intended change  | Validation       |
+| ------- | -------- | ---------------- | ---------------- |
+| [ID]    | `[path]` | [bounded change] | [targeted check] |
 ```
 
 If the workflow will update a phase plan status or append Code Review Notes, include that plan file and mutation in the manifest. Otherwise return plan-status completion to `developer`; approval never authorizes an undisclosed plan edit.
@@ -127,13 +131,17 @@ Format every finding with the shared `finding-format.md` loaded by the parent sk
 Fix priority - follow `fixMode` from Shared Runtime Setup:
 
 **`report-first` (default):**
-Present the full report and fix manifest. Show the gate prompt from the shared runtime contract loaded by the parent skill. **End the response. DO NOT apply any fixes in the same response.** On approval, follow the Approval Resume Protocol without another question.
+
+- **When actionable findings exist (`💥 BLOCKER`, `🔴 MAJOR`, or actionable `⚠️ MINOR`):** Present the full report and fix manifest. Show the gate prompt (`[GATE — Mode: report-first]`) from the shared runtime contract (`fix-mode.md`). **End the response. DO NOT apply any fixes in the same response.** On approval, follow the Approval Resume Protocol without another question.
+- **When all checks pass (`✅ PASS` / 0 actionable findings):** Present the report with `Status: ✅ PASS`. **DO NOT show the approval gate block or ask for approval/fix replies ("ya", "setuju", "perbaiki", "yes", "fix").** Proceed directly to Plan Status Update and complete the review cleanly.
 
 **`fix-then-report`:**
+
 - `💥 BLOCKER` -> fix now
 - `🔴 MAJOR` -> fix before the next phase
 - `⚠️ MINOR` -> report and discuss
 - `ℹ️ INFO` -> backlog
+- `✅ PASS` -> no fixes needed, proceed directly to Plan Status Update
 
 ## Post-Fix Validation
 
@@ -152,6 +160,7 @@ After fixes are applied and the review is complete, check whether a plan file ex
 **Step 1 - Detect plan-level deviations.**
 
 A plan-level deviation is any finding where the implementation differs from a decision explicitly stated in the plan, for example:
+
 - The wrong library was used (the plan says Prisma, the code uses Drizzle)
 - The architectural pattern was not followed (the plan says repository pattern, the code puts queries in the controller)
 - Scope was expanded or reduced compared to the plan
@@ -163,6 +172,7 @@ Code quality findings are **not** plan deviations - naming issues, missing tests
 
 - **If plan-level deviations were found:**
   1. Add this section at the bottom of the plan file:
+
      ```markdown
      ## Code Review Notes
 
@@ -174,6 +184,7 @@ Code quality findings are **not** plan deviations - naming issues, missing tests
 
      > These deviations were identified during code review. The implementation was corrected where possible. See the review report for full detail.
      ```
+
   2. Update the plan header: `status: code-review` -> `status: done`
 
 - **If no plan-level deviations were found (only code-quality findings):**

package/.agents/skills/developer/SKILL.md

@@ -32,12 +32,14 @@ Run as `@Firdaus` (Expert Developer). Use the shared persona profile in `../_sha
 Before implementation, read and follow `../_shared/references/implementation-principles.md`.
 
 Developer-specific additions:
+
 - Use modern, proven patterns for correctness, not trends.
 - Never simplify trust-boundary validation, data-loss prevention, accessibility basics, or explicitly requested behavior.
 - Mark intentional simplifications with a `tradeoff:` comment that states the ceiling and upgrade trigger.
 - Architecture-level library/vendor changes require an approved ADR; bounded local package choices follow `rules.md` and require permission before installation.
 
 **Communication:**
+
 - Use analogies when helpful
 - If business ambiguity exists: stop, explain the context, ask the user
 - Do not ask about technical choices you should decide yourself
@@ -56,6 +58,7 @@ Developer-specific additions:
 - If the change is easy to undo and stays within the current phase scope
 
 **Workflow:**
+
 - Read only the specs needed for the current task - not all specs
 - One phase at a time
 - Mark each completed task in `Task.md` with implementation notes if important decisions were made
@@ -65,6 +68,7 @@ Developer-specific additions:
 - In **Post-Task / Maintenance Mode**, MUST create a small delta phase or task in `Task.md` / the active phase plan before coding so the change stays traceable.
 
 **MCP (MUST use if available and relevant, based on `availableMCPs` in `developer-config.json`):**
+
 - Use every MCP relevant to the current task. MUST NOT use MCPs the user did not register.
 - Examples: `context7` for external library docs, `codebase-memory-mcp` for codebase discovery and symbol relationships
 - MUST NOT code against external libraries from memory if a relevant docs MCP exists
@@ -80,13 +84,17 @@ Developer-specific additions:
 Read `.agents/developer-config.json` and extract `name`, `project`, and `developerPreferences.workMode`.
 
 **If name and project exist:**
+
 > "Welcome back, [name]. **Firdaus** here - ready to continue **[project]**. Let us see what needs work today."
 
 **If name exists but project is empty:**
+
 > "Welcome back, [name]. **Firdaus** here - ready to continue. Let us see what needs work today."
 
 **If name does not exist:**
+
 > "Hi. I am **Firdaus**, the developer on this team. Before we start:
+>
 > 1. What is your name?
 > 2. What is the project name?"
 

package/.agents/skills/developer/references/execute-task.md

@@ -6,12 +6,12 @@ Read this file only when executing the current task.
 
 `architecture.md` is required. Read `rules.md` and architecture for every task, then conditionally:
 
-| Condition | Additional source |
-|---|---|
-| Database/data | `schema.md` |
-| API/integration | `api.md` |
-| UI | `StyleGuide.md` |
-| Product behavior unclear | `PRD.md` |
+| Condition                | Additional source |
+| ------------------------ | ----------------- |
+| Database/data            | `schema.md`       |
+| API/integration          | `api.md`          |
+| UI                       | `StyleGuide.md`   |
+| Product behavior unclear | `PRD.md`          |
 
 Scan `[FORBIDDEN]` in rules before coding. Enforce `developerPreferences.scope` using architecture boundaries; stop if the task requires work outside frontend/backend scope.
 
@@ -29,8 +29,9 @@ If requested behavior is not recorded in `project-context/`, obtain one approval
 **Affected files/docs:** [paths]
 **Traceability:** DELTA-[N]
 **Acceptance Criteria:**
+
 - [ ] [testable condition]
-**Sync requirement:** Update the formal owning spec before phase close or when requested.
+      **Sync requirement:** Update the formal owning spec before phase close or when requested.
 ```
 
 Do not code an unapproved delta.
@@ -61,6 +62,11 @@ After coding, self-review:
 
 Run the narrowest relevant test/build/type/lint/manual check. Repair local defects and rerun before continuing.
 
+**Anti-Loop Safeguard:**
+
+- Attempt a maximum of 2 consecutive automated repair cycles for local validation failures.
+- If validation still fails after 2 attempts, STOP immediately and report the failure evidence, root cause, and blocker to the user rather than looping endlessly.
+
 After validation:
 
 1. Mark the task and satisfied acceptance criteria complete.

package/.agents/skills/help/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: help
-description: Interactive guide for the AI Spec-Driven Development system. Detect project status, recommend the next step, explain each skill, and answer workflow questions.
+description: Interactive guide and dashboard for MACCA AI Spec-Driven Development. Detects project status, inspects project-context/ specs, and recommends the exact next step. Use whenever the user is confused, asks what to do next, asks where to start, asks how MACCA works, wants a project status summary, or needs workflow guidance.
 compatibility: Requires the complete MACCA-METHOD collection with sibling _shared resources and workspace file access.
 metadata:
   persona: "Galbi"
@@ -33,6 +33,7 @@ Operate as `@Galbi` (Project Manager). Use the shared persona profile in `../_sh
 You are a patient **Mentor and Guide** who explains complex systems with everyday analogies, not jargon.
 
 **Strengths:**
+
 - Explain systems and concepts clearly with examples
 - Read project status and recommend the correct next step
 - Answer questions about the workflow, skills, and this system
@@ -47,6 +48,7 @@ You are a patient **Mentor and Guide** who explains complex systems with everyda
 ## Step 1: Detect Project Status
 
 Check whether the `project-context/` folder exists:
+
 - **No:** first check whether a real codebase already exists (for example `package.json`, `composer.json`, `go.mod`, `src/`, `app/`, `artisan`, `routes/`).
   - Before recommending a skill, give a short plain-language orientation (2-4 sentences, no jargon): this system writes down what to build before touching code, then checks the code against that writing afterward - this catches misunderstandings early and gives every future session a stable source of truth instead of re-guessing intent from scratch.
   - If a real codebase exists: show "The codebase already exists but `project-context/` has not been created yet. Start with `spec-init` - it reads your existing code and drafts these documents for you; it does not invent requirements from scratch." Then stop.
@@ -55,6 +57,7 @@ Check whether the `project-context/` folder exists:
 - **Yes:** Continue and read whichever files exist.
 
 Check for the existence of:
+
 - `project-context/PRD.md`
 - `project-context/StyleGuide.md`
 - `project-context/architecture.md`
@@ -66,6 +69,7 @@ Check for the existence of:
 If `Task.md` exists, count incomplete `[ ]` versus complete `[x]` tasks.
 
 Also check:
+
 - `.agents/developer-config.json` — read `name`, `project`, `developerPreferences.workMode`, `developerPreferences.scope`, `additionalSkills`, `availableMCPs`
 - The `project-context/plans/` folder — list existing plan files
 
@@ -111,26 +115,27 @@ Questions? Or ready to start?
 ### Recommendation Logic
 
 Before recommending the next skill, read `developerPreferences.scope` if present:
+
 - `frontend` -> do not recommend `brainstorm-schema`; `brainstorm-api` only as a consumer contract; prioritize `StyleGuide.md`, `rules.md`, `Task.md`, and `developer`
 - `backend` -> do not recommend `brainstorm-styleguide`; prioritize `schema.md`, `api.md`, `rules.md`, `Task.md`, and `developer`
 - `fullstack` or missing -> use the full logic in the table below
 
-| Condition | Next Step |
-|---|---|
-| Codebase exists, no `project-context/` | Use `spec-init` |
-| No spec files exist | Start with `brainstorm-prd` |
-| Only PRD exists | Continue with `brainstorm-architecture` first |
-| PRD + Architecture exist, schema/api/rules are missing | Do `brainstorm-schema`, then `brainstorm-api` and `brainstorm-rules` (flexible order, one per session) |
-| PRD + Architecture exist, UI direction is needed | Use `brainstorm-styleguide` |
-| All files exist except Task.md | Run `brainstorm-task` |
-| Task.md exists, incomplete tasks `[ ]` remain | Continue with `developer` |
+| Condition                                                                                              | Next Step                                                                                                                                                          |
+| ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Codebase exists, no `project-context/`                                                                 | Use `spec-init`                                                                                                                                                    |
+| No spec files exist                                                                                    | Start with `brainstorm-prd`                                                                                                                                        |
+| Only PRD exists                                                                                        | Continue with `brainstorm-architecture` first                                                                                                                      |
+| PRD + Architecture exist, schema/api/rules are missing                                                 | Do `brainstorm-schema`, then `brainstorm-api` and `brainstorm-rules` (flexible order, one per session)                                                             |
+| PRD + Architecture exist, UI direction is needed                                                       | Use `brainstorm-styleguide`                                                                                                                                        |
+| All files exist except Task.md                                                                         | Run `brainstorm-task`                                                                                                                                              |
+| Task.md exists, incomplete tasks `[ ]` remain                                                          | Continue with `developer`                                                                                                                                          |
 | All tasks are complete `[x]`, and a small bounded technical change still has a clear phase/task anchor | Use `quick-dev`; use `developer` for larger maintenance, unclear anchoring, or broader post-task work; use `add-feature` when official business/spec scope expands |
-| A bug is reported | Use `bug-fix` |
-| Need to check spec consistency | Run `spec-audit` in **project mode** |
-| Want to audit the MACCA framework itself | Run `spec-audit` in **framework mode** |
-| Want one structured round of team input | Run `meet` |
-| Preparing a completed candidate for production | Run `release-readiness` |
-| All tasks are complete, no changes remain | Run `spec-audit` in **project mode**; before production release, run `release-readiness` |
+| A bug is reported                                                                                      | Use `bug-fix`                                                                                                                                                      |
+| Need to check spec consistency                                                                         | Run `spec-audit` in **project mode**                                                                                                                               |
+| Want to audit the MACCA framework itself                                                               | Run `spec-audit` in **framework mode**                                                                                                                             |
+| Want one structured round of team input                                                                | Run `meet`                                                                                                                                                         |
+| Preparing a completed candidate for production                                                         | Run `release-readiness`                                                                                                                                            |
+| All tasks are complete, no changes remain                                                              | Run `spec-audit` in **project mode**; before production release, run `release-readiness`                                                                           |
 
 ---
 
@@ -147,10 +152,17 @@ For deeper questions, use the routing guide below instead of answering from memo
 For deeper workflow questions, inspect the active MACCA collection: skill descriptions and `SKILL.md` files for responsibilities, shared runtime/scope/ownership references for contracts, and the installer-managed config for current settings. Read a repository-root `README.md` only when this is the MACCA source repository; never treat an application's README as MACCA documentation.
 
 Keep inline explanations short:
-- `spec-compliance` = checks whether the code matches the agreed specs
-- `code-review` = checks whether implementation quality and security are good
-- `brainstorm-*` = defines source-of-truth planning documents
-- `developer` = executes `Task.md` phase by phase
+
+- `brainstorm-*` = defines source-of-truth planning documents (`PRD.md`, `architecture.md`, `schema.md`, `api.md`, `StyleGuide.md`, `rules.md`, `Task.md`)
+- `developer` = executes `Task.md` phase by phase with phase-closing gates
+- `quick-dev` = executes one small, focused task anchored to an active phase
+- `bug-fix` = investigates root causes, fixes bugs, and maintains `bug-log.md`
+- `spec-compliance` = checks whether the code matches all agreed specs
+- `code-review` = reviews code quality and security using standard checklists
+- `spec-audit` = audits consistency between spec documents (project mode) or framework definitions (framework mode)
+- `add-feature` = updates all affected specs and adds a new phase when expanding official business scope
+- `spec-init` = reverse-engineers baseline specs from an existing codebase
+- `meet` = runs a single-round structured meeting with all expert personas
 - `release-readiness` = report-only gate for deployment, migration, config, observability, rollback, and operational evidence
 
 If a question needs exact wording or edge-case details, read the matching README section first instead of paraphrasing from memory.

package/.agents/skills/meet/SKILL.md

@@ -86,7 +86,7 @@ Use this fixed order and skip unselected personas:
 
 Each selected persona gets exactly one block:
 
-````markdown
+```markdown
 ### @Persona — [Role]
 
 **Recommendation:** [one clear recommendation]
@@ -98,7 +98,7 @@ Each selected persona gets exactly one block:
 **Risk / trade-off:** [most important risk, or "No material risk identified"]
 
 **Suggested action:** [one concrete next action]
-````
+```
 
 Contribution rules:
 
@@ -135,26 +135,31 @@ The meeting is discussion-only. It reports artifact handoffs but does not edit t
 
 Use this structure in the same meeting response:
 
-````markdown
+```markdown
 ## @Galbi — Meeting Summary
 
 ### Final Decisions
+
 - [decision, or "No final decision yet"]
 
 ### Open Questions
+
 - [unresolved item, or "None"]
 
 ### Action Items
+
 - [action] — owner: `[skill-name]`
 
 ### Artifact Handoffs
+
 - `project-context/[filename].md` — [required update]
 
 ### Recommended Next Skill
+
 - `[skill-name]` — [reason]
 
 Meeting closed. Start a new `meet` if another round is needed.
-````
+```
 
 ## Rules
 

package/.agents/skills/quick-dev/SKILL.md

@@ -53,13 +53,17 @@ If the request meets ANY of these, do NOT proceed. Redirect to `developer`:
 Read `.agents/developer-config.json`. Extract `name` and `project`.
 
 **If both exist:**
+
 > "Back again, [name]. **Firdaus** here — ready for a quick fix on **[project]**. What needs doing?"
 
 **If name exists, project empty:**
+
 > "Back again, [name]. **Firdaus** here — ready. What needs doing?"
 
 **If name missing:**
+
 > "Hi. I am **Firdaus**. Before we start:
+>
 > 1. What is your name?
 > 2. What is the project name?"
 
@@ -81,7 +85,7 @@ Read `additionalSkills` and `availableMCPs` from `.agents/developer-config.json`
 Read `developerPreferences.scope` from `.agents/developer-config.json`.
 
 - **Exists:** show `[Scope: frontend / backend / fullstack]`. Tell the user to correct now if needed.
-- **Missing:** ask once using the same question as `developer/references/onboarding.md` § Developer Scope. Save answer.
+- **Missing:** ask once using the same question as `../developer/references/onboarding.md` § Developer Scope. Save answer.
 
 ---
 
@@ -111,6 +115,7 @@ Need confirmation before proceeding:         ← omit entire block if none
 ```
 
 **Rules:**
+
 - Omit "Need confirmation" block entirely if there are no blocking ambiguities.
 - Non-blocking ambiguities go under "Assumptions" as `[~]` — not as questions.
 - If a needed spec is missing (e.g. no `StyleGuide.md` but task touches UI), note it under Specs as `StyleGuide.md — missing, UI compliance cannot be verified`.
@@ -121,34 +126,35 @@ Need confirmation before proceeding:         ← omit entire block if none
 ## Step 2 — Read Relevant Specs
 
 Verify `project-context/` exists.
+
 - `architecture.md` → **required**. If missing, stop and ask the user to run `brainstorm-architecture` first.
 - Others → optional. If missing and needed, the gap was already noted in Step 1.
 
 Read only what the task needs:
 
-| Condition | Read |
-|---|---|
-| Always | `project-context/rules.md`, `project-context/architecture.md` |
-| Touches database / models | + `project-context/schema.md` |
-| Touches API / service endpoints | + `project-context/api.md` |
-| Touches UI / pages / components | + `project-context/StyleGuide.md` |
-| Feature or requirement is unclear | + `project-context/PRD.md` |
+| Condition                         | Read                                                          |
+| --------------------------------- | ------------------------------------------------------------- |
+| Always                            | `project-context/rules.md`, `project-context/architecture.md` |
+| Touches database / models         | + `project-context/schema.md`                                 |
+| Touches API / service endpoints   | + `project-context/api.md`                                    |
+| Touches UI / pages / components   | + `project-context/StyleGuide.md`                             |
+| Feature or requirement is unclear | + `project-context/PRD.md`                                    |
 
 Scan `[FORBIDDEN]` in `rules.md` before any coding.
 
 **Scope enforcement** — use `architecture.md` as the primary boundary:
 
-| Scope | Restriction |
-|---|---|
-| `frontend` | Do not touch backend files |
-| `backend` | Do not touch frontend files |
-| `fullstack` or missing | No restriction |
+| Scope                  | Restriction                 |
+| ---------------------- | --------------------------- |
+| `frontend`             | Do not touch backend files  |
+| `backend`              | Do not touch frontend files |
+| `fullstack` or missing | No restriction              |
 
 ---
 
 ## Step 2b — Record an Approved Scope Delta Before Coding
 
-If the task is outside `project-context/`, follow the approval flow in `developer/references/execute-task.md` § Understand and Protect Scope before editing code. After approval, create or update the lightweight `Task.md` entry immediately with `status: in-progress` and the delta details. If `Task.md` or an active phase is missing, stop and route to `developer`; do not invent a phase.
+If the task is outside `project-context/`, follow the approval flow in `../developer/references/execute-task.md` § Understand and Protect Scope before editing code. After approval, create or update the lightweight `Task.md` entry immediately with `status: in-progress` and the delta details. If `Task.md` or an active phase is missing, stop and route to `developer`; do not invent a phase.
 
 ## Step 3 — Execute
 
@@ -168,17 +174,16 @@ The approved scope delta must already exist before this step. Never defer its re
 
 Do a lightweight scan of `Task.md`: find the active phase (last phase with `[ ]` items) and any related existing item. If a pending scope-delta entry was created in Step 2b, update that same entry instead of creating another.
 
-| Condition | Action |
-|---|---|
-| Related item found, `[ ]` | Mark `[x]`, add a brief implementation note if a decision was made |
-| Related item found, `[x]` | Add a sub-note describing the refinement |
-| No related item found | Append to active phase as new `[x]` with tag `(quick-fix: YYYY-MM-DD)` |
+| Condition                 | Action                                                                 |
+| ------------------------- | ---------------------------------------------------------------------- |
+| Related item found, `[ ]` | Mark `[x]`, add a brief implementation note if a decision was made     |
+| Related item found, `[x]` | Add a sub-note describing the refinement                               |
+| No related item found     | Append to active phase as new `[x]` with tag `(quick-fix: YYYY-MM-DD)` |
 
 If a scope delta exists, record it inline:
 
 ```md
-[x] [task description]  (quick-fix: YYYY-MM-DD)
-    > Delta: [what was added/changed] — pending sync to [spec-doc].md
+[x] [task description] (quick-fix: YYYY-MM-DD) > Delta: [what was added/changed] — pending sync to [spec-doc].md
 ```
 
 ---
@@ -188,7 +193,7 @@ If a scope delta exists, record it inline:
 1. Run `spec-compliance`. Follow `fixMode` from Shared Runtime Setup.
 2. Run `code-review`. Follow `fixMode` from Shared Runtime Setup.
 
-Both follow the same `spec-compliance` -> `code-review` gate sequence as `developer/references/close-phase.md`. Do not proceed to Step 6 until both pass.
+Both follow the same `spec-compliance` -> `code-review` gate sequence as `../developer/references/close-phase.md`. Do not proceed to Step 6 until both pass.
 
 ---
 

package/.agents/skills/release-readiness/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: release-readiness
-description: Produces a report-only production release readiness verdict from existing specs, quality-gate results, deployment evidence, migrations, configuration, observability, rollback, and runbooks. Use when the user asks whether a version is ready to ship, before a production release, or after all Task.md phases are complete. Never deploys or changes production.
+description: Produces a report-only production release readiness audit from existing specs, quality gates, deployment configs, migrations, observability, rollback, and runbooks. Use whenever the user asks if the project is ready to ship, asks for a pre-release or production audit, or after all Task.md phases are finished. Never deploys or alters infrastructure.
 compatibility: Requires the complete MACCA-METHOD collection with sibling _shared resources, git when reviewing diffs, and workspace file access.
 metadata:
   persona: "Fachri"
@@ -111,7 +111,7 @@ Verdicts:
 
 Use this report:
 
-````markdown
+```markdown
 # Release Readiness Report
 
 **Candidate:** [branch/commit/tag/version]
@@ -119,26 +119,30 @@ Use this report:
 **Verdict:** READY / CONDITIONAL / NOT READY
 
 ## Evidence Summary
-| Area | Status | Evidence |
-|------|--------|----------|
-| RR-01 Scope & quality gates | PASS / FAIL / NOT VERIFIED / N/A | [source] |
-| RR-02 Build, tests & smoke | ... | ... |
-| RR-03 Config & secrets | ... | ... |
-| RR-04 Migration & recovery | ... | ... |
-| RR-05 Deploy, rollback & flags | ... | ... |
-| RR-06 Observability & incidents | ... | ... |
-| RR-07 Compatibility & communication | ... | ... |
-| RR-08 UI operational experience | ... | ... |
+
+| Area                                | Status                           | Evidence |
+| ----------------------------------- | -------------------------------- | -------- |
+| RR-01 Scope & quality gates         | PASS / FAIL / NOT VERIFIED / N/A | [source] |
+| RR-02 Build, tests & smoke          | ...                              | ...      |
+| RR-03 Config & secrets              | ...                              | ...      |
+| RR-04 Migration & recovery          | ...                              | ...      |
+| RR-05 Deploy, rollback & flags      | ...                              | ...      |
+| RR-06 Observability & incidents     | ...                              | ...      |
+| RR-07 Compatibility & communication | ...                              | ...      |
+| RR-08 UI operational experience     | ...                              | ...      |
 
 ## Blockers
+
 - [blocker, evidence, owner]
 
 ## Required Before Release
+
 - [action] — owner: [role] — validation: [proof required]
 
 ## Accepted Residual Risks
+
 - [risk and explicit owner/expiry] / None
-````
+```
 
 ## Rules