---ci---
phase: 1
milestone: v1.0
status: execute
persona: backend-engineer
task: T-2.3
requirements:
covered: [REQ-12]
---/ci---
Wave 2, task T-2.3. contracts-repo/.gitea/workflows/issue-to-contract.yml
is the reference copy kept in the acdl repo (Phase 04 pushes it to the
actual acdl-contracts repo). Skeleton: on: issues [opened]; one job
parse-and-trigger with explicit placeholder steps. The header comment
documents the cross-repo trigger plan (workflow_dispatch API per D-014).
Phase 04 implements the real step bodies (run l3b_agent_stub.py, commit
contract.yaml to a new branch, close the issue, dispatch the pipeline).
---ci---
phase: 1
milestone: v1.0
status: execute
persona: backend-engineer
task: T-2.2
requirements:
covered: [REQ-10]
---/ci---
Wave 2, task T-2.2. .gitea/workflows/pipeline.yml is the reusable pipeline
skeleton (on: workflow_call) with 4 jobs: dev, qa-gate, prod-gate, finalize.
Branch-pin rule documented in the header comment (uses @milestone/v1.0-initial).
All step bodies are explicit placeholders marked 'Phase 04 will implement'.
Phase 04 will replace the placeholders with the real Dev logic and the
workflow_dispatch approval inputs (D-013; Gitea ignores environment: blocks).
---ci---
phase: 1
milestone: v1.0
status: execute
persona: backend-engineer
task: T-2.1
requirements:
covered: [REQ-01, REQ-09, REQ-10]
---/ci---
Wave 2, task T-2.1. scripts/gitea_setup.sh is idempotent: creates
acdl-contracts + acdl-evidence under the continuous-intelligence org with
default_branch=main + auto_init=true (D-015); pushes a placeholder
index.html to acdl-evidence main via the file-contents API (D-016);
creates qa + prod branches on acdl-contracts as a visible stand-in for the
unsupported Gitea environments API (D-013). 409/422 treated as success
(already exists). bash -n clean.
---ci---
phase: 1
milestone: v1.0
status: research
research:
gitea_capabilities:
pages: not_supported
environments_api: not_supported
repository_dispatch: not_supported
workflow_call: supported
workflow_dispatch: supported
issues_opened: supported
workarounds:
- D-012 raw file URLs in place of Pages
- D-013 workflow_dispatch approval inputs in place of environments
- D-014 workflow_dispatch API in place of repository_dispatch
verification_toolchain:
typecheck: bash -n + python -m py_compile (no package.json)
test: per-phase scripts/verify_phaseNN.sh
build: no-op
---/ci---
ARCHITECTURE.md gains a Gitea API surface table and a branch-pinning rule.
PERSONAS.md is the canonical project-level persona roster: lead-developer
and backend-engineer always active; infra-stub-engineer custom persona owns
L1 stubs; data-engineer deactivated (no DB); frontend-engineer deactivated
until Phase 05.
---ci---
phase: 1
milestone: v1.0
status: clarify
decisions:
- id: D-011
decision: Single-project mode explicitly enforced via config.json mode=single
rationale: run.md Step 0 reads projects[] length as multi-project trigger; explicit flag disambiguates from D-010
confidence: 0.95
alternatives: [move acdl into .ciagent/acdl/ subdirectory and adopt multi-project paths]
- id: D-012
decision: Gitea has no native Pages; serve acdl-evidence via raw file URLs + CORS note
rationale: Research confirms Gitea has no [pages] section; raw URLs work without server config
confidence: 0.85
alternatives: [sidecar static server, external Pages host]
- id: D-013
decision: QA/Prod gates modeled as workflow_dispatch approval inputs (D-004 fallback) instead of Gitea environments
rationale: Research confirms Gitea ignores environment: blocks and exposes no environments API
confidence: 0.90
alternatives: [external approval bot, drop approval gates entirely]
- id: D-014
decision: Cross-repo triggering uses workflow_dispatch API from inside a step (no repository_dispatch)
rationale: Gitea Actions does not support repository_dispatch
confidence: 0.85
alternatives: [push-based trigger with a sentinel file, polling]
- id: D-015
decision: New repos acdl-contracts and acdl-evidence use default_branch=main with auto_init=true
rationale: Matches Gitea DEFAULT_BRANCH=main; required for the default branch to exist before any push
confidence: 0.95
alternatives: [use milestone/v1.0-initial as default_branch]
- id: D-016
decision: Pages placeholder for Phase 01 is a minimal HTML stub; full timeline UI deferred to Phase 05
rationale: Phase 01 success criterion is the URL returns 200 with placeholder; full UI is Phase 05
confidence: 0.90
alternatives: [build a minimal timeline now]
---/ci---
Clarifications accepted at full autonomy per clarify.md Step 4. Three requirements
re-stated: REQ-09 (new repos default_branch=main), REQ-10 Pages (raw-URL 200
substitute), REQ-10 environments (workflow_dispatch inputs + qa/prod branches).
See .ciagent/REQUIREMENTS.md Clarifications table.
---ci---
phase: 0
milestone: v1.0
status: specify
security:
- id: SEC-001
type: info_disclosure
disposition: mitigated
summary: Literal API token was committed in config.json gitea.api_token_env field
fix: Replaced literal with env var name 'ACDL_GITEA_TOKEN'; token supplied via shell env at runtime
severity: high
stride: Information Disclosure
---/ci---
The 40-char value previously stored in .ciagent/config.json was a live Gitea
API token. Per the spec constraint 'no secrets in repo', the field now holds
an env var name. The token itself is exported in the shell session at runtime
and is never written to disk. Treat the prior value as already-leaked and
rotate it via the Gitea UI before any external disclosure.
Jon Chery