feat(tri): landed --file asserts a path, not only content (Closes #2269) - #2270
Conversation
Verifying a merged pull request, probing for CITED_NUMBERS returned ABSENT while research/CITED_NUMBERS_2026-08-20.md was on main. The tool was right and the question was wrong: --probe searches content, and a file rarely contains its own name. --file <path> asserts existence on the default branch, reported as EXISTS/MISSING beside the content probes. Fifth way a landing probe lies — and the first fixable in the tool rather than in the caller. Closes #2269
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
|
Measured rather than assumed: dispatched the workflow on master (run 32319733329). Master fails it too, and more broadly — every spec failing here also fails on master. The failure is pre-existing repository drift, not this change. Merging on that evidence; the drift is filed separately. |
PR DashboardGenerated at: 2026-08-20 01:14:49 UTC
Summary
Seal Status
|
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
PR DashboardGenerated at: 2026-08-20 02:07:42 UTC
Summary
Seal Status
|
Closes #2269. Found while verifying that #623's provenance package reached trinity-fpga's main — the probe said ABSENT about a file that was present, because it searched content for a filename.
🤖 Generated with Claude Code