thanhnvandClaude Opus 4.8
36a4812ef3
Standard production layout: the OKR app (was nested under AINative_OKR_CASAN5/) is now
the repository root. No more wrapper directory.
- Promote AINative_OKR_CASAN5/* -> repo root (backend/ frontend/ packages/ apps/
.specify/ docs/ infra/ nginx/ scripts/ + configs). Merge tool dirs: .gitea (kept the
active deploy ci.yml, added harness-ci.yml + runbooks), .claude (agents/commands +
launch.json), .github moved up.
- Remove redundant: 00_SUBMISSION_PACKAGE, scattered root notes (FPT_CASAN_Full.md,
tu-tuong-casan.md, casan-tu-sinh..., casan_harness_assessment.md, source-review...,
README_CASAN5_REFINED.md), casan-next-plans/ and optimize-docs/ (competition/planning
artifacts — roadmap + design history preserved in git log / commit messages).
- Update all references to the old layout:
- .gitea/workflows/{ci,harness-ci}.yml, .github/workflows/{ci,deploy}.yml:
working-directory .; drop AINative_OKR_CASAN5/ prefix; .specify/{tests,scripts}
-> packages/casan-harness/... (.specify/logs state kept)
- .claude/launch.json, .gitea/*-runbook.md: path prefixes
- CLAUDE.md, README.md: docs/input -> apps/okr/domain/input
- policy-bundle.yaml: 8 policy paths -> packages/casan-harness/...; manifest re-signed
- secrets-scan.sh: fixture excludes -> new package/domain paths.
Full gate from the new root: PASS=64 FAIL=0 SKIP=3.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.8 KiB
1.8 KiB
Gate Retry Protocol (No-Halt Mode)
When any review gate returns REJECTED, the pipeline does NOT stop.
Gate Retry Loop
REJECTED verdict received
│
├─ Extract CRITICAL issues list from review report
├─ Write [ISSUE] entry in boss log
├─ Increment retry counter for this gate
│
├─ If retry counter ≤ 5:
│ Invoke fix agent with CRITICAL issues list
│ Re-invoke review agent
│ Evaluate new verdict → repeat if still REJECTED
│
└─ If retry counter > 5:
Write [ESCALATION] entry in boss log
Mark step as "ESCALATED — Partial Pass"
Continue pipeline with known limitations documented
Fix Agent Selection per Gate
| Gate Step | Review Agent | Fix Agent | Fix Instruction |
|---|---|---|---|
| Step 5 | okr.reviewspec |
speckit.specify |
"Fix CRITICAL spec issues: . Re-generate affected sections of spec.md." |
| Step 7 | okr.reviewplan |
speckit.plan |
"Fix CRITICAL plan conformance issues: . Update plan.md." |
| Step 11 | okr.reviewcode |
speckit.implement |
"Fix CRITICAL code review issues: . Apply minimal targeted fixes." |
| Step 12 | okr.testkit |
speckit.implement |
"Fix CRITICAL test failures tracing to SRS/BD/DD: ." |
BACK-TO-PLAN Fix Cycle (Step 12 only)
When Step 12 tests FAIL, unlike other gates, this triggers a full fix cycle from STEP 6:
- Extract ALL failed test cases with design document references
- Write
[BACK-TO-PLAN]entry in boss log - Re-invoke pipeline from STEP 6 → 7 → 8 → 8b → 9 → 10 → 11 → 12
- Max 3 full cycles. After 3 cycles: write
[ESCALATION], proceed to Step 13 anyway.