v1.0.0-alpha.2

portable-devshell v1.0.0-alpha.2

This is the second 1.0 prerelease, focused on upgrade safety, Extension-owned persistence and collaboration, and MCP App usability. It is an alpha release for controlled evaluation, not a stable release.

Highlights

1. Host-owned Extension database capability: Extensions use a scoped host-owned SQLite API rather than privately opening their persistent databases. Comment and Agent provider state now use the database capability with lifecycle-aware acquisition, transaction rollback, and sandbox/permission-model tests.
2. Real 0.7.7 upgrade and rollback coverage: the installer snapshots persistent state before replacement. Testspace covers legacy Audit v2-to-v3, Context v1-to-v2, Comment v1-to-v2, and Agent JSON-to-SQLite migration; startup failure, partial migration failure, and unsupported schema paths preserve or restore the prior installation.
3. Agent-work mailing through Comment: Contexts can claim an agent-work identity and exchange queued messages with other agents using the existing Comment and Worker capabilities. Mailing has its own Domain entry and tests with local and Reverse instances, without adding another model-facing MCP tool.
4. MCP App presentation split: an explicit Workspace uses fullscreen mode, while ordinary ToolCalls can show optional compact Inline cards with semantic command, file, and result renderers. The Workspace exposes scoped ToolCall history and paged retained terminal output. Approval/Ask/Wait interactions remain Inline; resource aliases support loading older content-hashed cards.
5. CLI and infrastructure reliability: devshell instance create is supported through the existing CLI/model-command surface instead of a separate MCP tool. ToolCall rewrite keeps host session authority; Web static asset roots and the Core Audit migration scan receive additional path/symlink validation.

Compatibility and operational guidance

• Protocol compatibility is not a replacement guarantee. The installer replaces Control and Worker as an offline unit; its preflight reports Control, Worker, and Frame protocol range mismatches without treating a disconnected prior generation as a live protocol peer. Unsupported persistent schemas and malformed protocol ranges are still rejected.
• Legacy data migration is bounded. Existing 0.7.7-format persistent data is migrated; much older unsupported schemas are not reintroduced. Back up installation and configuration state before upgrading. Failed migration restores the prior version and state, as exercised in Testspace.
• No new MCP provisioning tool. Instance creation remains an existing CLI capability and Mailing reuses Comment. The MCP App's historical resource URI aliases serve the current bundled viewer; this is not an archive of every historical JavaScript/CSS bundle.
• Agent remains separately installed. The Release includes a platform-neutral Agent Extension archive, but not its managed model-provider dependencies.

Verification

• Local source/test TypeScript checks, Domain import rules, ESLint, complete workspace build, package tests and script tests passed on Linux x64. The final package test run exited successfully; the Web suite passed 175/175 in its normal Node 26/JSDOM environment.
• An isolated Linux Testspace used the published v0.7.7 baseline and the alpha.2 candidate. All five upgrade cases passed: successful upgrade, existing Comment target recovery, failed-startup rollback, partial Audit migration rollback across two databases, and unsupported-schema rejection.
• Node 26 still emits an upstream oidc-provider LTS-support warning. Chromium-dependent browser tests on the local test host were skipped because Chromium was unavailable; the GitHub Development CI separately installs Chromium and is required before Release publication.
• Official cross-platform release artifacts, SHA-256 verification, and any release-level CI results are controlled by the GitHub Release workflow; these local checks do not substitute for that workflow.

Refer to docs/development/acceptance.md and docs/development/compatibility.md for the supported test and compatibility contracts.

What's Changed

• fix(mcp): honor forwarded HTTPS on loopback proxies by @Y-M-Zhong in #1
• fix(mcp): recover expired OAuth registration approvals by @Y-M-Zhong in #2
• fix(build): unify Linux workers on cargo zigbuild by @Aromatic05 in #3
• perf: optimize audit storage and Control runtime by @Aromatic05 in #4
• fix: dedupe tmux audit and Workspace wake recovery by @Aromatic05 in #5
• test: repair CI overview fixtures by @Aromatic05 in #6
• fix(workspace): fence PiP remount reconnect loop by @Aromatic05 in #7
• fix(workspace): frame automatic continuation state by @Aromatic05 in #8
• fix(workspace): consume waits completed during agent activity by @Aromatic05 in #9
• fix(workspace): make reentry server authoritative by @Aromatic05 in #10
• fix(installer): fence rollback by runtime generation by @Aromatic05 in #11
• fix(tools): enforce namespace naming contract by @Aromatic05 in #12
• fix(release): close installer and testspace preflight gaps by @Aromatic05 in #13
• fix(release): complete second release audit by @Aromatic05 in #14
• fix(workspace): harden app lifecycle and negotiation by @Aromatic05 in #15
• feat(audit): record MCP tool provenance by @Aromatic05 in #16
• refactor(mcp): move control-plane tools to CLI by @Aromatic05 in #17
• feat(reverse): isolate bulk RPC traffic by @Aromatic05 in #18
• feat(audit): add provenance hot cold lifecycle by @Aromatic05 in #19
• feat(cli): add secret scanning by @Aromatic05 in #20
• feat(cli): add layered skill catalog by @Aromatic05 in #21
• fix(control): bound read workloads by @Aromatic05 in #22

New Contributors

• @Y-M-Zhong made their first contribution in #1
• @Aromatic05 made their first contribution in #3

Full Changelog: https://github.com/Aromatic05/portable-devshell/commits/v1.0.0-alpha.2