Start required local services without changing configuration

[shiny-code-app]

Agents can skip local validation or ask the owner unnecessarily when a required local service is stopped. Shared execution guidance now tells them to start the required local service or app, record what they started and why, and ask for missing authority when startup affects others, remote or production systems, paid resources, or effects that cannot be established.

Startup must leave login behavior, machine settings, and service configuration unchanged. Failures and workarounds are reported; fixes for why a service was stopped remain follow-up work under existing planning and posting authority. The task report is the fallback when no PR or issue write is authorized.

Refs #771. Land after the cross-repository instruction change in PR #782, following the owner-requested sequence.

Validation: existing catalog structure/reference, behavior, command-policy, and public-safety validators pass. Markdown guidance only; no executable code changed, so IDE inspection was not run. The shared reference is reached through the same execution-skill links on both supported harnesses.

Review: Anthropic claude-opus-5-5[1m] reviewed the initial diff and the revised final diff. Acted on the recording/follow-up authority concerns and made the no-configuration-change boundary apply to the start action itself. Installed Homebrew help confirms that a start command can register login startup while its run command does not. Unknown external effects now explicitly require clarification because a wrong assumption could affect production or paid resources.

Six bounded decision cases covered ordinary local startup, known production/billing effects, disabled login startup, an explicit leave-all-local-state-unchanged request, a startup command with login-registration effects, and unreadable configuration that determines remote billing. The decisions were to start only the ordinary local dependency, preserve explicit read-only restrictions, choose a non-registering startup method, and hold uncertain/external effects for the needed information or approval. These were decision exercises, not live service-start evidence.

The final review's read-only ambiguity was declined as a policy expansion: the existing explicit user-instruction and read-only boundaries still apply, and the strict read-only case held startup. One case is not a general reliability claim. The suggestion that reporting a workaround grants configuration-write permission was declined: reporting does not authorize execution, and the adjacent configuration and follow-up constraints remain explicit.

No release or deployment workflow is triggered. Background auto-review: not yet observable at PR creation. Alert API availability is recorded in PR #781; unavailable signals are not described as clean. Merge authorization already covers this change; its merge remains sequenced after the prior two PRs.

[shiny-code-app]

Final bounded case against the revised source: when startup failed from a port conflict and recovery required a service configuration edit, the agent left configuration untouched, reported the blocked checks, and proposed the cause fix as follow-up work. The explicit leave-all-local-state-unchanged case was also rechecked and held startup. No real service operations or configuration writes were performed in these decision cases.

[shiny-code-app]

This branch now includes the two preceding landed guidance changes. At head c02d9b6177947d7736caa0aca2106ac17764403d, its diff against main is still only the local-service prerequisite rule. Catalog structure/reference, behavior, command-policy, and public-safety validators pass. The independently reviewed rule itself is unchanged by the base update; the existing decision-case evidence remains applicable. No new scope, model-review finding, or owner decision was introduced.

[shiny-code-app]

The requested series is complete in order: communication guidance, target-repository instruction reads, then this local-prerequisite rule. All three plan issues are closed with plan:done; independent reviews, final-head CI, post-merge catalog validation, and CodeQL results are recorded.

Runtime reconciliation succeeded after each merge. Final main is clean and matches remote at 51a87a0b93e63334f34fe4009dc9c7911153462e. The three task worktrees and local branches were removed using normal Git removal after ancestry, local-content, ownership, and volume checks. Unrelated worktrees and shared interpreter targets were preserved. Synthetic fixtures were archived and verified before removal; private review/inspection evidence remains retained for the related snapshot investigation. The accepted PyCharm exception on the first PR remains explicitly recorded as inconclusive evidence, not a clean inspection.

No owner decision or required work remains for these three issues.