---
name: merge-and-commission-rescue-island
description: Continue Stephanos Rescue Island issue 3103 through existing protected review, merge, sync and commissioning gates; inspect readiness before dispatch and preserve canonical and Seed ownership.
---

# Merge and commission Rescue Island

Use for an operator request to merge, test or commission the existing Rescue
Island work in Cheekyfellastef/stephan-os. Keep the original PRs and worker/task
identities. This skill adds preparation guidance, not a new tool or authority.

## Before any protected merge dispatch

1. Read current main and each PR's exact title, head, tree and base. The stacked
   child must be requalified against main after its parent is protected-merged.
2. Inspect the complete technical review-thread inventory. Match each finding
   to the current source and focused regression. Resolve only verified fixes
   when the operator authorises that review-state change. Do this BEFORE dispatch.
   Resolution is not independent review approval.
3. Inspect the existing immutable independent-review artifact, run, attempt,
   archive and payload digest for that exact head/base. Recover successful
   artifacts when comment publication failed; do not rerun completed reviews.
   High-risk pilot code still needs qualified independent specialist coverage.
4. Read complete prior protected attempts for this source identity, including
   job evidence. An active run is not a reason to mint a fresh request. A
   same-base authority-stage failure remains held by canonical replay protection.
   Never delete a run, create an empty commit, change unrelated main content or
   swap transports to evade that fence. Legitimate reviewed main changes use
   the existing main-movement continuation with fresh ancestry, CI and review.
5. Use shared/agents/sovereignRescueMergeReadinessV1.mjs in the canonical repository
   as a read-only structural check when it is installed. Its inputs remain
   unauthenticated, and every execution-authority flag stays false. If absent,
   inspect the canonical predicates directly; do not invent an action ID.
6. Carry the operator's already-given merge request into one exact owner-authored
   canonical #2808 protected workflow packet. Keep a stable request ID through
   transport retries. Use the existing bounded environment-approval operation
   only for the exact pending run/PR/head/main admitted by its verifier.
7. Wait for the actual protected merge result and verify GitHub PR/main state.
   Dispatch, environment approval and a healthy process are intermediate proof.

## Sync, test and commission

Use the existing fast-forward-only source sync after an authorised merge.
Preserve dirty changes; never reset, clean or stash them to pass a check.
Run the focused preflight, pilot and Git-boundary tests at the resulting exact
source. Runtime process head and served UI build head are separate observations.

Commission rescue-island-01 only through an installed, independently reviewed
Island-owned authenticated intake and ownership adapter. Require an explicitly
operator-selected existing issue/title, allowed paths, unclaimed task/source,
fresh gaming/resource proof and bounded model custody. No fixture booleans,
readiness verdict, new skill or free canonical lane slot supplies that authority.
Never feed Island work through the original Goal Conveyor or Seed Canopy Forge,
touch an incumbent lease, or permit two writers on one logical source resource.

Retain SELECT -> CLAIM -> authentic physical PICKUP -> scoped DIFF -> TEST ->
isolated COMMIT -> independent PR review -> protected merge -> live proof as
separate receipts. Label test fixtures as fixtures. Clone 02 and unattended
refill remain separate qualification milestones. Report merged, installed,
building and unproven states separately; stop dependent execution on a real
protected rejection while completing independent authorised preparation.