WIP: fix: harden kan-ductor agent safety gates #60

Closed

glm wants to merge 0 commits from glm/codex-kan-ductor-stabilization into main AGit

glm commented

2026-05-15 19:31:37 +02:00

First-time contributor

Canary status: missing - fire 3+3 review before merge

Summary

Hardens the Kan-ductor maintainer layer after the Piotr + Iskra MCP smoke loop started working. This PR focuses on safety gates, audit truth, recap reliability, MCP readiness probes, and maintainer tooling.

Scope

Adds projection:write and projection:override_warnings scopes.
Adds server-side KAN_PROJECTION_APPLY_ENABLED=false default for real Leviathan apply.
Blocks projection writes with security/gate warnings unless explicitly overridden.
Stores and reads exact audit/activity lineage through activityPublicId for create/move/comment/relation actions.
Adds low-confidence fallback labeling for old time-window audit matching.
Redacts default human audit reads; raw payloads require includeRaw=true and workspace:manage.
Adds getRecentActivity.summary for Piotr/Iskra recap questions.
Adds /live, /ready, and readiness-compatible /health to MCP.
Adds relation activity enum values and relation activity creation.
Adds dry-run-first machine identity maintainer CLI.
Captures durable BMAD context in _bmad-output/project-context.md.

Non-goals

No production deploy.
No production DB migration.
No production token issuance or rotation.
No KAN_PROJECTION_APPLY_ENABLED=true in production.
No autonomous drift repair.
No analytics dashboard or full UI polish.

Spec sources read

docs/agent-mcp-contract.md
docs/leviathan-projection-contract.md
docs/openclaw-kan-mcp.md
_bmad-output/project-context.md
Stabilization issues: #5, #6, #53-#59 via meta #2 context

Tests / smoke

Run locally:

pnpm --filter @kan/api typecheck
pnpm --filter @kan/db typecheck
pnpm --filter @kan/mcp typecheck
pnpm --filter @kan/api test -- agent.test.ts
pnpm --filter @kan/mcp test -- health.test.ts
pnpm --filter @kan/api exec eslint src/routers/agent.ts src/routers/agent.test.ts
pnpm --filter @kan/db exec eslint src/repository/agent.repo.ts src/repository/card.repo.ts src/repository/cardActivity.repo.ts src/repository/cardRelation.repo.ts src/schema/cards.ts
node --check scripts/kan-machine-identity-admin.mjs
git diff --check

Known repo-level lint caveats:

Full @kan/api lint still reports pre-existing lint debt outside this PR scope.
@kan/db lint still reports pre-existing lint debt outside this PR scope.
@kan/mcp lint currently lacks an eslint flat config in that package.

Rollback

Revert this PR.
Do not run the new migration in production if rollback is needed before deploy.
Keep KAN_PROJECTION_APPLY_ENABLED=false.
Do not issue or rotate production machine credentials from the new CLI.

Owner gates

Piotr approval required before:

merge,
production DB migration,
production deploy/restart,
enabling KAN_PROJECTION_APPLY_ENABLED=true,
issuing/rotating/revoking production machine credentials,
expanding trust boundary or public exposure,
treating low-confidence old audit matching as authoritative.

3+3 review request

Required before merge because this PR touches auth scopes, write gates, audit redaction, MCP readiness, schema enum migration, and drift/lineage semantics.

Canary status: missing - fire 3+3 review before merge ## Summary Hardens the Kan-ductor maintainer layer after the Piotr + Iskra MCP smoke loop started working. This PR focuses on safety gates, audit truth, recap reliability, MCP readiness probes, and maintainer tooling. ## Scope - Adds `projection:write` and `projection:override_warnings` scopes. - Adds server-side `KAN_PROJECTION_APPLY_ENABLED=false` default for real Leviathan apply. - Blocks projection writes with security/gate warnings unless explicitly overridden. - Stores and reads exact audit/activity lineage through `activityPublicId` for create/move/comment/relation actions. - Adds low-confidence fallback labeling for old time-window audit matching. - Redacts default human audit reads; raw payloads require `includeRaw=true` and `workspace:manage`. - Adds `getRecentActivity.summary` for Piotr/Iskra recap questions. - Adds `/live`, `/ready`, and readiness-compatible `/health` to MCP. - Adds relation activity enum values and relation activity creation. - Adds dry-run-first machine identity maintainer CLI. - Captures durable BMAD context in `_bmad-output/project-context.md`. ## Non-goals - No production deploy. - No production DB migration. - No production token issuance or rotation. - No `KAN_PROJECTION_APPLY_ENABLED=true` in production. - No autonomous drift repair. - No analytics dashboard or full UI polish. ## Spec sources read - `docs/agent-mcp-contract.md` - `docs/leviathan-projection-contract.md` - `docs/openclaw-kan-mcp.md` - `_bmad-output/project-context.md` - Stabilization issues: #5, #6, #53-#59 via meta #2 context ## Tests / smoke Run locally: ```bash pnpm --filter @kan/api typecheck pnpm --filter @kan/db typecheck pnpm --filter @kan/mcp typecheck pnpm --filter @kan/api test -- agent.test.ts pnpm --filter @kan/mcp test -- health.test.ts pnpm --filter @kan/api exec eslint src/routers/agent.ts src/routers/agent.test.ts pnpm --filter @kan/db exec eslint src/repository/agent.repo.ts src/repository/card.repo.ts src/repository/cardActivity.repo.ts src/repository/cardRelation.repo.ts src/schema/cards.ts node --check scripts/kan-machine-identity-admin.mjs git diff --check ``` Known repo-level lint caveats: - Full `@kan/api lint` still reports pre-existing lint debt outside this PR scope. - `@kan/db lint` still reports pre-existing lint debt outside this PR scope. - `@kan/mcp lint` currently lacks an eslint flat config in that package. ## Rollback - Revert this PR. - Do not run the new migration in production if rollback is needed before deploy. - Keep `KAN_PROJECTION_APPLY_ENABLED=false`. - Do not issue or rotate production machine credentials from the new CLI. ## Owner gates Piotr approval required before: - merge, - production DB migration, - production deploy/restart, - enabling `KAN_PROJECTION_APPLY_ENABLED=true`, - issuing/rotating/revoking production machine credentials, - expanding trust boundary or public exposure, - treating low-confidence old audit matching as authoritative. ## 3+3 review request Required before merge because this PR touches auth scopes, write gates, audit redaction, MCP readiness, schema enum migration, and drift/lineage semantics.

glm added 1 commit

2026-05-15 19:31:37 +02:00

fix: harden kan-ductor agent safety gates

Forgejo CI / verify (pull_request) Successful in 10m28s

Details

Forgejo Docker Images / build (pull_request) Failing after 6s

Details

fa443e8874

glm changed title from ~~fix: harden kan-ductor agent safety gates~~ to WIP: fix: harden kan-ductor agent safety gates

2026-05-15 19:32:23 +02:00

glm referenced this pull request

2026-05-15 19:32:36 +02:00

[meta] Kan-ductor maturity waves #2

codex referenced this pull request

2026-05-15 19:37:53 +02:00

fix: harden kan-ductor agent safety gates #61

codex commented

2026-05-15 19:38:10 +02:00

Collaborator

Closing as superseded by #61. This PR was accidentally created through the GLM Forgejo identity; per agent-souls identity discipline, the Codex-owned PR is #61.

codex closed this pull request

2026-05-15 19:38:10 +02:00

codex referenced this pull request

2026-05-15 19:38:22 +02:00

[meta] Kan-ductor maturity waves #2