[ancongui]

Large coding-provider events lost their trailing outcomes when the activity feed truncated JSON at 8,000 characters. Retain complete sanitized messages within explicit archive limits and present recognized commands, previews and exit codes in Studio. Full-content reads verify the descriptor and complete bytes under current project access and credential checks. HTTP, SDK, CLI and MCP share that contract. Bounded evidence exports retain references; historical events are not backfilled.

Distinct provider recoveries produce distinct source-control milestones even when they end in the same run status. Runs without a recovery retain their original fingerprints. GitHub polling feedback also rechecks the exact comment, current provider permission and native authority after token preparation. Edited or revoked requests remain held without a post or replay. The remote check and GitHub write are separate operations; this does not promise atomic remote revocation.

Protect interrupted-effect cleanup from concurrent cancellation and retain its storage fence until it drains. Two deterministic regressions fail on the earlier source and pass with the fix; the original native no-replay assertions remain intact.

Prepare 0.2.25, update the README and guides, and regenerate all 424 documentation capture records through 48 controlled browser producers. These screenshots illustrate fixtures, not a completed generated product.

Validation:

• 164 combined host tests, five native activity-archive cases, and 19 native worker/shutdown cases pass. The additional token-boundary fix passes 21 affected native cases and 69 host cases, with an independent five-path review.
• 504 Studio units, 33 existing evidence browser cases, five new archive browser cases, all 94 documentation browser cases, strict documentation, lint, types and production build pass on their qualified inputs. The final backend/docs delta changes no screenshot inputs.
• The final de810fd35201ab28cd6c86c3ed3a85d53d4b982b wheel and source archive pass exact membership, metadata and RECORD checks, followed by a new installed-artifact smoke outside the checkout.
• Earlier complete CI exposed a missing build fixture and ten obsolete catalog/schema expectations. The build input is now included. The test correction preserves all original 145/150-tool wire, hash and callback-AST baselines; all eight affected MCP cases and both native migration cases pass. Failed runs and logs remain preserved.

Complete CI for exact head de810fd35201ab28cd6c86c3ed3a85d53d4b982b remains pending. No live coding-provider recovery or generated-product acceptance is claimed.