v0.22.1

Added

• run status, run end and run start --reattach (with or without --worker-pid) run in Go with the same output, exit codes, run record, mirror and signed ledger rows as Node, as do run help, usage errors and unknown flags; a plain run start, run start --add-worker and run reload still hand over to Node with their own reason (B454)
• gates run runs in Go for every form Node completes: a run with no --run and no --block, custom, kind and formatter gates (pint and prettier in argv batches), repeat_new_tests with changed sources, JS Number forms of --timeout-ms (0x, 0o, 0b, exponent), unknown flags, no HOME (the user's home folder), a --timeout-ms over the timer limit (1 ms timer and Node's warning), an empty --run or --block and a missing --cwd, all as Node; a bad gate config stops with one stderr line that names the cause and the fix; only a run record with a mismatched run_id or no workspace still hands over; a command that cannot start is a red spawn-error gate; the block land gates step and the batch land preflight run the same Go path (B450)
• block open, block claim, block stop, block close and block land no longer hand over to Node: help, unknown flags, errors and the error log run in Go, block close checks light limits in Go, and every other case Go does not serve exits 1 with one block <sub>: refused: <cause> (<code>); <fix> line and writes nothing; only the land gates step still hands over (B450) (B451)
• block open, block claim, block stop, block close and block land serve help, unknown flags, errors and the error log in Go; block close checks light limits in Go, reads only the closing block's rows (another block's rows no longer hand the close to Node) and prints Node's detail for a rule_break row whose id is not text; no case is refused, and the cases Go does not serve yet still hand over to Node (B466 ports them) (B451)
• npm run release:site — after npm publish, waits until npm serves the version, builds the site data in an
  isolated worktree of the site repo, runs every site gate, commits only src/data/site-data.json on
  release-site/v<version> and deploys; a red gate deploys nothing; --dry-run stops before commit and deploy (B315)

Fixed

• gates run hands a gate command that is an executable file with no #! line to Node again (Node runs it with /bin/sh on Linux and refuses it on macOS; Go had shown a red spawn-error gate); context pack names node on PATH in the pack header when CODE_FORGE_NODE does not resolve, as before B452, instead of refusing; the Go test for gates run with no HOME no longer writes ~/.code-forge/queue in the real home; the Node parity tests now check the B449–B452 Go forms against Node instead of expecting a hand-over (B469)
• status, review-file, context: fewer Node hand-overs — Go runs every context form, status for array run records, an infinite spend and broken run files, and the review-file enqueue worktree and run-record-unreadable refusals; Node stays only for a non-ASCII block id in status and a few review-file states Go cannot read (B452)
• block rebase runs in Go in every form (--help, closed and awaiting blocks, --head, --accept-changed, --accept-landed), and block ready runs in Go with hooks.on_block_end and with close.require_human under an active autopilot grant; only run state Go does not expect still hands over to Node (B449)
• The config and command references now describe the merge gate as it runs: gates.merge_gate runs the Go test selection for the merge, never the full suite, reuses a green gate on the same tree (gate_reused) and is always on in a batch; block land usage lists --push, --watch-ci, --copy-links and batch land, and gates run usage lists --full, --preflight and --no-preflight (B444)
• npm run release:site deploys the merged site folder docs-site/site/.pages-out (marketing pages plus /docs)
  instead of dist, which has no /docs; --deploy-dir <path> picks another folder inside the site root, and a
  missing folder or index.html after the gates stops before commit and deploy (B446)
• block land output no longer says the merge gate runs the full suite: --no-merge-gate warns merge gate skipped; the merged tree was not checked, a batch refuses it with a batch always runs the merge gate; --no-merge-gate is refused, a red gate stops with tests failed: and a missing test command with test gate unavailable: configure gates.test before merging; help lists every block land flag and batch land (B447)
• code-forge ci watch survives the GitHub API rate limit: a rate-limit reply is never a CI result; it waits until the reset from gh api rate_limit (else backs off 60 s doubling to 15 min), prints ci watch: GitHub API rate limit; retry at HH:MM UTC per wait, and past --timeout exits 4 with rate limit, gave up instead of a failure; polling stays at one call per 30 s, and a second watch for the same repo and commit exits 0 without starting (B448)

npm: https://www.npmjs.com/package/@codedology/code-forge/v/0.22.1
Full changelog: https://github.com/ricardov03/code-forge/blob/v0.22.1/CHANGELOG.md