update first - 84

This commit is contained in:
thanhnv
2026-06-30 02:21:39 +09:00
commit 07ac1bdcdd
561 changed files with 88164 additions and 0 deletions
@@ -0,0 +1,58 @@
# Report Hard Gate Protocol
## ⛔ MANDATORY BEFORE NEXT STEP
After each step completes, the boss MUST enforce this gate before proceeding:
```
STEP N completes
│
▼
[GATE A] CHECK: Are all primary artifact files physically present on disk?
│ Use Glob tool for each path listed in artifacts: of STEP-RESULT block.
│
├─ ANY MISSING → BLOCKED. Do NOT mark step COMPLETE.
│ Re-invoke the sub-agent with explicit instruction:
│ "File <path> was not written. Re-generate and write it now."
│ Write boss log: [ARTIFACT GATE] STEP N — missing: <path>. Re-invoking.
│ (Counts against gate-retry-protocol max retries)
│
└─ ALL PRESENT → GATE A PASSED
│
▼
[GATE B] CHECK: Does the phase report file EXIST?
│
├─ NO → BLOCKED. Generate the report NOW using data already produced.
│ Write boss log: [REPORT GATE] STEP N — report generated (late).
│
└─ YES → CHECK: Does report contain ALL required sections?
│
├─ NO → ADD missing section inline. Re-write file.
│ Write boss log: [REPORT GATE] STEP N — patched missing section: <name>.
│
└─ YES → CHECK: Any unresolved [NEEDS CLARIFICATION] markers?
│
├─ YES → Auto-resolve every item. Patch report.
│ Write boss log: [REPORT GATE] STEP N — auto-resolved N TBC items.
│
└─ NO → ✅ BOTH GATES PASSED → Advance to STEP N+1
```
> **Rule:** `pipeline-context.yaml` step status may only be set to `COMPLETE` after GATE A and GATE B both pass. Setting it earlier — based solely on the sub-agent's STEP-RESULT claim — is forbidden.
## Required Report Sections (all steps)
1. `## Summary` — brief phase outcome
2. `## Artifacts Produced` — list of all files written (with paths)
3. `## [AUTO-RESOLVED] Assumptions` — auto-resolved clarifications
4. `## [NEEDS CLARIFICATION] Items` — remaining unresolved items (should be empty in built-in mode)
5. `## Issues & Retries` — record of rejected verdicts and retry attempts
6. `## Next Step` — what step follows and what inputs it will receive
## Step-Specific Additional Sections
| Step | Additional Required Section |
|------|-----------------------------|
| STEP 4 | `## QA Summary` — full table of questions + auto-resolved answers |
| STEP 10 | `## Test Results` — pass/fail table per test class, Istanbul/c8 coverage % | `## Screen Verification` — per-screen: ID, HTTP status, render OK/FAIL |
| STEP 13 | `## Launch Status` — FE/BE startup, DB seed count, screen accessibility |