👷 Prepare automated package releases

[nbsp1221]

Summary

• Set the initial package version to 0.1.0 and source runtime version metadata from the package manifest.
• Add release-it automation for version commits and tags, then publish tagged releases through GitHub Actions using npm Trusted Publishing without a long-lived npm token.
• Generate the corresponding GitHub release after a successful package publish and let npm determine provenance for each publishing environment.

Verification

• pnpm check — formatting, linting, typechecking, 40 unit and integration tests, and the production build passed.
• pnpm release --ci --dry-run --no-increment --no-git.requireBranch --no-git.requireUpstream --no-git.push — simulated the initial release flow without changing Git state or pushing.
• npm pack --dry-run --json — produced the expected seven package files for chat2shell@0.1.0.

[leverframe]

Leverframe review

🟢 Incremental review completed in 317s

• 0 new findings
• 2 existing findings were verified fixed
• 3 of 3 changed files reviewed
• Verification: 6 passed

Changes d3aca4c..50d8251 · Commit 50d8251 · View check run

[leverframe]

Leverframe review

The code, lockfile, package contents, and stable-version build pass under Node v24.20.0, npm 11.19.0, and the declared pnpm 11.23.0. Two release-workflow defects remain: prerelease tags cannot publish, and a post-publish failure cannot be recovered by rerunning the workflow.

Findings

2 findings were published inline.

Checks

6 passed · 1 failed · 0 not run

Show 7 checks

Status	Check	Evidence
🟢 passed	node --version; pnpm --version; npm --version	Selected repository/CI-compatible environment: Node v24.20.0, pnpm 11.23.0, npm 11.19.0.
🟢 passed	pnpm install --frozen-lockfile	Installed 464 packages; the lockfile was current and passed pnpm supply-chain policy verification.
🟢 passed	pnpm check	Formatting, oxlint/eslint, TypeScript checking, 40 unit/integration tests, and the tsdown production build passed.
🟢 passed	node dist/cli.mjs --version; npm pack --dry-run --json	The built CLI reported 0.1.0 and the package dry run produced a valid chat2shell@0.1.0 tarball containing the executable and declared files.
🟢 passed	pnpm exec release-it --dry-run --ci --increment=prepatch --preRelease=beta	In a temporary main-branch clone with an upstream, release-it resolved 0.1.0 to 0.1.1-beta.0 and showed the matching commit, annotated tag, and push operations.
🔴 failed	npm publish --dry-run --loglevel notice	Against a temporary 0.1.1-beta.0 build, npm 11.19.0 reproduced the defect: You must specify a tag using --tag when publishing a prerelease version.
🟢 passed	git diff --check 3169bd993f8492089316aecf6a2c1e6e39dc21ec...d3aca4cf4e3d13b802516fc28cd3295d3d74e39e	No whitespace errors were reported.

Limitations

• No real npm publication or GitHub release was performed because review scope forbids publishing and GitHub credential use. The release state transitions were verified through dry runs, installed implementation behavior, and focused temporary-clone simulations.

• Docker Sandbox E2E tests were not run; repository guidance excludes them from the normal quality gate, and this diff does not alter sandbox behavior.