fix(ci): unbreak the pytest gate and repair repos.kdl KDL v2 booleans #471
No reviewers
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/agentic-os!471
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/ci-pytest-gate-and-repos-kdl"
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?
The recent
.ward/edits landed through the Forgejo web UI, which bypasses pre-commit, and reddened every aos workflow that runs the pytest gate:ci,release,mirror-to-github, anddep-bump.publish-dev-basesits behind that gate withneeds:, so it has been skipped on every push since, and no dev-base image has published.dep-bumpruns the same gate before it pushes, so the pinnedWARD_VERSIONstayed at0.567.0while ward shippedv0.626.0. That is why ward inside the published image reads stale.What broke
pmrole holding merge authority, so the bundle test'scount == 2assertion failed. The test now pins the merge overlay by role name rather than by count, which guards the surface a bare count never did.true/false). The v2 parser cli-guard uses rejects them and fails the whole document, which silently degraded ward's exec mount and leftward ops forgejounavailable on the host. Regression from778666c.guardfile.aws.engineer.kdlwas missing its trailing newline.Verification
Run inside
agentic-os:latest, the same container CI uses:uv run pytest- 455 passed (was 1 failed).uv run pre-commit run --all-files- all hooks pass..ward/*.kdlfile now parses withcalico32/kdl-go, the parser cli-guard uses.