You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
queen(heal): root cause, heal log row and one anomaly scan in self_health #13319
self_health detects trouble but keeps no cause, no log of what was healed and no single scan. This issue EXTENDS specs/queen/self_health.t27 and adds no second spec. It adds root_cause, a heal log row (type, cause, fix, prevention), one anomaly_scan combining the AK_* kinds of specs/acceleration/pareto_weak_points.t27 with conflict_starved, and one escalate. The next free team_msg tag is 36 (specs/queen/team_msg.t27), for the escalation message. Refs #13260
Boundary
specs/queen/self_health.t27
User Scenarios
Given a lane is starved by a merge conflict when anomaly_scan runs then it reports conflict_starved together with the AK_* kinds in one result.
Given a heal was applied when it is logged then the row holds type, cause, fix and prevention.
Given a heal failed twice when escalate is called then exactly one escalation is produced.
Requirements
FR-001: self_health MUST provide root_cause returning the cause of an anomaly.
FR-002: self_health MUST provide a heal log row with the fields type, cause, fix and prevention.
FR-003: self_health MUST provide one anomaly_scan that combines the AK_* kinds of pareto_weak_points.t27 with conflict_starved, and one escalate.
FR-004: The change MUST add no new spec file.
Success Criteria
t27c test-report specs/queen/self_health.t27 exits 0, reports FAIL 0 and vacuous passes 0, and tests for root_cause, the heal row, anomaly_scan and escalate appear.
git diff --name-only origin/master lists 0 files outside the Boundary and the seal files.
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.
Activity
gHashTag commentedon Nov 17, 2026
Spec created: specs/queen/queen_operations.t27 (typecheck OK, 1 test pass). Covers Queen operations issues.
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Specs created for M10 milestone. Typecheck OK.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.