gemini(w5): apply projection partial-failure report tests #127

New issue

Closed

opened 2026-05-28 01:20:43 +02:00 by codex · 1 comment

codex commented

2026-05-28 01:20:43 +02:00

Collaborator

Parent: #2
Agent lane: Gemini 3.5 Flash
Wave: 5 / Swarmheart / Leviathan
Risk class: medium

Goal

Make controlled projection apply recoverable when one task fails.

Context refs

docs/leviathan-projection-contract.md
_bmad-output/project-context.md

Scope

Find apply projection result shape.
Add fixture where one task succeeds and one fails safely.
Assert output has partial results, failed task refs, and resume/idempotency guidance.

Acceptance

Partial failure does not hide successful writes.
Batch audit summary records result without secrets.
No production apply feature flag changes.

Suggested checks

Projection apply tests in local/dev only.

Non-goals / fences

Do not deploy, restart production, rotate secrets, or run production migrations.
Do not widen MCP write authority or public exposure.
Keep the change small enough for one focused PR or one scouting report.

Expected output

A short PR or issue comment with findings, touched files, tests run, and remaining risks.

Parent: #2 Agent lane: Gemini 3.5 Flash Wave: 5 / Swarmheart / Leviathan Risk class: medium ## Goal Make controlled projection apply recoverable when one task fails. ## Context refs - `docs/leviathan-projection-contract.md` - `_bmad-output/project-context.md` ## Scope - Find apply projection result shape. - Add fixture where one task succeeds and one fails safely. - Assert output has partial results, failed task refs, and resume/idempotency guidance. ## Acceptance - Partial failure does not hide successful writes. - Batch audit summary records result without secrets. - No production apply feature flag changes. ## Suggested checks - Projection apply tests in local/dev only. ## Non-goals / fences - Do not deploy, restart production, rotate secrets, or run production migrations. - Do not widen MCP write authority or public exposure. - Keep the change small enough for one focused PR or one scouting report. ## Expected output A short PR or issue comment with findings, touched files, tests run, and remaining risks.

codex added the

labels

2026-05-28 01:20:43 +02:00

codex referenced this issue from a commit

2026-06-03 09:57:17 +02:00

fix(agent): report Leviathan partial apply recovery (#127)

codex referenced this issue from a pull request that will close it,

2026-06-03 09:57:36 +02:00

fix(agent): report Leviathan partial apply recovery #150

codex commented

2026-06-03 09:57:53 +02:00

Author

Collaborator

Codex PR opened: #150

Scope:

added task-level idempotencyKey and resumeHint to Leviathan apply results,
centralized apply result formatting,
kept old batch audit replay compatibility by making the new fields optional in the schema,
added integration coverage for one applied task plus one failed move caused by proposal_required,
asserted the successful write remains applied, failed card remains unmoved, and batch audit stores summary/results/recovery fields.

Checks:

pnpm --filter @kan/api exec vitest integration-tests/agent.integration.test.ts --run -t "reports partial Leviathan apply failures" — passed.
pnpm --filter @kan/api exec vitest integration-tests/agent.integration.test.ts --run — passed, 16 tests.
pnpm --filter @kan/api typecheck — passed.
pnpm exec prettier --check packages/api/src/routers/agent.ts packages/api/integration-tests/agent.integration.test.ts docs/leviathan-projection-contract.md — passed.

No production deploy, restart, DB migration, token/Infisical change, or projection apply enablement.

Codex PR opened: https://git.pdurlej.com/pdurlej/kan-ductor/pulls/150 Scope: - added task-level `idempotencyKey` and `resumeHint` to Leviathan apply results, - centralized apply result formatting, - kept old batch audit replay compatibility by making the new fields optional in the schema, - added integration coverage for one applied task plus one failed move caused by `proposal_required`, - asserted the successful write remains applied, failed card remains unmoved, and batch audit stores summary/results/recovery fields. Checks: - `pnpm --filter @kan/api exec vitest integration-tests/agent.integration.test.ts --run -t "reports partial Leviathan apply failures"` — passed. - `pnpm --filter @kan/api exec vitest integration-tests/agent.integration.test.ts --run` — passed, 16 tests. - `pnpm --filter @kan/api typecheck` — passed. - `pnpm exec prettier --check packages/api/src/routers/agent.ts packages/api/integration-tests/agent.integration.test.ts docs/leviathan-projection-contract.md` — passed. No production deploy, restart, DB migration, token/Infisical change, or projection apply enablement.