genesis-compiler 1.2.23 → 1.2.25

package/README.md

@@ -108,10 +108,10 @@ empty or already-adopted project.
 
 `genesis init` creates an empty Blueprint, a focused engineering approach, an
 empty optional Stack, the current `genesis/version`, three project Agent Skills,
-and project-local Codex hooks. The skills are ordinary
+and one project-local Codex guidance hook. The skills are ordinary
 [Agent Skills](https://agentskills.io): `genesis-project`, `genesis-program`,
 and `genesis-deslop`, each with standard `SKILL.md` and `agents/openai.yaml`
-metadata. Open `/hooks` once in Codex to review and trust the hooks. After
+metadata. Open `/hooks` once in Codex to review and trust the guidance hook. After
 that, use Codex normally. No technology is assumed until you explicitly select
 Stack components:
 
@@ -127,12 +127,12 @@ complete directory into `.agents/skills/`, including its `references/`,
 `scripts/`, `assets/`, and agent metadata. Every relative Markdown link and image
 must resolve within that same Skill directory after relocation; a missing
 target or path that escapes the Skill root makes the Skill invalid. The agent
-loads valid resources only when the Skill requires them. For example, the
-`genesis-stack` catalog's JSKIT piece installs the JSKIT package's own `jskit`
-skill. A piece's optional
-`## Guidance` is concise
-supplemental project-work guidance; it does not create or replace a generic
-technology skill.
+loads valid resources only when the Skill requires them. A technology does not
+need a Skill to be selectable: the curated JSKIT piece, like ordinary framework
+pieces, links its authoritative framework documentation through Stack prose and
+declares no Skill. A piece's optional `## Guidance` is concise supplemental
+project-work guidance; it does not create or replace a generic technology
+skill.
 
 `.agents/skills/.genesis-managed.json` records only copies Genesis owns.
 Genesis never overwrites an unmanaged skill and preserves locally modified
@@ -182,7 +182,7 @@ People may edit `## Project requirements` to name obligations the presets do
 not capture, including a specific organizational, compliance, cryptographic,
 or scale constraint. `genesis engineering set` changes only the profile and
 preserves those requirements. Generated prompts, path-focused context, Codex
-session guidance, Post-change work, and Deslop all receive the effective
+session guidance, implementation Post-change work, and Deslop all receive the effective
 approach. A project upgraded from an older Genesis release safely uses
 `focused.v1` until `genesis init` or `genesis engineering set focused.v1`
 records the file.
@@ -263,27 +263,19 @@ Python, Java, C#, C/C++, PHP, Go, Rust, Ruby, Kotlin, and Shell. A future techno
 adds its adapter through its Stack piece rather than teaching Genesis prompts
 to parse that language.
 
-Before changing project files for a user-requested implementation, Codex runs
-`genesis hook authorize`. At the end of an authorized turn that changed
-Git-visible project files, the Stop hook asks Codex for bounded follow-up turns.
-Unmarked turns finish normally even if another process changes the same
-checkout. When the selected Stack contributes `Post-change` work, all
-contributions compose deterministically into one optional code-changing turn.
-Genesis then reconciles the Blueprint and affected Program explanations from
-the complete changed-path set and actual Git diff, and refreshes both City
-projections. A focused, behavior-preserving Deslop pass runs before both Cities
-are refreshed again; its response is the concise user-facing completion. A
-project with no selected Stack uses only the `genesis-deslop` skill. Selected
-Stack components enrich Post-change work, reconciliation, and cleanup with
-general Guidance, and enrich cleanup further with technology-specific Deslop
-guidance.
-
-The hook never starts another Codex process. Its small per-session phase is
-limited to `implementation -> optional post-change -> reconcile -> deslop ->
-done`, so it cannot keep continuing recursively. The Stop after Deslop clears
-the sequence rather than scheduling another model turn. Empty Post-change
-content is skipped rather than producing an empty turn. Question, explanation,
-review, diagnosis-only, and unchanged turns finish normally.
+The project Codex hook injects a short operating guide at startup, resume,
+clear, and compaction. It records no turn state, blocks no Stop, and requests no
+follow-up turn. Implementation prompts compose selected Stack `Post-change`
+guidance into the original implementation turn, and the project skill keeps
+intentional Blueprint and affected Program changes aligned there.
+
+Deslop runs only when explicitly requested. With no stated scope it reviews the
+latest commit; “the last N commits” reviews the net surviving first-parent
+range, and a named commit or range is honored exactly. It requires a clean
+worktree and leaves ordinary uncommitted cleanup for review rather than
+amending history. Genesis supplies the behavior-preserving boundary and Git
+scope rules. Selected Stack components add technology-specific Deslop guidance
+without weakening or broadening that contract.
 
 Projects can customize a selected technology through its matching file, such
 as `genesis/stack/jskit.md`:
@@ -303,7 +295,7 @@ Additional project-specific context about how JSKIT is used here.
 
 ### Post-change
 
-- Additional project-specific work to perform once after implementation.
+- Additional project-specific work to perform before the implementation turn completes.
 
 ### Deslop
 
@@ -321,7 +313,7 @@ A replacement for the installed JSKIT description.
 
 ### Post-change
 
-- Replacement installed post-change work.
+- Replacement installed post-change work for the implementation turn.
 
 ### Deslop
 
@@ -357,8 +349,9 @@ genesis prompt                                      # implementation work
 genesis prompt --task start                        # open a new or existing project conversation
 genesis prompt --task adopt                        # import an existing project's complete contract
 genesis prompt "Add filtering by note title"
-genesis prompt --task deslop                        # explicit cleanup
-genesis prompt --task deslop "Only review billing"
+genesis prompt --task deslop                        # clean up the latest commit
+genesis prompt --task deslop "Deslop the last 5 commits"
+genesis prompt --task deslop "Deslop commit a1b2c3d"
 genesis prompt --task program                       # refresh explanation
 genesis prompt --task blueprint "Start on notes"   # update product intent
 genesis prompt --task describe                      # create/refresh Blueprint and complete Program
@@ -377,8 +370,9 @@ The eight task types are deliberately explicit:
 - `work` implements the Blueprint and optional request using current code,
   Program, the selected engineering approach, selected Stack context, and
   progressively loaded Agent Skills.
-- `deslop` requests cleanup explicitly. Codex projects also receive a bounded
-  automatic Deslop turn after their separate explanatory reconciliation turn.
+- `deslop` requests behavior-preserving cleanup of committed work explicitly.
+  It defaults to the latest commit, accepts a first-parent commit count or exact
+  commit/range, requires a clean worktree, and leaves its result uncommitted.
 - `program` edits only `genesis/program/` to explain the code that exists, with
   selected Stack guidance available for technology-specific correctness.
 - `blueprint` edits only `genesis/blueprint.md` from explicit user intent. It
@@ -418,19 +412,20 @@ Components may contribute:
 
 - a concise description and supplemental Guidance used across relevant tasks;
 - existing-project Adoption requirements used only while importing a codebase;
-- optional Post-change work composed once after a code-changing implementation;
+- optional Post-change work composed into the original implementation turn;
 - one authoritative Agent Skill directory when the component owns one;
 - generic external-resource requirements;
-- cleanup advice used by explicit and automatic Deslop prompts;
+- cleanup advice composed on top of the core explicit Deslop contract;
 - structural code indexers used by Machine City and function lookup;
 - default verification commands.
 
 Technology-specific supplemental rules intentionally remain in Stack pieces.
 General `Guidance` enriches implementation, review, Program, description, and
-cleanup tasks; `Adoption` adds import-only requirements; `Post-change` composes
-one optional code-changing continuation before explanation; `Deslop` adds
-cleanup-only rules. None shadows an official generic technology skill or
-assumes that an upstream skill contains every rule Genesis needs.
+cleanup tasks; `Adoption` adds import-only requirements; `Post-change` adds
+work to finish in the original implementation turn; `Deslop` adds
+technology-specific cleanup rules to Genesis's invariant behavior-preserving
+contract. None shadows an official generic technology skill or assumes that an
+upstream skill contains every rule Genesis needs.
 
 Genesis core contains no Stack pieces and no database, framework, language, or
 platform dependency. See [Stack components](docs/stack-components.md).

package/docs/assurance-model.md

@@ -34,8 +34,7 @@ project. It creates ordinary project files with mode `0666`, directories and
 executable skill files with mode `0777`, and lets the invoking process umask
 and the destination directory's inherited ACL establish the effective mode and
 group. Atomic replacements are created beside their destination so they inherit
-the same filesystem policy before becoming visible. Private hook continuation
-state remains explicitly `0600`.
+the same filesystem policy before becoming visible.
 
 This keeps ordinary single-user projects conventional while allowing a managed
 host to require shared-group writes and no access for other users. The host is

package/docs/prompt-integration.md

@@ -46,10 +46,11 @@ Genesis keeps each instruction at one useful level:
   selected profile in every implementation and cleanup path.
 - The generated JSON block contains current structural facts and warnings.
 
-Detailed technology manuals belong in the technology skill's `references/`
-directory. Concise rules Genesis needs beyond that skill belong in Stack
-`Guidance`; they are composed into relevant prompts without creating a
-colliding generic skill.
+Detailed technology manuals belong to the technology's authoritative
+documentation, which Stack prose may link directly. A technology may also
+offer a separately installable Skill with its own `references/` directory.
+Concise rules needed in project prompts belong in Stack `Guidance`; they are
+composed without creating a colliding generic skill.
 
 ## Existing projects
 
@@ -76,22 +77,19 @@ does not perform adoption automatically. If the user accepts, Codex runs the
 command itself and follows its returned prompt in the same conversation. Other
 hosts can call `adoptProject()` and send its `prompt` directly.
 
-Codex can instead use the project-local hooks installed by `genesis init`.
-Those hooks inject a short operating guide and record the Git-visible state when
-each user prompt begins. Before editing for an explicit user implementation
-request, Codex marks that turn with `genesis hook authorize`. Only an authorized
-turn whose project files changed can request bounded continuations; unmarked
-turns finish normally even if another process changes the checkout. Selected
-`Post-change` contributions compose into one optional code-changing turn;
-Genesis then reconciles Blueprint and affected Program explanations from the
-complete Git-visible change set and Deslops the implementation. The Deslop
-response is the concise user-facing completion. The hooks invoke the same
-Genesis project operations and never start another agent process. A per-session
-phase permits only `implementation -> optional post-change -> reconcile ->
-deslop -> done`. Empty Post-change content skips that phase. Genesis refreshes
-both City projections after reconciliation so Deslop sees the current
-explanation and function inventory, then refreshes them again after Deslop in
-case cleanup changed the implementation map.
+Codex can instead use the project-local hook installed by `genesis init`.
+That hook injects a short operating guide at startup, resume, clear, and
+compaction. It does not record user turns, authorize edits, intercept Stop, or
+request another model turn. Selected `Post-change` contributions are included
+in the original implementation prompt, whose project skill also keeps
+intentional Blueprint and affected Program changes aligned.
+
+Deslop is an explicit prompt task available to any host or command-line user.
+It resolves the latest commit by default, a requested first-parent count, or an
+exact commit/range; requires a clean worktree; and leaves cleanup as ordinary
+uncommitted work. Genesis owns that invariant contract. Selected Stack
+`Deslop` prose and applicable technology skills enrich the cleanup without
+changing its scope or behavior-preserving boundary.
 
 Once Codex identifies relevant source, `genesis context <path...>` returns only
 Program modules citing those paths plus the effective engineering approach and
@@ -112,7 +110,6 @@ user-installed generic technology skills independent.
 Matching files under `genesis/stack/<component>.md` may add to or override that
 selected component's Description, Guidance, Adoption, Post-change, and Deslop
 fields. Effective Guidance is used by work, review, Program, describe, Deslop,
-and path-context generation. The Codex continuation flow also carries it into
-Post-change work, reconciliation, and cleanup; effective Post-change work runs
-once before reconciliation, while Deslop guidance remains cleanup-only. Effective Adoption
-guidance is included only in the adoption workflow.
+and path-context generation. Effective Post-change work is composed into the
+implementation prompt, while Deslop guidance remains cleanup-only. Effective
+Adoption guidance is included only in the adoption workflow.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-compiler",
-  "version": "1.2.23",
+  "version": "1.2.25",
   "type": "module",
   "description": "An agent-independent prompt, multi-language code-index, cleanup, and verification companion with optional Codex hooks.",
   "repository": {
@@ -32,7 +32,6 @@
     "prompts/describe.txt",
     "prompts/deslop.txt",
     "prompts/program.txt",
-    "prompts/reconcile.txt",
     "prompts/review.txt",
     "prompts/start.txt",
     "prompts/work.txt",

package/plugins/genesis/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis",
-  "version": "1.2.23",
+  "version": "1.2.25",
   "description": "Makes Codex aware of optional Genesis adoption for existing projects.",
   "author": {
     "name": "Mobily Enterprises"

package/prompts/deslop.txt

@@ -1,29 +1,14 @@
-For every repository listed in the task, read and follow that repository's
-`.agents/skills/genesis-deslop/SKILL.md` completely. Review and clean every
-listed repository before responding.
+Read and follow `.agents/skills/genesis-deslop/SKILL.md` completely.
 
-This is a dedicated behavior-preserving cleanup task, separate from
-implementation. Review the requested scope, or otherwise the ordinary Git diff
-and immediately related code. Apply every selected Stack cleanup instruction
-supplied below and load applicable official technology skills for additional
-language and framework context.
+This is an explicitly requested behavior-preserving cleanup of committed work.
+Resolve the commit or first-parent commit range from USER REQUEST exactly; when
+no scope is stated, use the latest commit. Require a clean worktree before
+editing and leave the cleanup as ordinary uncommitted work for review.
 
-Use `.genesis/machine-city.json` and the Genesis `index <name-or-path>` operation
-to find existing public and internal functions. Remove or consolidate genuine
-repeated helpers, but confirm behavior and call sites in source before changing
-them.
+Apply the selected Stack cleanup guidance and applicable technology skills in
+addition to the Genesis Deslop contract. Stack guidance may improve
+technology-specific cleanup, but it cannot broaden the resolved Git scope,
+weaken behavior preservation, or turn this into another implementation pass.
 
-The changed paths and nearby code are a location boundary, not permission to
-implement other behavior found there. Deslop may reorganize behavior already
-present; it may not complete, correct, or extend behavior. If review reveals a
-defect, missing behavior, contract mismatch, or test gap, report it as a
-follow-up finding and leave it unchanged in this pass, even when it is inside a
-changed path or appears related to the preceding implementation.
-
-Do not broaden the product change. Run focused checks when useful and summarize
-what became simpler, files changed, and checks actually run.
-
-Your response from this turn is the final user-facing answer for the original
-request. Make it concise and self-contained. Lead with the outcome, include the
-important implemented behavior and any genuine blocker or unfinished work, and
-do not mention automatic phases, hooks, or these instructions.
+Report the resolved range, what became simpler, files changed, checks actually
+run, and any defect or gap deliberately left for follow-up.

package/prompts/work.txt

@@ -8,15 +8,18 @@ Before adding a helper or public operation, query the Genesis
 `index <name-or-path>` operation and reuse an existing function when it already
 owns the behavior.
 
-This is the implementation turn. Do not edit the Blueprint, Program, or
-`.genesis/`; the separate reconciliation turn owns explanatory changes. Keep
-applicable consumer-owned Stack sections aligned when the implementation changes
-facts governed by those contracts. Follow the selected technology skill and the
-section's own schema; Genesis only transports the section and does not interpret
-or execute it. Never put an environment value or secret in Stack. Never invent
-missing external-resource values. Preserve useful work and report a genuinely
-missing resource instead of constructing a parallel fallback.
+Keep the Blueprint and affected Program modules aligned in this turn when the
+implementation intentionally changes observable product behavior. Private
+restructuring may require only corrected source citations or no explanatory
+edit. Keep applicable consumer-owned Stack sections aligned when implementation
+changes facts governed by those contracts. Follow the selected technology skill
+and the section's own schema; Genesis only transports the section and does not
+interpret or execute it. Never put an environment value or secret in Stack.
+Never invent missing external-resource values. Preserve useful work and report
+a genuinely missing resource instead of constructing a parallel fallback.
 
+Apply any supplied Stack Post-change guidance before reporting completion. It
+belongs to this implementation turn and does not request a follow-up agent turn.
 Run focused checks when useful. Summarize files changed, checks actually run,
 and anything still requiring attention.
 

package/skills/genesis-deslop/SKILL.md

@@ -1,13 +1,12 @@
 ---
 name: genesis-deslop
-description: Perform a separate behavior-preserving cleanup pass after implementation. Use when asked to Deslop, simplify, remove repeated helpers, clarify ownership, or align changed code with established project and technology patterns.
+description: Deslop committed work through an explicit behavior-preserving cleanup pass. Use when asked to Deslop a commit or recent commits, simplify completed work, remove repeated helpers, clarify ownership, or align changed code with established project and technology patterns.
 ---
 
 # Genesis Deslop
 
-Review and simplify the current local codebase without changing product
-behavior. Start with the requested scope, or otherwise the ordinary Git diff
-and the code immediately around it.
+Review and simplify committed work without changing product behavior. Deslop is
+explicit: never run it merely because implementation finished.
 
 When this repository is Genesis itself or has `genesis-compiler` installed
 locally, invoke every Genesis CLI operation through the project-pinned package:
@@ -16,6 +15,28 @@ package. Otherwise use `genesis <arguments>` only when that executable is
 already available on `PATH`. Never install or update Genesis merely to satisfy
 a workflow instruction.
 
+## Resolve the committed scope
+
+Before reading or editing the selected change, require a clean worktree and
+index with `git status --short`. Stop and report the existing paths when it is
+not clean; do not stash, commit, discard, or mix them into Deslop.
+
+Resolve the user's scope as follows:
+
+- With no stated scope, use the latest commit.
+- “The last N commits” means the net surviving change from the first parent
+  before those N commits through `HEAD`.
+- A named commit means that commit against its first parent.
+- An explicit commit range means exactly that range.
+- A root commit uses Git's root-diff form because it has no parent.
+
+Inspect the resolved commit identities and changed paths before editing. Review
+the committed diff, current source, direct call sites, relevant tests, and the
+affected Program and Stack context. Do not substitute the ordinary working-tree
+diff for the selected committed scope.
+
+## Apply the cleanup contract
+
 Apply the engineering approach supplied with the task. If this skill is invoked
 directly, read `genesis/engineering.md` as well as the relevant project context.
 Cleanup must reduce or preserve complexity, never introduce unapproved
@@ -26,7 +47,7 @@ operation to find existing public and internal functions before introducing or
 consolidating an abstraction. Confirm every apparent duplicate in source and
 its call sites.
 
-Within the preceding implementation's intended behavior and scope, leave no
+Within the selected commits' intended behavior and scope, leave no
 repeated helpers, no code that is unclear or hard to reason about, and no code
 that goes against established patterns in the codebase. Remove unnecessary
 wrappers, abandoned scaffolding, parallel framework plumbing, and speculative
@@ -34,7 +55,7 @@ abstractions. Consolidate ownership where one clear module is enough. Do not
 optimize for tiny files or indirection; optimize for a small, obvious design
 that a junior programmer can follow.
 
-Cleanup is not a second implementation pass. A changed path limits where cleanup
+Cleanup is not a second implementation pass. A committed path limits where cleanup
 may occur; it does not authorize different behavior in that file. Deslop may
 reorganize behavior already present; it may not complete, correct, or extend
 behavior. If review reveals a defect, missing behavior, contract mismatch, or
@@ -43,15 +64,22 @@ is inside a changed path or appears related to the preceding implementation. Do
 not implement the finding or alter tests to accommodate it during Deslop.
 
 Apply every technology-specific Deslop instruction supplied by the selected
-Stack. Load applicable official technology skills for additional framework and
-language context, but do not expect them to contain Genesis's cleanup policy.
+Stack and load applicable official technology skills for framework and language
+context. Stack guidance enriches this contract; it cannot weaken the
+behavior-preserving boundary, change the selected Git scope, or authorize
+unrelated implementation.
 
 You may edit or delete implementation and test files when that is the clearest
-behavior-preserving cleanup. Do not edit `genesis/`, `.genesis/`, Git metadata,
-dependency directories, generated build output, retained migration history, or
-external resources. Do not weaken tests, public behavior, or data guarantees.
-Do not create a second architecture or perform unrelated rewrites.
-
-Run focused checks when useful. Final declared checks remain available through
-the Genesis `verify` operation. Summarize what became simpler, files changed,
-and checks actually run.
+behavior-preserving cleanup. If moving or renaming selected source makes an
+affected Program citation stale, update only that citation or informational
+Implementation map. Do not change the Blueprint or a Program public contract to
+excuse cleanup behavior. Do not edit `.genesis/`, Git metadata, dependency
+directories, generated build output, retained migration history, or external
+resources. Do not weaken tests, public behavior, or data guarantees. Do not
+create a second architecture or perform unrelated rewrites.
+
+Leave the cleanup as ordinary uncommitted work for review and a later normal
+commit. Never amend or rewrite the selected commits. Run focused checks when
+useful. Final declared checks remain available through the Genesis `verify`
+operation. Summarize the resolved commit range, what became simpler, files
+changed, checks actually run, and follow-up findings left unchanged.

package/skills/genesis-deslop/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Genesis Deslop"
-  short_description: "Simplify changed code without behavior drift"
-  default_prompt: "Use $genesis-deslop for a separate behavior-preserving cleanup pass over the current changes."
+  short_description: "Clean up committed work without behavior drift"
+  default_prompt: "Use $genesis-deslop to Deslop the latest commit."

package/skills/genesis-project/SKILL.md

@@ -65,19 +65,25 @@ Neither is authority or proof; both may be regenerated with the Genesis
   tradeoff. Never silently override the engineering approach.
 - Work directly in the current Git tree and leave useful edits visible in the
   ordinary diff.
-- Do not edit the Blueprint, Program, or `.genesis/` during implementation; the
-  separate reconciliation turn owns explanatory updates. Keep exact
+- Keep the Blueprint and affected Program modules aligned in this same turn
+  when implementation intentionally changes observable product behavior.
+  Private restructuring may require only corrected Sources or an informational
+  Implementation map, and may require no explanatory edit. Keep exact
   consumer-owned operation declarations, such as Vibe64 `## Outputs`, aligned
   when implementation intentionally changes the corresponding commands or
   capabilities. Record only capability metadata and environment-variable names
   there, never values or secrets; do not infer or execute the section as
-  Genesis behavior.
+  Genesis behavior. Treat `.genesis/` as replaceable derived navigation data,
+  not authored product intent.
 - Follow established project and technology seams instead of creating parallel
   frameworks, persistence layers, transports, validators, or UI systems.
 - Never invent unavailable external-resource values or pass literal
   environment-variable names as data. Report the missing resource and preserve
   useful work.
-- Keep the implementation direct and cohesive. Run focused checks when useful.
+- Keep the implementation direct and cohesive. Apply any supplied Stack
+  Post-change guidance before reporting completion; it is part of this
+  implementation turn, not a request for another agent turn. Run focused checks
+  when useful.
 
 ## Verify and report
 

package/src/cli.js

@@ -20,12 +20,8 @@ import {
   verify,
 } from './index.js';
 import {
-  authorizeCodexTurn,
   codexAdoptionRecommendation,
   codexSessionContext,
-  completeCodexTurn,
-  discardCodexTurn,
-  recordCodexTurn,
 } from './index/codex-hooks.js';
 import { engineeringProfile, readEngineeringBaseline } from './index/engineering.js';
 import { asDiagnostic, fail } from './index/errors.js';
@@ -138,8 +134,8 @@ function parseCommand(argv) {
         'Command inspect requires environment or section <name>.',
       );
     }
-  } else if (command === 'hook' && (operands.length !== 1 || !['authorize', 'begin', 'discover', 'end', 'session', 'stop'].includes(operands[0]))) {
-    fail('CLI_HOOK_ACTION_REQUIRED', 'Command hook requires exactly one of: discover, session, begin, authorize, stop, end.');
+  } else if (command === 'hook' && (operands.length !== 1 || !['discover', 'session'].includes(operands[0]))) {
+    fail('CLI_HOOK_ACTION_REQUIRED', 'Command hook requires exactly one of: discover, session.');
   } else if (!['adopt', 'context', 'hook', 'index', 'inspect', 'prompt'].includes(command) && operands.length > 0) {
     fail('CLI_EXTRA_ARGUMENT', `Command ${command} accepts no arguments.`);
   }
@@ -266,8 +262,6 @@ function writeResult(command, result) {
   }
   if (command === 'hook') {
     if (['discover', 'session'].includes(result.kind) && result.output) line(process.stdout, result.output);
-    else if (result.kind === 'authorize') line(process.stdout, `authorize: ${result.status}`);
-    else if (result.kind === 'stop') line(process.stdout, JSON.stringify(result.output));
     return;
   }
   if (command === 'stack' && Array.isArray(result.pieces)) {
@@ -292,20 +286,6 @@ function writeResult(command, result) {
   line(process.stdout, `${command}: ${result.status}`);
 }
 
-async function hookInput() {
-  if (process.stdin.isTTY) fail('CODEX_HOOK_INPUT_INVALID', 'Codex hook input must be supplied on stdin.');
-  const chunks = [];
-  let bytes = 0;
-  for await (const chunk of process.stdin) {
-    bytes += chunk.length;
-    if (bytes > 1024 * 1024) fail('CODEX_HOOK_INPUT_INVALID', 'Codex hook input exceeds 1 MiB.');
-    chunks.push(chunk);
-  }
-  try { return JSON.parse(Buffer.concat(chunks).toString('utf8')); } catch (error) {
-    fail('CODEX_HOOK_INPUT_INVALID', `Codex hook input is invalid JSON: ${error.message}.`);
-  }
-}
-
 async function execute({ command, operands, options }, { signal } = {}) {
   const projectRoot = options.projectRoot || process.cwd();
   const stackPackages = options.stackPackages || [];
@@ -382,20 +362,7 @@ async function execute({ command, operands, options }, { signal } = {}) {
     if (operands[0] === 'discover') {
       return { kind: 'discover', ...await codexAdoptionRecommendation({ projectRoot }) };
     }
-    if (operands[0] === 'session') {
-      return { kind: 'session', ...await codexSessionContext({ projectRoot }) };
-    }
-    if (operands[0] === 'authorize') {
-      return { kind: 'authorize', ...await authorizeCodexTurn({ projectRoot }) };
-    }
-    const input = await hookInput();
-    if (operands[0] === 'begin') {
-      return { kind: 'begin', ...await recordCodexTurn({ input, projectRoot }) };
-    }
-    if (operands[0] === 'end') {
-      return { kind: 'end', ...await discardCodexTurn({ input, projectRoot }) };
-    }
-    return { kind: 'stop', status: 'ready', output: await completeCodexTurn({ input, projectRoot }) };
+    return { kind: 'session', ...await codexSessionContext({ projectRoot }) };
   }
   if (command === 'verify') {
     return verify({

package/src/index/assets.js

@@ -6,7 +6,6 @@ const assets = {
   adopt: new URL('prompts/adopt.txt', root),
   work: new URL('prompts/work.txt', root),
   describe: new URL('prompts/describe.txt', root),
-  reconcile: new URL('prompts/reconcile.txt', root),
   deslop: new URL('prompts/deslop.txt', root),
   program: new URL('prompts/program.txt', root),
   blueprint: new URL('prompts/blueprint.txt', root),