Fix delivery resolution and operation skill discovery

.agents/skills/boatstack-autoplan/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-autoplan
+description: Create and approve a verified delivery plan. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Autoplan
+
+Select the `approved-plan` terminal. This trigger supplies planning intent only. It never approves unseen plan bytes.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.agents/skills/boatstack-autoplan/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Boatstack Autoplan"
+  short_description: "Create and approve a verified delivery plan."
+  default_prompt: "Use $boatstack-autoplan to follow the authority-preserving Boatstack V2 driver."
+policy:
+  allow_implicit_invocation: false

.agents/skills/boatstack-run/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-run
+description: Drive delivery to an open or updated pull request. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Run
+
+Select the `open-or-updated-pr` terminal. This trigger never grants merge authority. Provider authority remains a separate verified receipt.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.agents/skills/boatstack-run/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Boatstack Run"
+  short_description: "Drive delivery to an open or updated pull request."
+  default_prompt: "Use $boatstack-run to follow the authority-preserving Boatstack V2 driver."
+policy:
+  allow_implicit_invocation: false

.agents/skills/boatstack-update/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-update
+description: Apply a checksum-verified Boatstack update. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Update
+
+Select the `installation.update` transition. This trigger does not reclassify or advance a product delivery.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.agents/skills/boatstack-update/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Boatstack Update"
+  short_description: "Apply a checksum-verified Boatstack update."
+  default_prompt: "Use $boatstack-update to follow the authority-preserving Boatstack V2 driver."
+policy:
+  allow_implicit_invocation: false

.claude/skills/boatstack-autoplan/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-autoplan
+description: Create and approve a verified delivery plan. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Autoplan
+
+Select the `approved-plan` terminal. This trigger supplies planning intent only. It never approves unseen plan bytes.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.claude/skills/boatstack-run/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-run
+description: Drive delivery to an open or updated pull request. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Run
+
+Select the `open-or-updated-pr` terminal. This trigger never grants merge authority. Provider authority remains a separate verified receipt.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.claude/skills/boatstack-update/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-update
+description: Apply a checksum-verified Boatstack update. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Update
+
+Select the `installation.update` transition. This trigger does not reclassify or advance a product delivery.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.cursor/commands/boatstack-autoplan.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-autoplan
+description: Create and approve a verified delivery plan. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Autoplan
+
+Select the `approved-plan` terminal. This trigger supplies planning intent only. It never approves unseen plan bytes.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.cursor/commands/boatstack-run.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-run
+description: Drive delivery to an open or updated pull request. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Run
+
+Select the `open-or-updated-pr` terminal. This trigger never grants merge authority. Provider authority remains a separate verified receipt.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.cursor/commands/boatstack-update.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-update
+description: Apply a checksum-verified Boatstack update. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Update
+
+Select the `installation.update` transition. This trigger does not reclassify or advance a product delivery.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.gemini/skills/boatstack-autoplan/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-autoplan
+description: Create and approve a verified delivery plan. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Autoplan
+
+Select the `approved-plan` terminal. This trigger supplies planning intent only. It never approves unseen plan bytes.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.gemini/skills/boatstack-run/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-run
+description: Drive delivery to an open or updated pull request. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Run
+
+Select the `open-or-updated-pr` terminal. This trigger never grants merge authority. Provider authority remains a separate verified receipt.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.

.gemini/skills/boatstack-update/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: boatstack-update
+description: Apply a checksum-verified Boatstack update. Use only when the user explicitly selects this Boatstack operation.
+---
+
+# Boatstack Update
+
+Select the `installation.update` transition. This trigger does not reclassify or advance a product delivery.
+
+Run `boatstack status --repo . --format json` once for observation. An authority-free
+`FRONTIER` from status is diagnostic only and cannot terminate this selected operation.
+
+Bind one command-scoped context containing the exact goal, delivery, repository,
+worktree, flow, actor, and supplied authority receipts. Preserve that context
+through every `next`, `apply`, `recover`, and re-resolution. Never synthesize missing
+authority or infer it from authentication, files, branches, or prior conversation.
+
+Begin each cycle with an untargeted authority-bearing `next`. Apply only the
+stable transition ID from the immediately preceding prescription and only its
+declared parameters. Preserve the complete apply response and stderr, including
+admission, receipt, postcondition, error, recovery, and transaction fields.
+Re-resolve with the same context after every complete receipt.
+
+Stop only on an authority-bearing `FRONTIER`, `BLOCKED`, `REFUSED`, or
+`UNRESOLVED` result for this operation. Treat `TERMINAL` as exact goal evidence.
+If recovery is active, use only a transition in `recovery_info.permitted` and
+the exact transaction ID. Never choose maintenance, correction, abandonment,
+merge, provider, or destructive authority as an escape from a frontier.