Keep task graph off the default status hot path#814
Conversation
|
Self-review: this PR fixes the dashboard status hot-path budget regression by moving optional task graph projection behind an explicit cold-path flag. The root cause was not the todo lanes themselves, but always attaching |
|
Findings: none from this review pass. Open questions / assumptions: I treated this as a status hot-path budget repair that moves Validation performed:
Merge decision: hold for normal reviewer/branch-protection flow; no blocker found in the diff plus focused hot-path smoke. |
Summary
task_graph_projection_v0off defaultloopx statusoutput to preserve the dashboard status interface budgetloopx status --include-task-graphfor callers that explicitly need the optional graphValidation
python3 examples/hot-path-interface-budget-smoke.pypython3 examples/task-graph-projection-fixture-smoke.pypython3 examples/review-packet-cli-smoke.pypython3 -m py_compile loopx/status.py loopx/cli_commands/status.pypython3 examples/status-markdown-smoke.pypython3 examples/goal-channel-status-export-smoke.pyloopx check --scan-path loopx/status.py --scan-path loopx/cli_commands/status.py --scan-path examples/hot-path-interface-budget-smoke.py --scan-path docs/status-data-contract.md --scan-path docs/reference/protocols/task-graph-projection-v0.mdgit diff --checkFocused result:
dashboard_status_jsonis now 17634/18000 in the hot-path smoke; default source CLI omitstask_graph_projection, while--include-task-graphincludes it.