Release Loop-Engineering v1.1.0#6
Merged
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.
What changed
Why
Loop-Engineering should support suitable long-horizon tasks in any domain without creating a separate Skill per use case. A user can start with a vague idea, review a verifiable Goal and suggested Loop structure, then let one universal Skill advance the approved work Part by Part without skipping failed checks or claiming completion early.
User impact
Validation
npm test: 161/161 passingnpm run validate:examplesnpm run validate:proposalsnpm run doctorgh skill publish --dry-run: cleannpm run package:smokenpm audit --omit=dev --audit-level=high: 0 vulnerabilitiesnpm publish --dry-run --access public: passingSummary by cubic
Release v1.1.0 adds an Idea‑to‑Loop “Propose” mode that turns vague requests into verifiable Goal Contracts and approved loops, plus a domain‑neutral finite Work Plan with Part gates and a final Goal Gate. It also introduces canonical SHA‑256 digests, hardened state locks, new schemas/templates, updated docs, and pinned runtime commands.
New Features
LoopProposalwith at most three material questions, explicit assumptions/readiness, and complete traceability; humanLoopProposalDecisionbinds an exact proposal SHA‑256; deterministic compile toloop.yaml.nextnow signalswork,goal-evaluation, orcompleted; independent final Goal evaluation (goal-evaluation.schema.json).Migration
npm exec --yes --package=github:sheepxux/Loop-Engineering#v1.1.0 -- loopctland update any pinned fallback in adapters/scripts.LoopProposal, obtain a humanLoopProposalDecisionbound to its SHA‑256, then compile toloop.yaml; do not execute unapproved candidates.workPlaninloop.yaml, run one Part at a time (or as approved), and perform an independent final Goal evaluation before markingcompleted.loopctl doctorandloopctl validateafter upgrading; follow new lock‑gate guidance when recovering stale locks.Written for commit ccc388c. Summary will update on new commits.