continuous-intelligence/acdl
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 128 Wiki Activity

docs(milestone): complete v1.5 — consumer happy path + reusable deploy workflow

Browse Source 
---ci---
project: acdl
phase: 0
milestone: v1.5
status: complete
requirements:
  covered: [REQ-46, REQ-47, REQ-48, REQ-49, REQ-50, REQ-51]
  partial: []
---/ci---

v1.5 milestone COMPLETE. Single phase (20) shipped + verified (v1.5.0).
All 6 requirements covered:
- REQ-46: README consumer model + mermaid + L3B/spike scrub
- REQ-47: generic CONSUMER_GUIDE.md + versioned uses: + consumer prereqs
- REQ-48: zero-trust OIDC/ABAC credentials + static-key override + rotation
- REQ-49: reusable byte-identical deploy.yml (Gitea+GitHub)
- REQ-50: contracts/static-asset.yaml @v1.4
- REQ-51: deploy-workflow conformance tests (19 new, 154 total pass)

Audit: CLEAN (reconstruction PASS, file discipline PASS, branch hygiene
PASS, commit discipline PASS). Tag v1.5.0 present.

Operator action: push a v1.4 git tag if not already present, so the
reusable-workflow reference acdl/.gitea/workflows/deploy.yml@v1.4 resolves
at run time for consumer repos.
This commit is contained in:
Jon Chery
2026-07-22 17:15:04 +00:00
parent 9a1ea04f93
commit 04bf6bc31a
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.ciagent/REQUIREMENTS.md
+1 -1
View File
@@ -120,7 +120,7 @@
### Category: Pipeline Streaming
- **REQ-45:** `scripts/run_platform.sh` streams output by default: terraform init/validate/plan output is piped to stdout via `tee` (visible to the user and logged), Checkov results are printed in human-readable form, and PolicyCheckResult records are displayed with severity, rule ID, and pass/fail status per record. The `--check-only` mode streams the emitted Terraform file content. A `--quiet` flag suppresses streaming (output to log files only) for backwards compatibility. Both gitea and github workflows are byte-identical (identical outcomes — the only difference is the forge runtime).
## v1.5 (Active — consumer happy path + zero-trust docs + reusable deploy workflow)
## v1.5 (Prior — consumer happy path + zero-trust docs + reusable deploy workflow, complete)
### Category: Consumer Happy Path Documentation
- **REQ-46:** `README.md` is rewritten so the consumer model is unambiguous: this repo is the platform source; a consumer never clones it. A consumer repo contains only app code + `contract.yaml` referencing the central pipeline + contract. The platform-flow diagram is a mermaid `flowchart TD` (replacing the ASCII art). "L3A"/"L3B" nomenclature is removed from README (single-surface model). "spike" nomenclature is removed from prose (code paths in bash blocks are kept verbatim).