chore(release): 0.8.2

[archgatebot]

archgate

0.8.2 (2026-03-04)

Features

• add Windows (x64) build and CI smoke test (#20) (e579520)
• distribute binaries via npm platform packages (#7) (9fc775c)
• docs: add Brazilian Portuguese i18n and GEN-002 ADR (#30) (291f1d7)
• docs: add Cloudflare Web Analytics (#33) (fe615a0)
• docs: add Starlight documentation site (#23) (0bf9653)
• docs: port terminal/editor chrome from marketing site (#34) (2457f87), closes #1a1a1 #0f0f0 #f8f9 #eef0f2
• init: add Cursor editor integration with MCP and governance rules (#15) (912405b)
• login: add github auth and plugin install for init (#21) (e2ec02c)
• mcp: add cursor_session_context tool (#17) (a82c5b6)

Bug Fixes

• add .gitkeep to archgate-win32-x64 bin directory (#36) (204a2e1)
• ci: add auto-install to deploy-docs toolchain setup (#26) (cc5805b)
• ci: add explicit permissions to workflows (#38) (0289273), closes #1 #2 #3
• ci: upgrade npm to v11 for OIDC trusted publishing (#41) (13341f3)
• ci: use npm trusted publishing (OIDC) instead of secret tokens (#40) (49d94ad)
• ci: use workflow-scoped concurrency groups for PR pipelines (#37) (552da08)
• drop --provenance (private repo), use npm-token input for release (fa7f042)
• improve packaging (#4) (1d8245a)
• mcp: start server without a project and guide onboarding (3df4ee6)
• move bundled deps to devDependencies to avoid unnecessary installs (#19) (2a6d62f)
• replace Bun.$ shell calls with Bun.spawn for Windows compatibility (#43) (ca33377)
• upgrade: switch from GitHub API to npm registry for version checks and install (96ac92a)
• use ./ prefix for npm publish to avoid GitHub shorthand resolution (79dce8d)
• use NPM_TOKEN for registry auth alongside --provenance (394d2c5)
• use NPM_TOKEN secret instead of OIDC for npm publish (4704f33)
• use OIDC provenance for platform packages, NPM_TOKEN for main package (b8ce61d)

---

This PR was generated with simple-release.

📄 Cheatsheet

You can configure the bot's behavior through a pull request comment using the !simple-release/set-options command.

Command Format

!simple-release/set-options

```json
{
  "bump": {},
  "publish": {}
}
```

Useful Parameters

Bump

Parameter	Type	Description
version	string	Force set specific version
as	'major' | 'minor' | 'patch' | 'prerelease'	Release type
prerelease	string	Pre-release identifier (e.g., "alpha", "beta")
firstRelease	boolean	Whether this is the first release
skip	boolean	Skip version bump
byProject	Record<string, object>	Per-project bump options for monorepos

Publish

Parameter	Type	Description
skip	boolean	Skip publishing
access	'public' | 'restricted'	Package access level
tag	string	Tag for npm publication

Usage Examples

Force specific version

!simple-release/set-options

```json
{
  "bump": {
    "version": "2.0.0"
  }
}
```

Force major bump

!simple-release/set-options

```json
{
  "bump": {
    "as": "major"
  }
}
```

Create alpha pre-release

!simple-release/set-options

```json
{
  "bump": {
    "prerelease": "alpha"
  }
}
```

Publish with specific access and tag

!simple-release/set-options

```json
{
  "bump": {
    "prerelease": "beta"
  },
  "publish": {
    "access": "public",
    "tag": "beta"
  }
}
```

Access Restrictions

The command can only be used by users with permissions:

• repository owner
• organization member
• collaborator

Notes

• The last comment with !simple-release/set-options command takes priority
• JSON must be valid, otherwise the command will be ignored
• Parameters apply only to the current release execution
• The command can be updated by editing the comment or adding a new one

[rhuanbarreto]

!simple-release/set-options

{
  "bump": {
    "as": "minor"
  }
}