[P0] Remove legacy nested harnesses and leave prolog-rlm runtime-only #186
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/prolog-rlm#186
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent/related: #141, #184, #124, PR #125
Goal
Clean
prolog-rlmback to a domain-neutral reusable runtime before implementing the approved plugin-only DeepSeek Harness architecture.The user has explicitly authorized removal of the old harnesses. The prior #141
OLD HARNESS REMOVAL GATEis therefore lifted.Required end state
prolog-rlmcontains reusable runtime/library code only. Product/frontend harnesses live downstream.a0-symbolicsis one downstream frontend/consumer, not the owner or replacement for the code-harness product.Remove / retire
agentProlog/product harness from this repository.prolog-rlm.Preserve / relocate before deletion
Do not delete reusable generic runtime contracts merely because they currently live under
agentProlog/.Audit and relocate any genuinely generic pieces first, especially the renderer-independent protocol/facade semantics currently represented by:
agentProlog/prolog/prolog_agent_ui_v1.plagentProlog/prolog/prolog_agent_ui_facade.plIf these remain generic, move/rename them into normal core
prolog/,test/, anddocs/locations with domain-neutral names. If they are product-specific, move them downstream instead.Invariants
prolog-rlmback to standalone AgentProlog or a0-symbolics;Acceptance
agentProlog/no longer exists onmainas a nested product harness.nix flake checkpasses.agentProlog/product paths.Ordering
Do this cleanup before building the #184 plugin-only Harness core. The new Harness work starts from the cleaned runtime boundary rather than preserving or refactoring the obsolete product harness in place.
#186 first structural slice: PR #187
Cleanup is now implemented on
cleanup/186-remove-legacy-harnessesin draft PR #187.Current verified structure:
agentProlog/product harness is removed from the branch;prolog_agent_ui_v1is relocated to normal coreprolog/with the exact original blob (no wire/protocol code change);test/fixtures/;test/support/;CI is running for the exact current head across deterministic CI, Nix flake, clean SWI pack install, Tree-sitter FFI, and paid OpenRouter. #186 stays open until those gates and final stale-reference review are complete.
#187 exact-head gate is green
PR #187 head
7387cbaa4d19b66aa89b55688618c945902e85eahas now passed every triggered gate:The PR is now ready for review. It is intentionally not merged yet; #186 should remain open until the cleanup lands on
mainand the post-merge tree/docs are rechecked. After that, #184 is the next Harness implementation track.