Opus
Step 2 'Resolve parent repo' contradicts the Sandbox note's no-gh-api claim
- skills/fleet-state/SKILL.md:79-86
- skills/fleet-state/SKILL.md:251-253
The Sandbox note asserts the skill performs 'No `gh api` calls,' but Step 2 explicitly runs `gh api repos/...` (and `gh repo view`) to resolve the parent repo when PARENT_OVERRIDE is empty. This is a deceptive doc — an operator reading the security/sandbox section would believe the skill is hermetic local I/O when in fact it shells out to GitHub on every non-override run.
Recommendation
Either remove the `gh api` invocation in Step 2 (e.g., cache PARENT_REPO from an existing state file, or require the override), or update the Sandbox note to declare the single `gh api repos/<self>` call used purely to discover the parent repo's `full_name`.