Adopt portable swarm practices in loop engineering - #39
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Loop-engineering gave shared-filesystem workers conflicting instructions about writing shared Worklog state. This change defines one role and handoff contract: workers return revision-aware evidence, the parent verifies it and owns shared persistence, and every orchestrator cycle invokes the driver so radar and queue checks stay active.
Adopts portable practices from swarm-forge: scoped ownership, independent acceptance checks, stale-return reconciliation and explicit uncertainty. Keeps the existing skill distribution; no plugin runtime is needed. Separates radar interpretation from process/artifact IO while preserving verdicts and the state schema. Adds malformed-response and rejected-state preservation coverage, and regenerates the loop-run package.
Removes historical migration, audit and Pixel reports, the MCP changelog, dated testing anecdotes and historical narratives from the shipped Worklog template. Enduring rationale is retained in two architectural decision records; active usage guidance and test specifications remain.
Validation:
Worklog project: generic-loop-engineering. Children: loop-swarm-contracts, loop-swarm-runtime, loop-design-docs, loop-swarm-verification. Scope is implemented and ready for review. No global skill installation or merge performed; Windows and x86 Linux were not tested.