# Update permission proof

AI-assisted; verified with the tests and tools listed above.

Manual real web-app comparison, Chromium preview, 1280 × 800 CSS pixels (2560 × 1600 capture), light theme, independent fresh databases. No agent turn was needed. No UI or RPC response was mocked. Base and head use their exact respective web source.

The scenario documentation was read first. The t3.project/t3.thread fixture cannot create a legacy bearer history or a managed-runtime update installation, so this proof used the documented manual alternative. A scoped pairing session missing environment:maintain represents the surviving narrow grants. This does not prove an actual historical-build upgrade/migration.

## Fixture

Run setup.mjs once per checkout, with dependencies installed:

```
EVIDENCE_DIR=<new-scratch-directory> node setup.mjs <checkout> base 20
EVIDENCE_DIR=<same-scratch-directory> node setup.mjs <other-checkout> head 10
node prepare-runtime.mjs <base-run.json> valid lab
node prepare-runtime.mjs <head-run.json> valid lab
```

The setup starts a primary web/server and two separate remote service launchers, Office and Lab. It temporarily sets the server package version to 0.1.7 while those remote processes start, then restores 0.1.8 before the primary starts. Runtime service-state and install sentinels make those source-built services managed installations. prepare-runtime.mjs stages a source-built 0.1.8 target. This avoids requesting unpublished 0.1.9. The update command, permission checks, launcher preflight, restart, version handoff, and reconnect all execute for real. This verifies a prepared development-runtime update, not downloading a published binary archive.

Office receives a bearer session with orchestration:read, orchestration:operate, settings:write, filesystem:read, access:read and no environment:maintain. Lab receives the default full-grant session. All data is synthetic. Pairing tokens remain local and are intentionally absent from these files. Regenerate expired tokens with the CLI auth pairing create command, using the same scope arguments in setup.mjs.

## Browser sequence on each commit

1. Open that run's primary pairing URL locally, finish onboarding, and connect Office using connectPairing.run (browser-actions.mjs). Dismiss any one-time notice. Open Settings → Connections (this revision labels its panel Environments).
2. Record hovering and clicking the disabled Office update icon. On base, obtain the actual button rectangle and use its center for pointer actions because disabled buttons do not accept a forced Playwright click. On head, hover/click its parent span wrapper. Capture after stable rendering: two screenshots 500 ms apart must be byte-identical. The base post-click still is not submitted as a second distinct outcome; the recording shows the no-op interaction.
3. With Office as the only outdated connection, hover/click Update all. Base is enabled and silently does nothing. Head is disabled, provides the permission description on the button, and its focusable wrapper displays re-pair guidance on hover/click.
4. Pair Lab, which is also initially 0.1.7 and grants environment:maintain. Click Update all and record through reconnect. Both sides successfully reach 0.1.8 on Lab. Base omits a skipped-server notice. Head names Office as skipped while reporting Lab updated. runtime-observations.json contains the actual persisted committed update states.
5. Run seed-project.mjs for Office and create a synthetic empty thread through the real thread.create command (no agent turn). To exercise the text Retry branch, reconnect Office with a newly minted full-grant pairing token, immediately dispatch updateServer during reconnection (it fails with 'Office is not connected'), then reconnect using the restricted token. Do not reload: the failed update state is client-local. Both commits show the same failed-update banner. Hover/click Retry; use focusDismissNotice() then Shift+Tab to focus the head wrapper. Base has no aria-describedby; head describes why Retry cannot update and how to pair again.
6. Create one more synthetic git repository with origin https://example.invalid/team/sample.git, and add it as 'Shared example' to both Office and Lab using the project add CLI. Enable Automatically balance load in Connections. Open a new draft in that grouped project. Lab is already current, Office still outdated. Hover/click the auto-balance banner's Update all. Base silently no-ops; head disables it, gives a tooltip, and click shows the permission toast. Its button's aria-describedby resolves to the same explanation; the wrapper has tabindex=0.

## Capture processing and limits

All submitted stills were captured after the stability check and opened for inspection. Recordings were inspected with decoded frame contact sheets. Composer Retry images/video crop the bottom toolbar; auto-balance images/video obscure only the model selector with a gray rectangle. No update controls or explanations are altered. The base mixed video is trimmed to its first 32 seconds, including successful reconnect.

The head's individual wording remains 'Office server' while batch wording is 'Office'. This discrepancy is visible in the captures and was not changed in this proof.

The primary Settings Version-row Update is guarded by canMaintain before it is rendered, so a denied-primary text-button state cannot be reached there. The auto-balance popover's individual ServerUpdateAction is only rendered for a manual-update server; its manual-update explanation takes priority over permission denial. The shared denied text branch is demonstrated by composer Retry, and the banner batch wrapper is demonstrated separately. Desktop shell and touch hardware were not tested; wrapper click uses a real browser pointer action.
