Commit Graph

8 Commits

Author SHA1 Message Date
ciagent 907f25e20d docs(init): validate v0.2 specification
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---
2026-06-03 20:52:01 +00:00
ciagent b1b2e3dcb6 fix(P07): harden .gitignore for .env and document pre-existing secret leak
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---
2026-06-03 20:42:39 +00:00
cloudinit-bot be9afa2d2c ship: v0.1 Foundation milestone complete (#1) 2026-06-03 20:08:57 +00:00
Jon Chery 55aae5347e chore(P00): rename orch-engine to orca, configure gitea + coreci (v0.1)
---ci---
project: orca
phase: 0
milestone: v0.1
status: execute
---/ci---
2026-06-03 11:36:32 +00:00
Jon Chery 0cba1aa5fe chore(P00): set autonomy level to full
---ci---
project: orch-engine
phase: 0
milestone: v1.0
status: execute
---/ci---
2026-06-03 11:18:58 +00:00
Jon Chery e2e77e79b9 chore(P00): quick task - populate config.json with backlog reference
---ci---
project: orch-engine
phase: 0
milestone: v1.0
status: execute
lessons:
  - Referenced backlog project's config.json (also Go 1.25+) to establish proper schema including autonomy, personas, parallelization, sessions, ci, repository, and commands sections
---/ci---
2026-06-03 11:15:12 +00:00
Jon Chery 8c086def69 chore(config): populate ciagent config with standard settings
---ci---
project: orch-engine
phase: 0
milestone: v1.0
status: execute
---/ci---
2026-06-03 11:08:48 +00:00
Jon Chery 97f437f9ef docs(init): initialize orch-engine (6 phases)
---ci---
project: orch-engine
phase: 0
milestone: v1.0
status: specify
decisions:
  - id: D-001
    decision: Use single-project mode for initial setup
    rationale: Simplified configuration for the initial phase
    confidence: 1.0
    alternatives: []
---/ci---

Specification: Build an offline/CLI-first orchestration engine.
Requirements: Simplicity, AI-first, Offline-first, CLI-first, prioritize security/bug-fixes over features, Go 1.25+.
Constraints: Simpler than Nomad, far simpler than Kubernetes.
Out of scope: K8s complexity.
2026-06-03 10:59:05 +00:00