Repository navigation
Releases: TheLithiumForge/open-forge
Releases · TheLithiumForge/open-forge
Release list
v0.9.0-beta.14
docs: keep the Task 81 record in Working until the beta14 records commit The previous commit carried a staged move of the record without its link updates. The record returns to Working, and the release records commit archives it with every link rewritten.
v0.9.0-beta.13
fix(delivery): link the osx-arm64 native Integration tests with Apple…
v0.9.0-beta.12
fix(delivery): annotate failed node:test checks in CI and wait for re…
v0.9.0-beta.11
chore(release): prepare 0.9.0-beta.11 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v0.9.0-beta.10
chore(release): prepare 0.9.0-beta.10 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v0.9.0-beta.9
fix(delivery): declare the Windows-only frontmatter question journey The published Install frontmatter question test drives the interactive prompt through the repository's Windows ConPTY harness and skips elsewhere. Declare its exact reason as a Windows-only public exclusion so Linux and macOS qualification accepts it, with delivery tests that keep the reason strict on Windows and in other suites. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v0.9.0-beta.8
fix(delivery): declare Windows registration exclusion
v0.9.0-beta.6
Open Forge remains Markdown, rules, and links. This beta makes the first setup easier to explain and lets a workspace grow as needed.
- Start with one ten-minute guide directly after Getting Started, with short Directive, Pattern, Skill and Memory examples.
- Choose Essentials, Full Core or Custom during interactive installation. Custom offers Add, Remove or Add + Git-ignore for each built-in category.
- Revisit choices and restore eligible missing defaults with
install --configure; restore one canonical route withroute init --framework. - Load the CLI usage Skill at startup when present. The summarized reference and Skill cover command flags and their useful cases, including batched Context reads and targeted Find searches.
- Keep selection wizards readable in small terminals and after resizing.
- Choose whether Library attachments Git-ignore their exact projected links.
--git-ignore true|falsesupports unattended use; Sync, Detach and Remove maintain the corresponding rules. - Preserve authored content, overwrite companions, intentional omissions and unrelated ownership during setup and restoration.
- Correct Install handling of safely superseded recovery snapshots in reused workspaces, retaining historical recovery data.
- Remove superseded drafts, archive completed tasks and analyses, and bring retained Memory records up to date.
Install the beta through npm install -g @thelithiumforge/open-forge@beta, or download the portable archive for your platform below.
Open Forge 0.9.0-beta.4
Open Forge 0.9.0-beta.4
Open Forge beta.4 focuses on safer, more predictable CLI behavior and clearer guidance.
- More reliable context and search. Plain
open-forge contextno longer crashes when a rule applies only to matching files. FilteredFindresults retain complete route details without adding excluded matches. - Safer, more accurate updates. Framework Update uses verified registered Library sources for navigation. Extension Update repairs stale generated navigation and preserves authored host content. Applied change counts now come from verified effects.
- Safer route moves and diagnosis. Route moves preserve unrelated references that are already missing, while affected or unsafe references still refuse the operation. Doctor separates generated navigation drift from edited managed content.
- Clearer Library ownership. Library may refresh a host's generated navigation without claiming ownership of the host file.
- Clearer help and documentation. Empty Extension-list and dry-run wording is corrected, force and Create confirmation help is clearer, recovery follow-up guidance is improved, and refreshed current docs now have an offline CI gate for broken local links and anchors.
Install beta.4 with:
npm install -g @thelithiumforge/open-forge@0.9.0-beta.4v0.9.0-beta.3
Use visible managed host boundaries with legacy Update migration