v0.1.2 — Skills show their descriptions again

forge skills install now writes its marker below each skill's frontmatter instead of above it. With the marker first, Claude Code read the marker line as the skill's description, so it never picked a forge-* skill up on its own; the skills only ran when called by name.

All three packages ship together at 0.1.2: @forgedesign/cli, @forgedesign/format, and @forgedesign/scenarios. Only the CLI changed. The Design Record format version remains 0.2.

Upgrade, then reinstall the skills to repair copies written by 0.1.0 or 0.1.1:

npm install -g @forgedesign/cli@latest
forge skills install          # or: forge skills install --home

Validation: 622 public tests, build/typecheck/lint/unused-code checks, version check, forge doctor, and a scratch install confirming each SKILL.md opens with its frontmatter.

v0.1.1 — Cloud connectivity restored

The published CLI reaches Forge Cloud at app.useforge.design again. Existing logins that saved https://useforge.design follow automatically, with their token preserved; custom Cloud addresses stay unchanged.

Publishing uses Cloud's staged-upload protocol: declare sizes and hashes, upload directly, then commit after every upload succeeds. The release includes upload retries, the frozen tag's message, and the updated PIN-management link. Existing library import paths and intake behavior remain compatible with 0.1.0.

All three packages ship together at 0.1.1: @forgedesign/cli, @forgedesign/format, and @forgedesign/scenarios.

Upgrade:

npm install -g @forgedesign/cli@latest

Validation: 620 public tests, build/typecheck/lint/unused-code checks, CI, record validation, and 11 clean-install routing/upload checks. Saved-token identity and comments checks succeeded against the app host; real HTML, CSS and Markdown staging uploads succeeded after the Cloud MIME-constraint fix. No review version was published by those staging probes.

v0.1.0

First public release. All three packages are published under one version number.

Install

npm install -g @forgedesign/cli
forge init ../my-prototype
forge skills install --home

Node 20 or later.

What is in it

• @forgedesign/cli: the forge binary. It handles init, and doctor checks the record: ids are unique, references resolve, statuses are valid, and accepted decisions haven't been quietly edited.
• @forgedesign/format: the parser and serialiser every tool uses to read a record, so there is only one grammar.
• @forgedesign/scenarios: a browser runtime with zero dependencies. A prototype imports it so a reviewer can open the app from a URL as a particular role with particular data.
• Six agent skills for Claude Code and Codex: forge-init, forge-intake, forge-ddr, forge-triage, forge-review, forge-freeze.

A record is markdown with frontmatter, stored in git. The skills do the thinking in your agent session, and only the CLI writes to the record.

Forge Cloud (forge login, forge publish) is a separate commercial service and a closed beta. Nothing else in this repo needs it.