[trissim]

Summary

1 functional lockfile change: Toad 4402052367 → 3f7b3e3987 (merged Retry UI #1396), paired with merged Core #3839. No application source or release-version pins change. Current tracked branch mains were refreshed through existing RuntimeStack.resolve(); Textual, ui-theme, formbridge and metaclass-registry remain unchanged.

Mechanism

Before: updating Core alone leaves Toad's Retry button/slash handler on an older dependency. Expected generation refusals cross the owner RPC correctly but the installed UI cannot consume the repair.

After: the existing stack lock selects the merged Toad handler whose parameter is the declared AgentConnection, not a narrower ACP Agent. No second installer, exception adapter, alternate package source or compatibility alias.

Evidence

• Actual archived exact-source pair: Core14 passed/rc0; Toad12 passed/rc0. Results and origins: /home/ts/.cache/agent-scratch/pi-shell-colleague/retry-ui/paired-run-01/.
• Same-PR annotation correction:26 runtime method bodies unchanged; actual runtime import/compile pass; targeted mypy5→3 removes the two introduced errors, not the three named baseline findings. Hosted NRA SUCCESS at exact Toad a5a8; independently reviewed and merged3f7b3e39.
• RuntimeStack.resolve() refreshed all five tracked branch dependencies in1.620s, rc0. Exact pushed/rebased69ab239c5b Git archive, with its own index and actual archived-module import, passed NativeBuildInputs.require_pinned:62inputs, digest f97c26f0c7430b0fb795a56781919d6d308d1fc08c58689dac4b203c0ad59586. Receipt: heartbeat-publication/retry-paired-stack-archive.log/.rc (rc0). No native recipe/source change, so its pinned artifact remains unchanged.
• Core brace Reject unmodeled brace groups at the lexical boundary #3840 is independently reviewed with actual127 passed/167 subtests/rc0 and merged fb1eaaa; the source branch is rebased onto current main before publication so it can ride the same installation.

Installation / acceptance still owed

One supported InstallRun, preserving identities/sessions/UNKNOWN inputs/backups/protected clients, then live answered communication and Shell's copied-native/UI Retry journey on the actual new prefix/stamp. Git merge is not installed acceptance. No donor/carry/model duplicate job or fresh local full suite was launched for this pin.

Assumed: no behavior change from replacing only a parameter annotation/import (all26 method bodies and runtime import checked). Native/physical acceptance is not assumed; source tests are not the final app result.

[Copilot]

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.