Skip to content

Stop false bad Colony health readiness#513

Merged
NagyVikt merged 1 commit into
mainfrom
agent/codex/fix-colony-health-readiness-classifiers-2026-05-10-15-37
May 10, 2026
Merged

Stop false bad Colony health readiness#513
NagyVikt merged 1 commit into
mainfrom
agent/codex/fix-colony-health-readiness-classifiers-2026-05-10-15-37

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Automated by gx branch finish (PR flow).

The health command was flattening two non-actionable states into bad readiness: branch-mismatch telemetry where claims already matched file/session/worktree, and older/current diagnostic claim telemetry that should not tell agents to reclaim already-claimed files.

Constraint: health output must remain operator-actionable and not mark live claim safety bad when the evidence points at lifecycle branch metadata drift.

Rejected: Keep using lifecycle_claim_mismatch for all branch_mismatch rows | it repeats the wrong reclaim instruction when the nearest claim already matched the edit scope.

Confidence: high

Scope-risk: narrow

Directive: Do not make claim-before-edit bad solely from branch_mismatch without checking nearest-claim relation evidence.

Tested: pnpm --filter colonyq test -- health.test.ts queen-health.test.ts

Tested: pnpm --filter colonyq typecheck

Tested: node apps/cli/dist/index.js health
@NagyVikt NagyVikt merged commit 716c231 into main May 10, 2026
@NagyVikt NagyVikt deleted the agent/codex/fix-colony-health-readiness-classifiers-2026-05-10-15-37 branch May 10, 2026 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant