lwc v0.19.5

Manage team and space deletion safely with a recycle bin, authorized restore, and preserved local memory.

• Team owners and space managers can preview, confirm, delete and restore resources in the bilingual console. Deletion retains memory; team restore leaves independently deleted spaces in the recycle bin.
• A team's revision changes when spaces are created, deleted or restored, so an old confirmation cannot unexpectedly affect a changed set of spaces. Errors appear inside the dialog; reload the preview before confirming again.
• Current space managers can hand over or revoke permissions while resources are archived; current team owners can remove members. Last-owner and last-manager protections remain in place, and memory access stays denied until restore.
• Sync errors at any stage, including after the initial permission check, suspend local shared writes on HTTP 401/410 or a space-wide HTTP 403. Resource-specific permission denials continue to constrain only the affected operations. Pending edits, SQLite and Wiki content remain available as evidence; restoration resumes normal synchronization.
• Native Hooks and CLI/MCP responses signal deletion without forcing an unrelated semantic conflict loop. Final publication checks reject in-flight writes that lost authorization.

The team control database migrates from schema 6 to schema 7. Stop the old server and take a complete backup before upgrading. Keep the old binary/image, administration assets and backup for rollback; an old 0.19.4 server cannot read the migrated control database. Never lower the schema number manually.

Soft deletion is reversible and does not permanently erase memory or clear client replicas. Restores use current permissions and do not re-enable old invitations. Publication does not upgrade an existing self-hosted deployment automatically.

Pro passed 8 targeted team tests and 15 real HTTP/CLI acceptance groups. A separate fault-injection run deleted a space after the client read head and before upload, proving immediate write suspension, pending-content preservation and successful sync after restoration. System Chrome verified stale confirmation rejection, visible dialog errors and fresh affected-space counts. See the lifecycle report.

Formal release gates additionally verify packages, all six native targets, the team container and release-asset installation before GitHub publication.

Install with npm install -g @i-xor/lwc@0.19.5, cargo install lwc --version 0.19.5 --locked, or checksum-verified GitHub release assets. Homebrew users can upgrade after the tap formula updates. Self-hosted operators can use ghcr.io/janyork/llm-wiki-cli-team:v0.19.5 after publication, following the backup and rollback instructions above.