fix(ci): gate canary on Infisical readiness #89
No reviewers
Labels
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
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/platform!89
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/fix/canary-infisical-readiness"
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?
Summary
ZAI_API_KEY/CANARY_FORGEJO_TOKENdependency fromcanary-required.ymlstack.env/ repo-secret canary patternsVerification
python3 -m py_compile control-plane/platformctl/ci/lint_workflows.py control-plane/platformctl/ci/canary_readiness.py control-plane/platformctl/ci/check_docs_drift.pypython3 -m pytest -q control-plane/platformctl/tests/test_forgejo_workflow_lint_contract.py control-plane/platformctl/tests/test_forgejo_ci_scripts_contract.pypython3 -m pytest -q control-plane/platformctl/testspyfallow analyze --root control-plane --format agent-fix-plan --output /tmp/platform-p0-pyfallow.json --fail-on error --min-confidence mediumpython3 control-plane/platformctl/ci/lint_workflows.py --policy .forgejo/ci-policy.yaml --workflows .forgejo/workflows --markdown /tmp/ci-workflow-lint.md --json /tmp/ci-workflow-lint.jsonpython3 control-plane/platformctl/ci/check_docs_drift.py --root . --json /tmp/docs-drift-report.json --markdown /tmp/docs-drift-report.mdNotes
This intentionally keeps canary as an honest readiness scaffold until rs2000 has a runner-local Infisical env bridge. It should stop false red checks caused by missing repo secrets without pretending the 3+3 review actually ran.