Skip to content

Latest commit

 

History

History
38 lines (24 loc) · 3.73 KB

v1.1.1.md

File metadata and controls

38 lines (24 loc) · 3.73 KB

Foreman 1.1.1

Foreman 1.1.1 is a maintenance release for the installer, plugin bundles and state runtime introduced in 1.1.0. Skills, diagnostics, playbooks, output templates, research guides and the advisory policy are unchanged.

Installation

Requires Node 22.19 or newer and a supported AI host.

npx foreman-sh init

Use npx foreman-sh@1.1.1 init to pin this version. Add --platform codex or --platform all as needed and --workspace /path/to/project to select the destination. The installer preserves existing files, prints the next steps and, when a CLAUDE.md already exists, names the one line to add. npx foreman-sh --version reports the installed version. The GitHub release includes the npm tarball and its SHA-256 checksum.

Upgrading from 1.1.0

Run npx foreman-sh init again in the project. It fills missing files and lists the thirteen command guide files that the 1.1.0 installer placed in .claude/commands/, such as execution-commands.md and solo-command.md. Delete those files: Claude Code shows each of them as a slash command until they are removed. Their replacements are installed under .claude/command-guides/, and the generated wrappers in .claude/commands/ point there.

Existing .foreman/ records keep working without migration. The next write adds .foreman/.gitignore, so the store stays out of version control. A preserved 1.1.0 CLAUDE.md still loads Foreman; replace it with the installed template from templates/CLAUDE.md in the package to get the shorter founder-facing instructions.

Changes

  • Command guides live in .claude/command-guides/; only generated wrappers remain in .claude/commands/, and the build refuses anything else there.
  • The npm package, plugin bundle and initialized workspaces exclude settings.local.json, dotfiles such as .DS_Store and the plugin-only plugin-commands/ wrappers.
  • The bundled runtime rejects a checkpoint for a playbook that is not in the catalog or a step beyond the playbook's length. The catalog now records each playbook's step count.
  • foreman-sh --version, -h and a usage screen; init prints next steps, the line to add to a preserved CLAUDE.md, and any legacy guide files in an upgraded workspace.
  • A founder-facing project CLAUDE.md replaces the repository's development instructions in installed workspaces.
  • The CLI imports lib/ directly, so node bin/cli.js init runs from a fresh clone without a build.
  • OpenClaw development dependency 2026.9.1; npm audit reports no vulnerabilities in any dependency.
  • Getting-started, security, architecture and contribution documentation aligned with the shipped commands and installation flow.

Verification and limits

The 25 automated tests, content validation of 287 files and 4,152 typed references, TypeScript checks, release metadata checks and installation of the packed tarball pass locally on Node 24 and Node 22. CI checks macOS and Linux with Node 22 and 24, including installation of the actual npm tarball and freshness of the committed bundles.

The live advisory and fresh-session state acceptance recorded for 1.1.0 was not rerun for this release. The advisory policy, skills, diagnostics, playbooks, modes and research guides are byte-identical to 1.1.0; the changed instruction files are RUNTIME.md, the generated command wrappers and the new project CLAUDE.md, which restates the runtime and advisory contract in shorter form. The opt-in runners now set up scenario workspaces through the installer, so a future acceptance run exercises exactly the installed files. Model answers remain variable; diagnostic routes are hypotheses to review.

Foreman is free under the MIT license. AI host accounts and model usage are separate. Runtime records belong in .foreman/, outside version control.