Add CI adoption templates #32
No reviewers
Labels
No labels
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
priority:p0
priority:p1
priority:p2
priority:p3
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/fallow-ts!32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/wave3-ci-templates"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Canary Context Pack
Product story
After findings, classification, and baselines, users need copy-paste CI examples that run fallow-ts as a deterministic checkpoint without MCP, secrets, or platform lock-in.
What changed
examples/ci/README.mdwith install, baseline, and copy paths.Why it changed
Wave 3 ends with CI adoption material so the agent review layer can be tried in real repos.
Files touched
examples/ci/forgejo-actions.ymlexamples/ci/github-actions.ymlexamples/ci/README.mdtests/ci_templates.test.mjsREADME.mdRuntime evidence
npm run buildnpm testnode dist/cli.js analyze --root . --format json --output /tmp/fallow-ts-report.jsongit diff --checkKnown constraints
Templates assume the consumer repo installs
fallow-tsas a dev dependency and runsnpm ci.Explicit out-of-scope
No artifact upload, no package publish flow, no MCP integration, no secrets or remote baseline service.
Requested decision
Approve if the templates are copy-pasteable, platform-native, Forgejo-first, and aligned with the baseline gate.
Merge blockers
Closes #16.