# A2CR 0.1.8 Metadata Refresh

Status: release target
Repository scope: `public-release/`
Tag: `v0.1.8`

This release refreshes public package metadata after the Apache-2.0 local-only
transition. It exists because the immutable `0.1.7` PyPI metadata still included
older BUSL, Roo Code, hosted service, and API-key wording even though the public
repository and official MCP Registry had moved to the local-only OSS line.

## Scope

- Publish `a2cr-mcp==0.1.8` from the current Apache-2.0 public repository.
- Keep `server.json`, the Python wrapper version, and the Claude Desktop MCPB
  compatibility version aligned on `0.1.8`.
- Preserve the public setup truth:
  - no A2CR account required
  - no API key required
  - no hosted base URL required
  - optional `A2CR_LOCAL_DB` only
- Include the dependency updates and project-centered dashboard baseline that
  landed after `0.1.7`.

## Verification

Before publishing:

```powershell
python -m pytest tests/local_workspace tests/test_mcp_stdio.py tests/test_public_repository.py tests/test_spec_documents.py -q
npm test
npm run typecheck
npm audit --audit-level=moderate
python -m build
python -m twine check dist/*
```

After publishing:

1. Confirm PyPI latest is `0.1.8`.
2. Confirm PyPI metadata no longer contains `BUSL`, `Roo Code`,
   `A2CR_API_KEY`, `A2CR_BASE_URL`, or hosted-service setup wording.
3. Publish `server.json` as the new official MCP Registry immutable version.
4. Re-check downstream MCP directories and request refreshes where stale setup
   text remains visible.