Reconcile backlog, roadmap, and GitHub issue state #89

Merged

lost-rob0t merged 6 commits from reconcile-backlog-issues into main

2026-08-18 05:49:34 +00:00

lost-rob0t commented

2026-08-18 05:46:20 +00:00

(Migrated from github.com)

Baseline

Canonical main inspected before branching:

abfc30ebb9f335d5841c1f7910bd474da905ebcf (2026-08-18)

The branch was created directly from that SHA.

Repository status reconciliation

TODO

updates the reconciliation SHA/date;
replaces the stale August 15 status/CI preamble with durable categories for correctness defects, feature/architecture work, docs/hygiene, and completed foundations;
keeps #42, #44, #45, and #46 as the current v0.1/manual-validation correctness blockers;
records merged #52/#53 and the merged #78/#83/#85 generic effect substrate without pretending #57/#79 canonical adoption is complete;
records #86 as open/unmerged rather than implementation evidence;
adds a concise authority/async/effect section so the post-August-15 runtime work is represented without turning TODO into an issue dump.

README

removes the unsupported claim that rlm_graph already implements parallel branches; the repository TODO still tracks that work as incomplete;
updates Status to distinguish the merged generic durable-effect substrate from incomplete canonical #79 adoption;
names the actual #3 correctness blockers.

PrologAgent roadmap

records #78/#83/#85 as the merged generic effect substrate;
makes #79 canonical adoption an explicit remaining Phase 0 dependency;
records PR #86 as open/unmerged rather than completed readiness;
clarifies that #54 core migrations are largely present while external process/test/network and downstream TUI integration remain.

Architecture/docs sweep

updates docs/external-tool-libraries.md to reflect that #52 is complete after #72, cross-reference docs/mcp-lifecycle.md, preserve loader/capability/authority/hard-policy separation, and leave #67 cleanup correctly open;
updates docs/async-runtime.md, which still incorrectly claimed tools/MCP/agents/graphs awaited the next #54 slice and described #52 lifecycle work as pending; it now records #60/#61/#62/#72 and the real remaining #54 scope.

AGENTS.md

Adds the durable rule that changing TODO/roadmap status or completing a slice must reconcile related parent/child GitHub issue state and remove stale blocker/completion prose. GitHub state, TODO state, roadmap state, and merged implementation evidence must not knowingly diverge.

GitHub issue reconciliation

Bodies updated:

#3 — keeps the epic scoped to v0.1/manual validation, removes stale historical CI wording, and lists the real blockers.
#54 — removes the stale claim that #52 remains open and records completed #52/#53 plus the remaining external-tool/TUI work.
#57 — records merged generic substrate/hardening/migration while keeping end-to-end canonical adoption open under #79.
#79 — replaces the stale draft-#78 baseline with current merged substrate state and records #86 as only an open slice 1.

Issue state corrected:

#44 reopened. Current main still has completion_after_execution(error(Error), ..., error(Error)) returning before the success-only plan_usage/2 + usage_add/3 aggregation path. That is exactly #44's unresolved failure-path accounting defect. #78 explicitly did not claim to close #44.

Documentation-only issue targeted for closure after merge:

#73 — both known stale #52-era documentation surfaces are corrected in this PR. It should close only once this exact change is on main.

Issues created: none. The missing-issue audit found no concrete untracked defect or coherent required implementation slice that was not already represented. Broad future TODO items were not exploded into issue spam.

Intentionally left open include #3, #42, #44, #45, #46, #49, #50, #51, #54, #56, #57, #67, #68-#71, #74-#77, and #79. In particular, #57/#79 stay open because canonical effect-boundary adoption is incomplete.

Verification

This PR changes only Markdown files. No runtime code or CI configuration is changed.

The requested local SWI commands could not be executed in the current work environment because swipl is not installed there. Rather than substitute fake or paid model evidence, the exact PR-head GitHub Actions run is the canonical executable gate.

No manual REAL OpenRouter call is triggered solely for this documentation slice. If the canonical workflow runs its configured credentialed lane, that CI result remains authoritative.

git diff --check cannot be run locally without a repository checkout in this connector-only environment; GitHub's exact-head whitespace/static checks remain the merge gate.

Non-goals

no unrelated runtime implementation;
no attempt to close #57 or #79 from generic substrate work;
no attempt to make unmerged PR #86 count as canonical implementation;
no speculative issue creation to make the tracker look busy.

## Baseline Canonical `main` inspected before branching: `abfc30ebb9f335d5841c1f7910bd474da905ebcf` (2026-08-18) The branch was created directly from that SHA. ## Repository status reconciliation ### TODO - updates the reconciliation SHA/date; - replaces the stale August 15 status/CI preamble with durable categories for correctness defects, feature/architecture work, docs/hygiene, and completed foundations; - keeps #42, #44, #45, and #46 as the current v0.1/manual-validation correctness blockers; - records merged #52/#53 and the merged #78/#83/#85 generic effect substrate without pretending #57/#79 canonical adoption is complete; - records #86 as open/unmerged rather than implementation evidence; - adds a concise authority/async/effect section so the post-August-15 runtime work is represented without turning TODO into an issue dump. ### README - removes the unsupported claim that `rlm_graph` already implements parallel branches; the repository TODO still tracks that work as incomplete; - updates Status to distinguish the merged generic durable-effect substrate from incomplete canonical #79 adoption; - names the actual #3 correctness blockers. ### PrologAgent roadmap - records #78/#83/#85 as the merged generic effect substrate; - makes #79 canonical adoption an explicit remaining Phase 0 dependency; - records PR #86 as open/unmerged rather than completed readiness; - clarifies that #54 core migrations are largely present while external process/test/network and downstream TUI integration remain. ### Architecture/docs sweep - updates `docs/external-tool-libraries.md` to reflect that #52 is complete after #72, cross-reference `docs/mcp-lifecycle.md`, preserve loader/capability/authority/hard-policy separation, and leave #67 cleanup correctly open; - updates `docs/async-runtime.md`, which still incorrectly claimed tools/MCP/agents/graphs awaited the next #54 slice and described #52 lifecycle work as pending; it now records #60/#61/#62/#72 and the real remaining #54 scope. ### AGENTS.md Adds the durable rule that changing TODO/roadmap status or completing a slice must reconcile related parent/child GitHub issue state and remove stale blocker/completion prose. GitHub state, TODO state, roadmap state, and merged implementation evidence must not knowingly diverge. ## GitHub issue reconciliation Bodies updated: - #3 — keeps the epic scoped to v0.1/manual validation, removes stale historical CI wording, and lists the real blockers. - #54 — removes the stale claim that #52 remains open and records completed #52/#53 plus the remaining external-tool/TUI work. - #57 — records merged generic substrate/hardening/migration while keeping end-to-end canonical adoption open under #79. - #79 — replaces the stale draft-#78 baseline with current merged substrate state and records #86 as only an open slice 1. Issue state corrected: - **#44 reopened.** Current `main` still has `completion_after_execution(error(Error), ..., error(Error))` returning before the success-only `plan_usage/2` + `usage_add/3` aggregation path. That is exactly #44's unresolved failure-path accounting defect. #78 explicitly did not claim to close #44. Documentation-only issue targeted for closure after merge: - #73 — both known stale #52-era documentation surfaces are corrected in this PR. It should close only once this exact change is on `main`. Issues created: **none**. The missing-issue audit found no concrete untracked defect or coherent required implementation slice that was not already represented. Broad future TODO items were not exploded into issue spam. Intentionally left open include #3, #42, #44, #45, #46, #49, #50, #51, #54, #56, #57, #67, #68-#71, #74-#77, and #79. In particular, #57/#79 stay open because canonical effect-boundary adoption is incomplete. ## Verification This PR changes only Markdown files. No runtime code or CI configuration is changed. The requested local SWI commands could not be executed in the current work environment because `swipl` is not installed there. Rather than substitute fake or paid model evidence, the exact PR-head GitHub Actions run is the canonical executable gate. No manual REAL OpenRouter call is triggered solely for this documentation slice. If the canonical workflow runs its configured credentialed lane, that CI result remains authoritative. `git diff --check` cannot be run locally without a repository checkout in this connector-only environment; GitHub's exact-head whitespace/static checks remain the merge gate. ## Non-goals - no unrelated runtime implementation; - no attempt to close #57 or #79 from generic substrate work; - no attempt to make unmerged PR #86 count as canonical implementation; - no speculative issue creation to make the tracker look busy.