Validates the v0.2 milestone specification against the deferred-v0.2
requirements in ROADMAP.md and the requirement status table. Updates:
- ROADMAP.md: v0.2 marked in-progress with 4 phases (P01 mTLS, P02
multi-node scheduling, P03 gosec+govulncheck, P04 iter.Seq). Adds
target milestone tag (v0.3.0) and per-phase tags (v0.2.1..v0.2.4)
per the feature-milestone promotion rule and the RELEASE_POLICY.md
standing rule on per-phase releases.
- REQUIREMENTS.md: flips REQ-011, REQ-014, REQ-022, REQ-023 from
'Deferred (v0.2)' to 'Pending (v0.2 PXX)'. Adds a v0.2 summary
section.
No code or schema changes. Pure SPECIFY output per run.md Step 3.
CLARIFY and RESEARCH follow.
---ci---
project: orca
phase: 0
milestone: v0.2
status: specify
---/ci---
Layer-3 security audit during P07 EXECUTE found that .env (containing
GITEA_TOKEN) was committed in 0cba1aa during P00 and remained in git
history. The pre-P07 .gitignore only excluded .env.local, not .env.
This commit:
1. Adds .env to .gitignore alongside .env.local (forward fix — prevents
future re-tracking).
2. Documents the pre-existing leak in .ciagent/PHASE7_SECURITY_AUDIT.md
with mitigation steps and required human actions (token rotation,
history rewrite, access-log audit, CI secret scanning).
The backfill script itself (commit de69788) does not leak the secret: it
sources .env from disk and never echoes or passes it on the command line.
The leak is upstream of P07 and is documented as P0 for the human to
remediate out-of-band.
---ci---
project: orca
phase: 7
milestone: v0.1
status: execute
version: v0.1.7
requirements:
covered: [REQ-007]
partial: []
---/ci---