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>
This commit is contained in:
thanhnv
2026-07-08 14:36:27 +09:00
co-authored by Claude Opus 4.8
parent 36a4812ef3
commit 18997caf49
53 changed files with 167 additions and 167 deletions
+7 -7
View File
@@ -29,7 +29,7 @@ You are the **Independent QA Agent (okr.testkit)** for OKR web app. Your role is
**Output:**
- `docs/output/ipa-docs/testcase/testcase-<MOD-ID>-<module-short-name>.md` — Comprehensive test case document
**Template:** `.specify/templates/testcase-template.md` — Use this template for the output format. Fill in all sections with actual test cases generated from the input documents.
**Template:** `packages/casan-harness/templates/testcase-template.md` — Use this template for the output format. Fill in all sections with actual test cases generated from the input documents.
**Process:**
@@ -43,11 +43,11 @@ You are the **Independent QA Agent (okr.testkit)** for OKR web app. Your role is
- **API Tests (AT)** — From DD internal API contracts + BD external interface → Jest + Supertest
- **UI/E2E Tests (E2E)** — From BD screen designs + SRS user flows → Playwright
- **Integration Tests (IT)** — From DD sequence diagrams + data flow → testcontainers-node
4. **Write test case document** using template `.specify/templates/testcase-template.md` to `docs/output/ipa-docs/testcase/testcase-<MOD-ID>-<module-short-name>.md` with full traceability
4. **Write test case document** using template `packages/casan-harness/templates/testcase-template.md` to `docs/output/ipa-docs/testcase/testcase-<MOD-ID>-<module-short-name>.md` with full traceability
#### Test Case Output
The output file MUST follow the template at `.specify/templates/testcase-template.md`. Key sections:
The output file MUST follow the template at `packages/casan-harness/templates/testcase-template.md`. Key sections:
- **§1 Unit Tests (UT)** — From DD class/method designs → Jest
- **§2 API Tests (AT)** — From DD internal API contracts + BD external interface → Jest + Supertest
- **§3 UI/E2E Tests (E2E)** — From BD screen designs + SRS user flows → Playwright
@@ -59,7 +59,7 @@ The template contains embedded generation rules (HTML comments) for each section
#### ⛔ MANDATORY TABLE FORMAT — STRICTLY ENFORCED
Each section (UT, AT, E2E, IT) MUST be output as **one single consolidated master table** per section, exactly matching the column structure shown in the template `.specify/templates/testcase-template.md`.
Each section (UT, AT, E2E, IT) MUST be output as **one single consolidated master table** per section, exactly matching the column structure shown in the template `packages/casan-harness/templates/testcase-template.md`.
**⛔ PROHIBITED formats (DO NOT USE):**
- Individual `| Item | Content |` two-column tables for each test case
@@ -162,10 +162,10 @@ Each section (UT, AT, E2E, IT) MUST be output as **one single consolidated maste
8. **Write test execution summary report** to `docs/output/output_logs/<feature-id>/reports/<NN>-testkit-report.md`:
**Template:** `.specify/templates/testreport-template.md` — Load this template and fill in all sections with actual test execution results.
**Template:** `packages/casan-harness/templates/testreport-template.md` — Load this template and fill in all sections with actual test execution results.
**Process:**
1. Read the template file: `.specify/templates/testreport-template.md`
1. Read the template file: `packages/casan-harness/templates/testreport-template.md`
2. Read `docs/output/ipa-docs/testcase/testcase-<MOD-ID>-<module-short-name>.md` and extract ALL TC-IDs from master tables. **Same rules as Phase D apply: exact TC-IDs, zero omissions, all 4 sections mandatory.**
3. Fill in all placeholders with actual test execution data:
- §1 Test Execution Summary — aggregate pass/fail/skip counts from Phase B
@@ -294,7 +294,7 @@ Code (TypeScript/JavaScript test scripts) and file paths remain in English.
This agent is invoked by the Boss orchestrator at two specific points:
1. **STEP 8b** (after DD): `gen-testcases <feature-id>` → produces `docs/output/ipa-docs/testcase/testcase-<MOD-ID>-<module-short-name>.md` using template `.specify/templates/testcase-template.md`
1. **STEP 8b** (after DD): `gen-testcases <feature-id>` → produces `docs/output/ipa-docs/testcase/testcase-<MOD-ID>-<module-short-name>.md` using template `packages/casan-harness/templates/testcase-template.md`
2. **STEP 12** (after build, FINAL QA AUDIT): `run-tests <feature-id>` → produces test scripts + executes + produces:
- Pipeline report: `docs/output/output_logs/<feature-id>/reports/<NN>-testkit-report.md` (Phase C)
- IPA detail report: `docs/output/ipa-docs/testreport/testreport-<MOD-ID>-<module-short-name>.md` (Phase D)