From 62c2c805aa77ca6824e2ee73997b56d8b548c070 Mon Sep 17 00:00:00 2001 From: shiny-code-bot Date: Thu, 24 Sep 2026 10:45:02 -0400 Subject: [PATCH 1/2] Start required local services within existing authorization --- skills/references/execution-scope.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/skills/references/execution-scope.md b/skills/references/execution-scope.md index be8a5d1f..96279958 100644 --- a/skills/references/execution-scope.md +++ b/skills/references/execution-scope.md @@ -45,6 +45,14 @@ Apply these rules when using the repository execution skills that link here. edits overlap or ownership cannot be established, rather than treating every dirty checkout as a blocker. Isolation does not relax protected-branch or runtime-checkout rules. +- When a task depends on a local service or app on this machine that is not + running, start it without asking and record what you started and why in the + PR or issue. Ask first if starting it affects another person, a remote or + production system, or paid resources, reusing approval that already covers + those effects. If startup fails, report the failure and any workaround. Do + not change login startup behavior, machine settings, or service configuration + to fix why it was not running; track that work in follow-up issues for + direction review. - Run checks required by the repository and affected behavior. Reuse passing evidence for the same revision and environment; broaden or repeat checks when changes, failures, or unresolved risk justify it. Report missing required From 39e01373ef312032e6354da61115b8d0cbe7276d Mon Sep 17 00:00:00 2001 From: shiny-code-bot Date: Thu, 24 Sep 2026 10:48:39 -0400 Subject: [PATCH 2/2] Keep local startup within configuration and posting boundaries --- skills/references/execution-scope.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/skills/references/execution-scope.md b/skills/references/execution-scope.md index 96279958..1707559b 100644 --- a/skills/references/execution-scope.md +++ b/skills/references/execution-scope.md @@ -47,12 +47,15 @@ Apply these rules when using the repository execution skills that link here. runtime-checkout rules. - When a task depends on a local service or app on this machine that is not running, start it without asking and record what you started and why in the - PR or issue. Ask first if starting it affects another person, a remote or - production system, or paid resources, reusing approval that already covers - those effects. If startup fails, report the failure and any workaround. Do - not change login startup behavior, machine settings, or service configuration - to fix why it was not running; track that work in follow-up issues for - direction review. + task's PR or issue when posting is authorized, otherwise in the task report. + Ask first if startup affects another person, a remote or production system, + or paid resources, or if those effects cannot be determined; reuse approval + that already covers those effects. Use a start action that leaves login + startup behavior, machine settings, and service configuration unchanged. If + startup fails, report the failure and any workaround. Leave fixes for why it + was not running to follow-up issues under existing planning and posting + authority; when no issue write is authorized, include the proposed follow-up + in the task report. - Run checks required by the repository and affected behavior. Reuse passing evidence for the same revision and environment; broaden or repeat checks when changes, failures, or unresolved risk justify it. Report missing required