--- name: fcis-go-runtime-migration description: Implement, verify and cut over the fresh standalone Fountain Coach FCIS Go service against peer canonical FCIS-STACK.md and FCIS-OPENAPI.json in Fountain-Coach/.github. Use for Go FCIS OAuth/WebAuthn/MCP/Host HTTP parity, dedicated native Go FountainStore bootstrap, fleet enrollment and grants, Go tests, release and acceptance. No legacy Swift issuer or historical grant migration prerequisite; preserve provider-neutral MIDI2/FCIS-KIT authority and finite owner-controlled DoD. --- # FCIS Go Runtime Migration **Owner-selected standalone target (18 November 2026):** The **peer canonical** `Fountain-Coach/.github/FCIS-STACK.md` and `Fountain-Coach/.github/FCIS-OPENAPI.json` jointly specify the native Go FCIS stack and HTTP wire surface. The root OpenAPI is the sole writable HTTP contract; the old `midi2-gpu-fabric/apps/estate-publisher/contracts/fcis-owner.openapi.json` is a predecessor, not an alternative authority. Native Go OAuth, WebAuthn passkeys, MCP, Host admission and a **fresh dedicated Go-native FountainStore** are the goal. Do **not** require an old Swift OAuth issuer, a migrated Swift snapshot, historical refresh families, a second persistence engine, PostgreSQL, SQLite, or unverified distributed replication. Preserve the issuer URL. Do not turn priority-two Stripe payment into a cutover gate. **Contract-walk:** For each currently specified canonical OpenAPI HTTP operation, record `specified-only`, `Go-implemented`, `source-tested`, `released`, and `live-accepted` separately. Implement/validate exact Go method, path, authorization, input/output/refusal schema and owner/Host/Store evidence against the **pinned root OpenAPI revision**. For MCP, compare actual tools/list and tools/call with admitted typed Host registry and per-client grant; the OpenAPI contains no independent MIDI2 instrument/grant authority. When the root spec contains a target path with no Go handler, report that exact operation `NOT_ESTABLISHED` without inventing a separate service, and implement it only as a bounded slice of the accepted cutover. No hardcoded `host.describe` ceiling is justified by a predecessor tool list. Use the existing `fountain-coach-instrument-creation` lifecycle for instrument implementation. This skill coordinates a bounded migration slice and selects an *admitted* deterministic Go build instrument; it grants no execution, deployment or Store authority. ## Mandatory finite execution contract — stop the loop Apply on **every** invocation, including a bare "proceed." The owner's requested outcome, not discovered dependencies, is the scope. This is a hard execution gate, not optional advice. 1. **One slice, one Definition of Done.** Before a source edit, build or Host action, state one concrete user-visible result, its owning repository, an exact acceptance witness, and a stopping condition. Read the current owning `PLANS.md` phase and reuse it; do not open another initiative. If the request contains several independent deliverables, complete the highest-priority admissible slice and list the rest as separate follow-ups rather than silently starting them. 2. **Authority before compilation.** Make one bounded preflight of actual installed instrument/registry, signed grant, owner/provider access and target Host. For a *live* operation with no required grant, signer, admitted command or authenticated provider control, **stop operational work before implementing adjacent infrastructure**. Report `BLOCKED` only for an observed authoritative refusal of an attempted operation, `UNAVAILABLE` for a positively absent admitted operation, and `NOT_ESTABLISHED` for unreadable or unattempted evidence. A prior source build cannot promote either state. 3. **15-minute hard limit.** From the first action in the current user turn, spend no more than **15 minutes** on this slice unless the owner explicitly reauthorizes a longer scope. Permit **one implementation attempt and one focused retry** of the same failing predicate. Permit **at most one full native/SwiftPM rebuild**, and only on an approved Ubuntu/external build host; a dependency-authentication failure or timeout is a stopping condition, not an invitation to rebuild repeatedly. Never compile on the MacBook Pro's internal storage. 4. **Freeze dependency scope.** An instrument build does not implicitly authorize designing a grant issuer, adding a second Host adapter, writing Store infrastructure, redeploying Caddy or synchronizing a ChatGPT plugin. Record any such missing requirement as the **first unmet gate** and stop the current slice. Do not invent a new prerequisite without a reproduced failure and binding existing rule. Do not create an additional skill/instrument to escape a refused capability. 5. **Stop on the first terminal condition:** independent acceptance, missing owner-signed grant or authenticated provider action, same predicate failing after one correction, the one-build ceiling, or the time budget. On time-budget expiry, leave the source/service in a safe stated condition; do not wait indefinitely for tests or claim a pending command succeeded. A subsequent "proceed" continues only the explicitly recorded next action, never all discovered backlog items. 6. **Give a finite handoff.** Report (a) original requested result, (b) actually completed and independently evidenced state with revision/receipt, (c) one precise first unmet acceptance predicate, and (d) one next authorized action or explicitly missing owner/provider action. Distinguish SOURCE-TESTED from LIVE-ADMITTED and HOSTED-SYNCED. Do not promise background work, request repeated "proceed" confirmations, or describe partial source work as operational success. ## First resolve, then act 1. Read the current `Fountain-Coach/.github` goal-fidelity standard, the owning runtime repository's `AGENTS.md` and active `PLANS.md` phase, and the bounded `governance-read` result (07, 08, 91, 93 and 160 as applicable). Inspect live versions, grants, release paths and the existing Swift seam before planning a replacement. Keep the user-approved goal fixed: **standalone Go FCIS serving both OAuth and MCP at `fcis.fountain.coach`, using a fresh dedicated native Go FountainStore**. Do not reinterpret the request as Swift state migration, distributed Store work or Go-only Reframe. 2. Name one canonical Go HTTP operation or the native Store bootstrap, its intended Go entrypoint, callers, Store effects, signed identity, grant checks, MIDI2 contract and acceptance authority. Legacy Swift routes are historical comparison where relevant, not a required runtime ancestor. Do not start a wholesale rewrite or rewrite already proven native Apple capability adapters. 3. Implement the **root-canonical OpenAPI** in a Go-owned module with pinned source revision, exact method/path/schema/security and Go-native owner/FountainStore authority. A new **dedicated FCIS FountainStore root** is explicitly authorized and is not a second competing authority; no new HTTP or MIDI2 vocabulary outside its owning contract, arbitrary Host shell power, or automatically admitted machine grant. Owner and clients may reauthorize/re-enroll as part of the chosen clean cutover. 4. For build/test, resolve the **live** FCIS instrument registry for `fountaincoach.go-build@0.1.0`, operation `workstation.go.verify`, through existing `reframe/capability.invoke` / `reframe/capability.event`. Select only an admitted workflow (`fcis.unit` or `fcis.verify`) and supply typed `action`, `workflow`, 40-character source revision, correlation and idempotency IDs. Never supply shell commands, paths, toolchain overrides, mount locations or credentials as model input. 5. If the Go Build instrument is unadmitted, stop **operational dispatch** with `UNAVAILABLE — Go Build Instrument not admitted` only when the registry confirms that absence. Otherwise mark the unobserved gate `NOT_ESTABLISHED`. Do **not** treat a bare "proceed" as authorization to open another build/security/issuer project. Implementing the candidate is a **separately named slice** under `fountain-coach-instrument-creation`, with isolated tests and its own DoD; never disguise local Go commands as admitted FCIS execution or fall back to Swift/Xcode/macOS build pollution. 6. The native Host must attest the executable, trusted source revision, owner grant, approved isolated build filesystem, bounded timeout, exclusive lease, original source status and read-only Store binding before execution. The instrument executes only fixed Go commands. Source tests, compiler success, Host receipts and runtime acceptance are distinct evidence classes. 7. Release/update uses the **currently demonstrated, owner-authorized production release mechanism**, whether a released Host-lifecycle instrument or the existing authenticated SSH/systemd/Caddy operator path expressly authorized by the owner. Preserve immutable release provenance, predecessor/rollback, exact public route and live acceptance. Never claim a source PR or Go build receipt is production cutover. Do not invent the admission of `fountaincoach.host-lifecycle@0.1.0`, and do not treat one connection's missing tool enumeration as proof SSH is unavailable. 8. After each migrated component, verify API/IDL parity, negative grants/replay/refusal, persistence, start/restart, renewal across the 24-hour grant boundary and independent owner-selected Host readback where relevant. Name the actual source revision, executable digest, test result, Store receipt and unmet gates. Stop after the bounded accepted result; do not reopen the prior Swift cleanup loop. ## Boundaries and current state The Go Build Instrument v0.1.0 is a **tested candidate**, not yet registered or callable from the production FCIS Host. Its Go library currently performs bounded local builds and emits a non-Store receipt when supplied with a host-validated authority object. That object is not a signature and must never be treated as standalone admission. See `Fountain-Coach/midi2-gpu-fabric/docs/fcis-go-build-instrument-v0.1.0.md` and `apps/estate-publisher/Scenarios/fcis-go-build-instrument-20261117.yaml`. The existing runtime repository's maintenance Kit currently declares Swift-only operation ownership. This is an **explicit migration boundary**: do not quietly change its existing behavior or claim a Go worker was admitted under that rule. The owner-approved Go-first direction authorizes developing a candidate and recording the contract change; a separate governed admission/release must reconcile the Kit/Host binding. Read [ownership-and-acceptance.md](references/ownership-and-acceptance.md) for component selection and finite proof. Do not create ZIP archives: canonical FCIS Skills are Git-owned in `Fountain-Coach/.github` and projected through the existing reviewed plugin.