create-egregore 0.19.32 → 0.20.0

package/runtime/prime/.codex/skills/me/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: me
+description: 'Fallback Codex adapter for the Egregore me workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore me Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+1. Read `.claude/skills/me/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/meeting/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: meeting
+description: 'Fallback Codex adapter for the Egregore meeting workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore meeting Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+## Structured UX parity
+
+This workflow has a Claude skill with user-visible structured output. After
+reading `.claude/skills/meeting/SKILL.md`, reproduce the same visible UX in Codex:
+
+- Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering,
+  exact confirmation blocks, and "no preamble" rules from the source skill.
+- Use the source skill's frame width, section order, labels, status footer,
+  and examples as the contract for the final response.
+- Never replace a required box/table/card/artifact view with a prose summary
+  unless the user explicitly asks for a summary.
+- When the source says to output a TUI box directly, paste that box as the
+  visible response, preferably in a `text` fenced block.
+- Never show raw JSON, raw command output, or unformatted script output when
+  the source skill requires formatted status or rendered output.
+
+1. Read `.claude/skills/meeting/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/note/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: note
+description: 'Fallback Codex adapter for the Egregore note workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore note Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+1. Read `.claude/skills/note/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/notion-connect/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: notion-connect
+description: 'Fallback Codex adapter for the Egregore notion-connect workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore notion-connect Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+1. Read `.claude/skills/notion-connect/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/onboarding/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: onboarding
+description: 'Fallback Codex adapter for the Egregore onboarding workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore onboarding Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+## Structured UX parity
+
+This workflow has a Claude skill with user-visible structured output. After
+reading `.claude/skills/onboarding/SKILL.md`, reproduce the same visible UX in Codex:
+
+- Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering,
+  exact confirmation blocks, and "no preamble" rules from the source skill.
+- Use the source skill's frame width, section order, labels, status footer,
+  and examples as the contract for the final response.
+- Never replace a required box/table/card/artifact view with a prose summary
+  unless the user explicitly asks for a summary.
+- When the source says to output a TUI box directly, paste that box as the
+  visible response, preferably in a `text` fenced block.
+- Never show raw JSON, raw command output, or unformatted script output when
+  the source skill requires formatted status or rendered output.
+
+1. Read `.claude/skills/onboarding/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/pr/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: pr
+description: 'Fallback Codex adapter for the Egregore pr workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore pr Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+1. Read `.claude/skills/pr/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/pull/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: pull
+description: 'Fallback Codex adapter for the Egregore pull workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore pull Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+1. Read `.claude/skills/pull/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/push/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: push
+description: 'Fallback Codex adapter for the Egregore push workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore push Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+1. Read `.claude/skills/push/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/quest/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: quest
+description: Manage Egregore quests from Codex when the user invokes /quest or $quest, or asks to manage quests, using memory-first files and optional connected-mode graph updates.
+---
+
+# Egregore Quest
+
+Native Codex Egregore skill. Quests are shared, open-ended explorations stored
+under `memory/quests/`.
+
+## Flow
+
+1. Run `bin/agent.sh sync`.
+2. Detect mode from `egregore.json` `mode`, defaulting to `connected`.
+3. Dispatch from the user request:
+   - no argument: list active and paused quests from `memory/quests/*.md`.
+   - name or slug: show quest details from the markdown file.
+   - `new`: create a quest.
+   - `contribute`: append a contribution entry.
+   - `prioritize`: set `priority` to `0`, `1`, `2`, or `3`.
+   - `pause`: set `status: paused`.
+   - `complete`: set `status: completed` and record an outcome.
+4. Filesystem writes are canonical. Quest files use frontmatter:
+
+```yaml
+---
+title: Example Quest
+slug: example-quest
+status: active
+projects: []
+started: YYYY-MM-DD
+started_by: handle
+priority: 0
+completed:
+---
+```
+
+5. Update `memory/quests/index.md` after create, status changes, and priority
+   changes.
+6. Commit and push memory immediately:
+
+```bash
+git -C memory add quests
+git -C memory commit -m "quest: $SLUG $ACTION" --quiet
+git -C memory push origin main --quiet
+```
+
+7. In connected mode only, mirror changes best-effort with `bin/graph.sh`.
+   For each named person, follow `.claude/context/notification-consent.md`:
+   create a direct-message plan, then show a separate exact Send / Edit /
+   Cancel checkpoint. Selecting quest participants is not notification
+   consent, and approvals cannot be batched across recipients. If planning or
+   dispatch fails, report that the quest was saved to memory and continue.
+
+## Interaction
+
+Use structured Codex question tooling when available for new quest fields and
+status confirmations. Otherwise ask one short numbered question at a time with
+an `Other:` option.
+
+## Output
+
+Structured UX parity is required:
+
+- `/quest` list mode renders the active quest table:
+  `| Quest | Project | Artifacts | Contributors |`, followed by paused quest
+  state and entry-point hints.
+- `/quest <name>` detail mode renders the same sectioned view as Egregore:
+  title rule, status, projects, started metadata, question, threads,
+  artifacts, todos when available, contributors, and entry points.
+- Create/update routes use compact structured confirmations with the quest
+  file path and memory push state. Do not substitute a loose prose summary.
+- In local mode, omit graph/notification wording while preserving the same
+  list/detail layout.
+
+## Rules
+
+- Do not use graph or notification calls in local mode.
+- Do not let graph failure block a filesystem quest update.
+- Do not use Claude Code commands.

package/runtime/prime/.codex/skills/reflect/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: reflect
+description: 'Fallback Codex adapter for the Egregore reflect workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore reflect Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+## Structured UX parity
+
+This workflow has a Claude skill with user-visible structured output. After
+reading `.claude/skills/reflect/SKILL.md`, reproduce the same visible UX in Codex:
+
+- Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering,
+  exact confirmation blocks, and "no preamble" rules from the source skill.
+- Use the source skill's frame width, section order, labels, status footer,
+  and examples as the contract for the final response.
+- Never replace a required box/table/card/artifact view with a prose summary
+  unless the user explicitly asks for a summary.
+- When the source says to output a TUI box directly, paste that box as the
+  visible response, preferably in a `text` fenced block.
+- Never show raw JSON, raw command output, or unformatted script output when
+  the source skill requires formatted status or rendered output.
+
+1. Read `.claude/skills/reflect/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/review-pr/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: review-pr
+description: 'Fallback Codex adapter for the Egregore review-pr workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore review-pr Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+## Structured UX parity
+
+This workflow has a Claude skill with user-visible structured output. After
+reading `.claude/skills/review-pr/SKILL.md`, reproduce the same visible UX in Codex:
+
+- Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering,
+  exact confirmation blocks, and "no preamble" rules from the source skill.
+- Use the source skill's frame width, section order, labels, status footer,
+  and examples as the contract for the final response.
+- Never replace a required box/table/card/artifact view with a prose summary
+  unless the user explicitly asks for a summary.
+- When the source says to output a TUI box directly, paste that box as the
+  visible response, preferably in a `text` fenced block.
+- Never show raw JSON, raw command output, or unformatted script output when
+  the source skill requires formatted status or rendered output.
+
+1. Read `.claude/skills/review-pr/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/save/SKILL.md

@@ -0,0 +1,125 @@
+---
+name: save
+description: Save Egregore work when the user invokes /save or $save, or asks to commit, push, sync, or save current changes from a Codex Egregore session.
+---
+
+# Egregore Save
+
+Native Codex Egregore skill. This is the user-facing abstraction for the git
+and memory workflow: users should be able to say "save this" without knowing
+which branch, commit, push, pull request, or memory sync steps are required.
+
+## Flow
+
+1. Confirm this is an Egregore checkout by checking for `bin/agent.sh`.
+2. Inspect state silently:
+
+```bash
+BASE=$(bash -c 'SCRIPT_DIR="$PWD"; CONFIG="$PWD/egregore.json"; . "$PWD/bin/lib/config.sh" && _get_base_branch') ||
+  { echo "Could not resolve the configured base branch; stopping before Git changes." >&2; exit 1; }
+git status --short
+git status --short memory 2>/dev/null || true
+BRANCH=$(git branch --show-current)
+AHEAD=0
+OPEN_PR=""
+case "$BRANCH" in
+  dev/*|feature/*|bugfix/*)
+    git fetch origin "$BASE" --quiet 2>/dev/null || true
+    AHEAD=$(git rev-list --count "origin/$BASE..HEAD" 2>/dev/null || echo 0)
+    if command -v gh >/dev/null 2>&1; then
+      OPEN_PR=$(gh pr list --head "$BRANCH" --base "$BASE" --state open \
+        --json url --jq '.[0].url // empty' 2>/dev/null || true)
+    fi
+    ;;
+esac
+```
+
+3. A clean working tree alone does **not** mean the work is fully saved:
+   - If there are repo or memory changes, continue.
+   - If the task branch is ahead of `origin/$BASE` and `OPEN_PR` is empty,
+     continue even when the tree is clean. The bridge must push any committed
+     work and create the missing PR.
+   - Stop with "everything is already saved" only when there are no repo or
+     memory changes and either the branch has no commits to integrate
+     (`AHEAD=0`) or an open integration PR already exists.
+4. Run the product distribution checkpoint before any commit or push when
+   `capability-distribution.json` exists:
+
+```bash
+node bin/capability-distribution.mjs validate --root .
+node bin/capability-distribution.mjs changes --root . --base "origin/$BASE" --json
+```
+
+   Inspect the diff as well as the receipt. Ask when this work introduces a new
+   or unclassified Egregore component, or changes a component's placement
+   without an explicit user decision in the current conversation. Components
+   include skills, packages, APIs, sites, workers, infrastructure, schemas,
+   assets, and runtime tools. Ordinary edits to an already classified component
+   do not prompt.
+
+   Show the tracker before asking:
+
+   `artifacts/capability-pipeline.html`
+
+   Ask once using structured Codex question tooling when available. Otherwise
+   render the compact numbered question and wait:
+
+```text
+Where should {name} live?
+1. OSS + Connect — part of the open runtime; Connect inherits it
+2. Connect only — delivered only to authenticated Connect users
+3. Curve Labs / Egregore — used only in this development instance
+```
+
+   Record every new component as `queued` under the selected placement and
+   attach all of its governed source paths. Availability is changed separately
+   after review. Group components into one checkpoint only when they share the
+   same placement. Apply the answer to `capability-distribution.json`, regenerate
+   `skill-distribution.json` and both artifacts, then validate again. Rebuild
+   runtime packs when an available runtime component changes placement. If the
+   user already made this exact decision during the current work, do not ask
+   twice.
+5. Synthesize:
+   - a short topic from the work,
+   - a clear commit message,
+   - a one-line user-facing scope summary,
+   - a PR description following `.claude/context/pr-format.md`:
+     `## What` (1–4 bullets), `## Why` (1–3 sentences), and
+     `## Verification` (how the change was checked — required when the
+     diff touches non-markdown files; be honest if unverified).
+6. If the scope is ambiguous or includes unrelated changes, ask for one compact
+   confirmation. Use structured Codex question tooling when available;
+   otherwise render:
+
+```text
+Save these changes?
+1. Save all
+2. Narrow scope
+Other:
+```
+
+7. Run the bridge command:
+
+```bash
+bin/agent.sh save --message "$MESSAGE" --topic "$TOPIC" --pr-body "$PR_BODY"
+```
+
+The bridge owns the mechanical workflow: sync memory, ensure a task branch,
+commit repo changes, push, and create or reuse a pull request when available.
+Always pass the synthesized `--pr-body` — the bridge only auto-generates a
+skeleton body as a last resort, and the CI `pr-format` check gates every PR.
+
+8. Parse the output and report only useful user information:
+   - branch name,
+   - whether a commit was created,
+   - whether push succeeded,
+   - pull request URL if present,
+   - memory sync status.
+
+## Rules
+
+- Do not ask the user to run git commands.
+- Do not expose implementation detail unless save fails.
+- If save fails, say which step failed and leave the branch/path clear.
+- Never run destructive git commands.
+- Do not use Claude Code commands.

package/runtime/prime/.codex/skills/slack-connect/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: slack-connect
+description: 'Fallback Codex adapter for the Egregore slack-connect workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore slack-connect Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+1. Read `.claude/skills/slack-connect/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.

package/runtime/prime/.codex/skills/summon/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: summon
+description: 'Fallback Codex adapter for the Egregore summon workflow.'
+---
+
+<!-- generated-by: bin/codex-sync-skills.sh -->
+
+# Egregore summon Adapter
+
+This is fallback coverage for a long-tail Egregore workflow that has not been
+ported to a hand-written Codex-native skill yet.
+
+Use the project shell and filesystem directly. Do not invoke Claude Code
+commands. Translate interactive choices to structured Codex question tooling
+when it is available; otherwise render compact numbered choices with an
+`Other:` option and wait for the user.
+
+## Structured UX parity
+
+This workflow has a Claude skill with user-visible structured output. After
+reading `.claude/skills/summon/SKILL.md`, reproduce the same visible UX in Codex:
+
+- Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering,
+  exact confirmation blocks, and "no preamble" rules from the source skill.
+- Use the source skill's frame width, section order, labels, status footer,
+  and examples as the contract for the final response.
+- Never replace a required box/table/card/artifact view with a prose summary
+  unless the user explicitly asks for a summary.
+- When the source says to output a TUI box directly, paste that box as the
+  visible response, preferably in a `text` fenced block.
+- Never show raw JSON, raw command output, or unformatted script output when
+  the source skill requires formatted status or rendered output.
+
+1. Read `.claude/skills/summon/SKILL.md` for the workflow details.
+2. Run the referenced `bin/` scripts directly from Codex.
+3. Treat graph and publish steps as best-effort unless that workflow explicitly
+   says they are required.
+4. For every external notification, follow
+   `.claude/context/notification-consent.md`: plan without sending, then show
+   a separate exact Send / Edit / Cancel checkpoint. Never infer notification
+   consent from the workflow request or a batch approval.
+5. Keep local-mode behavior filesystem-first and avoid graph or notification
+   calls when `egregore.json` declares `"mode": "local"`.
+6. Never call the deprecated `egregore-handoff` CLI for Egregore project
+   handoffs.