fix(query): attach the learning sidecar so CLI query output carries lesson annotations

[Azeem1985]

Fixes #3040.

The docs promise query surfaces the work-memory lessons (CHANGELOG 0.9.3: "graphify explain / query / GRAPH_REPORT.md / the HTML viewer surface them where you look"; README's reflect section says the same), and the renderer has carried learning=<status>[:stale] NODE-annotation support all along — but only for graphs that carry G.graph["_learning_overlay"]. serve._load_graph attaches it (so MCP query_graph annotates) and explain merges the sidecar itself; the CLI query loader builds its graph straight from graph.json and never attached the overlay, so the CLI answer silently dropped the lessons the MCP answer showed.

Fix: the CLI query path now attaches the overlay exactly like serve._load_graph — display-only, fail-safe to {} on any error. Both surfaces emit the identical learning=<status>[:stale] form, including the "code changed since — re-verify" stale marker; without a sidecar the output stays byte-identical (pinned by test).

Tests: sidecar entry → learning=preferred] on the annotated node only; vanished cited file → learning=tentative:stale]; no sidecar → no learning= anywhere. query/reflect/serve families green on top of v8 @ 0.9.49; ruff clean.

🤖 Generated with Claude Code

[graphify-labs]

Graphify reviewed this change.

Worth a look — the grounded gate found no coupling regressions or blocking issues, but 1 advisory finding(s) below merit a look before merge.

Formal verification. No changes could be formally verified in this run.

---

Graphify review — findings

Adds work-memory lesson annotations to graphify query output: dispatch_command now attaches the .graphify_learning.json overlay via load_learning_overlay the same way the MCP _load_graph path does, so learning=<status> and the :stale re-verify marker render on NODE lines identically across CLI, explain, and MCP. The overlay is display-only and falls back to empty on any load error, keeping sidecar-less output byte-identical to before. New tests cover the annotated, stale, and no-sidecar cases.

Worth a look

• Overlay attached from graph.json path instead of its parent directory — graphify/cli.py:1174 · Escalate · medium
  • agreed by 2 of 2 members but NOT verified (no proof, no reproducing execution) — consensus is not a verdict; needs human review

Analysis details — impact, health, verification

Impact & health

Graphify review

Impact — 450 functions depend on the 266 functions this change touches.

Health — this change adds coupling hotspots:

• new: dispatch_command() — 2 callers, 122 callees
• new: _stale_graph_sources() — 7 callers, 6 callees
• new: _run_hook_guard() — 4 callers, 7 callees
• new: test_poisoned_manifest_is_healed() — 0 callers, 6 callees

Verification — 450 functions in the blast radius were not formally verified this run (proofs are advisory here).

Gate & verification

graphify gate

PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.

Advisory (not blocking):

• verification_scope: 403 function(s) in the blast radius were not formally verified this run

Formal verification

Could not verify: Could not verify dispatch\_command.

The verifier did not have enough to check dispatch\_command, so it is saying so rather than guessing. No false assurance is the whole point.

Guarantee: No guarantee either way, this is an honest abstention, not a pass.

Note: Reason: not verifiable: all 23 sampled inputs raised on both versions — the function never executed, so 'no divergence' would be vacuous (mostly SystemExit — names the real obstacle, not a sampling gap)

· 4 more finding(s) on lines outside this diff (see the check run).

[Azeem1985]

Thanks for the grounded review. The flagged fan-out is in the end-to-end test functions — each deliberately exercises the full server lifecycle (spawn, handshake, call, stat the stamp/cache) inline so the test reads as one narrative; happy to factor the shared steps into a fixture if maintainers prefer lower per-test fan-out. No production-code findings noted. — Azeem1985/TelB-io fork

🤖 Generated with Claude Code