chore: version packages#247
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
12 times, most recently
from
51dcf66 to
4253322
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
4253322 to
059429b
Compare
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@gemstack/ai-autopilot@0.8.0
Minor Changes
4a6311e: Domain preset runs can now pick a build event kind, so a preset's bug-fix loop actually fires. A run chooses it with
runFramework({ buildEvent })/ theframework --kind <name>flag, and a preset can declare its own default viapreset.mdmetadata.event(surfaced asDomainPreset.defaultEvent). Precedence: run choice > preset default >major-change; an event the preset has no loop for still falls back to the built-in checklist.8c3e7d0: The domain loop drives the production-grade review phase (Open Loop: drive the domain loop as a run phase #252).
When a run has a domain preset, its review loop now replaces the built-in
checklist: each pass dispatches a
major-changeevent through the preset'sdriver-backed loop, so its review chain (e.g. code review, test coverage, security
review) fires through the wrapped agent, and Bootstrap's pass / improve / maxPasses
machinery gates on the union of the
{ blockers }verdicts the chain reports. Apreset with no loop for the build event falls back to the built-in checklist, so a
run is never left unreviewed. New:
domainLoopChecklist+verdictFromLoopRun(@gemstack/framework).
The shipped Software Development preset's review prompts (code review, test
coverage, security review) now end with a
{ blockers }verdict so the loopactually gates rather than only running.
03e06aa: Add the Open Loop bundle unit: a domain preset = {loops, prompts, skills} (Open Loop: bundle unit = preset {loops, prompts, skills} #242).
This is the keystone that ties the three data types the framework already ships
separately into one selectable, composable thing. Author one in code with
defineDomainPreset, or load one from a directory of.mdfiles (preset.md+loops/,prompts/,skills/) withloadDomainPreset.composeDomainPresetsmerges several into one (loops concatenate; prompts and skills merge by id/name,
later wins), so presets-of-presets falls out;
selectPresetpicks the user'sdomain by name. Kept distinct from the framework
Presetdetector inpresets/(skipped for the Open Loop MVP) by naming this
DomainPreset.3c72f14: Add modes (Autopilot / Technical) to domain presets via
conditionsfrontmatter (Open Loop: modes (Autopilot / Technical) via conditions frontmatter #244).A preset content file can now ship mode variants: a
stem.<variant>.mdsiblingthat declares
metadata.conditions(a mode or list) overrides itsstem.mdbasewhen those modes are active.
loadDomainPreset(dir, { modes })(andsoftwareDevelopmentPreset({ modes })) resolve the winner per stem — the mostspecific eligible variant, falling back to the base. The shipped Software
Development preset gains a
technicalvariant of its major-change loop as anillustration. This is the simple frontmatter fan-out; composing prompts from
parameters is the follow-up (Parameterized markdown #245).
e45e4d0: Preset discovery API: enumerate domain presets so the CLI/UI picker can list and
pick one by name (Preset discovery API: enumerate + pick domain presets by name #254).
builtinDomainPresets()loads every domain preset shipped under the package'spresets/directory (today just Software Development; new built-ins are picked upautomatically).
loadDomainPresetsFrom(dir)loads every immediate subdirectorythat holds a
preset.md, skipping the rest, sorted by name. Pair either with theexisting
selectPreset(list, name)to pick the user's chosen domain.396dc7f: Rename the loop engine's
rulesvocabulary toloops(Open Loop, Open Loop: rename rules -> loops in the engine #241).A loop is a meta prompt, so that is the user-facing unit even though rule logic powers it.
defineLoop/defaultLoops/Loop/LoopSpecreplacedefineRule/defaultLoopRules/LoopRule/LoopRuleSpec; the engine class is nowLoopEngine(wasLoop), created viacreateLoopEnginewithLoopEngineOptions; and its option key isloops(wasrules). Vocabulary only, no behavior change.24944b9: Ship the "Software Development" domain preset (Open Loop: 'Software Development' domain preset #243).
The first built-in Open Loop preset, authored as a directory of
.mdfiles:two loops (major-change -> code-review + test-coverage + security-review; bug-fix
-> root-cause + regression-test), five stack-agnostic prompt bodies, and one skill
pointer. Non-web and user-picked (no dependency detection). Load it with
softwareDevelopmentPreset();builtinPresetsDir()points at the shippedpresets/directory. Proves the bundle unit end to end.d2acba4: Add two more built-in domain presets:
web-developmentanddata-science.Each ships as a directory of
.mdfiles likesoftware-development, so it isauto-discovered by
builtinDomainPresets(), selectable via--preset <name>andthe-framework.yml, and drives the review phase. Both carry a Technical Controlvariant (leaner major-change loop) and a bug-fix loop. Their major-change review
prompts end with the
{ blockers }verdict footer so the review loop gates.@gemstack/framework@0.6.0
Minor Changes
4a6311e: Domain preset runs can now pick a build event kind, so a preset's bug-fix loop actually fires. A run chooses it with
runFramework({ buildEvent })/ theframework --kind <name>flag, and a preset can declare its own default viapreset.mdmetadata.event(surfaced asDomainPreset.defaultEvent). Precedence: run choice > preset default >major-change; an event the preset has no loop for still falls back to the built-in checklist.b81e563: Run a build under an Open Loop domain preset (Open Loop: wire domain presets into the framework run (framing + loop bridge) #251).
runFramework({ preset, modes })now accepts a user-picked domain preset({loops, prompts, skills}). Its skills (and their personas) frame every phase of
the run alongside the detected framework skill, the selected domain and active
modes are narrated, and its loops + prompts are materialized into a driver-backed
LoopEngineexposed asresult.loop(each pass is a fresh driver prompt). Thenew
driverLoopPromptsbridge does the materialization. Opt-in and additive: arun with no preset is unchanged. Driving the exposed loop as a run phase is the
follow-up (Open Loop: drive the domain loop as a run phase #252).
c28c373: the-framework.yml gains an
event:key so a repo can pin its build event kind (e.g.bug-fix) alongsidepreset/autopilot/technical. Precedence:--kindflag >the-framework.ymlevent > preset default >major-change.74a9907: CLI:
--preset <name>runs a build under an Open Loop domain preset, with--autopilot/--technicalmode flags (framework CLI: --preset <name> + --autopilot / --technical mode flags #256).--presetresolves a shipped domain preset by name (viabuiltinDomainPresets+selectPreset) and hands it torunFramework, so its loops, prompts, and skillsframe the build.
--autopilot/--technicalactivate the preset'sconditionsvariants (applied at load time and narrated). An unknown preset name is a usage
error that lists the available presets; the mode flags note when given without a
preset. Additive: a run with no
--presetis unchanged.8c3e7d0: The domain loop drives the production-grade review phase (Open Loop: drive the domain loop as a run phase #252).
When a run has a domain preset, its review loop now replaces the built-in
checklist: each pass dispatches a
major-changeevent through the preset'sdriver-backed loop, so its review chain (e.g. code review, test coverage, security
review) fires through the wrapped agent, and Bootstrap's pass / improve / maxPasses
machinery gates on the union of the
{ blockers }verdicts the chain reports. Apreset with no loop for the build event falls back to the built-in checklist, so a
run is never left unreviewed. New:
domainLoopChecklist+verdictFromLoopRun(@gemstack/framework).
The shipped Software Development preset's review prompts (code review, test
coverage, security review) now end with a
{ blockers }verdict so the loopactually gates rather than only running.
c24ae22: Read
the-framework.ymlfor per-repo Open Loop defaults (framework: read the-framework.yml for per-repo preset + modes defaults #258).A project can now carry its own domain preset + modes, so you do not retype the
flags each run:
The CLI reads it from the run's workspace and merges it with the flags:
--presetwins over the file's
preset;--autopilot/--technicalOR with the file'sbooleans (a flag only ever enables a mode). A missing file is a no-op and a
malformed one is a warning, never a failed run. New exports:
loadFrameworkConfig,parseFrameworkConfig,mergeRunConfig,FRAMEWORK_CONFIG_FILES,FrameworkFileConfig.edd242b: Repo files as persistent AI memory (Repo files as persistent AI memory (CODE-OVERVIEW / KNOWLEDGE-BASE / ...) #260).
The agent now reads the project's special files (CODE-OVERVIEW.md,
KNOWLEDGE-BASE.md, BRAINSTORMING.md, DECISIONS.md) at the start of a run and is
told to keep the ones it owns current, so a project's memory lives in the repo as
plain markdown and the next run picks up where the last left off.
DECISIONS.mdstays framework-owned (we write it from the decisions ledger), so the agent reads
it but does not edit it. New:
loadRepoMemory(cwd),memoryFraming,MEMORY_FILES, and amemoryoption onrunFramework; the CLI reads the filesfrom the workspace and frames them alongside personas and skills.
Patch Changes
@gemstack/example-autopilot-quickstart@0.0.7
Patch Changes
@gemstack/example-bootstrap-quickstart@0.0.7
Patch Changes
@gemstack/example-framework-demo@0.0.4
Patch Changes
@gemstack/example-framework-discovery@0.0.4
Patch Changes
framework-hello@0.0.3
Patch Changes