Releases: leblancfg/pi-fusion
Releases · leblancfg/pi-fusion
Release list
v0.4.2
What's Changed
- Publish releases through npm trusted publishing with GitHub Actions OIDC.
Verification
- CI passed on the version bump PR.
- The publish workflow verifies the tag matches package.json before publishing.
v0.4.1
What's changed
- Preserve the newest fusion conversation context when the context byte budget is tight. Older messages no longer evict the latest user/assistant exchange when fusion builds worker prompts.
- Stop saving transient next-turn
enabledstate in fusion presets. Presets now capture reusable configuration without accidentally arming or disarming the next fusion run. - Verify the npm package contents in CI with
npm pack --dry-run, so packaging allowlist or dist-output issues fail before release. - Bump the package version to
0.4.1.
Note: this GitHub release does not publish the npm package. npm publishing is handled separately.
v0.4.0
What's changed
- Run fusion sub-agents with the user's other extensions enabled. Previously every sub-agent was spawned with
--no-extensions, disabling all extensions. Now only pi-fusion opts itself out (via thePI_FUSION_SUBAGENTenv var) so discovery, rewrite, and worker sub-agents can use installed extensions without recursive fusion. - Add a "Session file" docs page documenting the
pi-fusion-settings,pi-fusion-run, andpi-fusion-archiveentries, their schemas, and how to reconstruct or extend them.
v0.3.0
Full sub-agent transcripts are now archived in the pi session file, keeping a fused turn auditable and resumable without inflating the context window.
Highlights
- Session archive. Complete, untruncated discovery/rewrite/worker transcripts are saved as non-context
pi-fusion-archiveentries (chunked for storage only, never semantically truncated). pi's context builder never feeds them to the model. - Bounded resume handoff. A single
custom_messagecarries a budgeted worker-conclusion summary plus a pointer to the run id. This is the only fusion content resumed/subsequent turns see, capped by--fusion-resume-bytes(default 8000). /fusion-transcriptcommand to view,list, or--writethe full archived transcript for any run.
Why
Separates three audiences with three byte budgets: the synthesis turn (fusion-output-bytes), durable future-turn context (fusion-resume-bytes), and worker inputs (fusion-context-bytes). Full fidelity for audit/resume; clamped context for everything downstream.
v0.2.1
v0.2.0
What's changed
- Make all
pi-fusionprompts visible and editable in fusion.json. - Write default prompts on first run.
- Merge global and project prompt overrides per field.
- Resolve project fusion config from ancestor project roots.
- Ignore malformed
fusion.jsonfiles instead of crashing. - Preserve the fusion actor marker for custom actor prompts.
- Fix fusion pane title borders.
- Publish compiled dist extension files and validate the dist entrypoint in CI.