@longtable/provider-codex 0.1.50 → 0.1.52

package/dist/skills.js

@@ -55,14 +55,16 @@ function baseSkillSpecs(surface = "compact") {
                 "- `$longtable: deploy a research team to review this measurement plan, show the main disagreements, and ask me what decision should be recorded before you revise it.`",
                 "- `$longtable: use editor, reviewer, methods, measurement, and voice perspectives to evaluate this manuscript section. Do not collapse disagreement too early.`",
                 "- `$longtable-methods`, `$longtable-measure`, `$longtable-theory`, `$longtable-reviewer`, or `$longtable-voice` when the researcher explicitly wants that shortcut.",
-                "- `$longtable-interview` to create or continue the first research-start interview.",
+                "- `$longtable-start` to create or continue the first research-start interview.",
+                "- `$longtable-interview` to run a structured follow-up interview after a Research Specification exists.",
                 "",
                 "## Routing Rules",
                 "",
                 "- `lt explore` keeps the problem open and asks clarifying or tension questions before recommending closure.",
                 "- `lt review` starts with the strongest weakness, objection, or missing evidence.",
                 "- `lt panel` creates a visible multi-role review with synthesis, role opinions, conflict summary, and a decision prompt.",
-                "- `$longtable-interview` runs the provider-native LongTable start interview. It replaces the old CLI start questionnaire as the primary research-start surface.",
+                "- `$longtable-start` runs the provider-native LongTable start interview. It replaces the old CLI start questionnaire as the primary research-start surface.",
+                "- `$longtable-interview` is post-start. If `.longtable/state.json` or `CURRENT.md` lacks a usable Research Specification, route to `$longtable-start` before offering option-first follow-up choices.",
                 "- Natural references to methods, measurement, theory, reviewer, editor, ethics, venue, or voice should foreground the matching LongTable role.",
                 "- The compact visible shortcut set is methods, measure, theory, reviewer, and voice. Other roles remain available through this router when the request calls for them.",
                 "- When research responsibility is about to shift, surface a Researcher Checkpoint before closure.",
@@ -96,7 +98,8 @@ function baseSkillSpecs(surface = "compact") {
                 "- Treat provider-native question UI as transport; LongTable state records are the source of truth.",
                 "- For systematic review, meta-analysis, PDF collection, full-text extraction, institutionally licensed sources, or TDM work, ensure `longtable access setup` readiness exists or surface an ACCESS CHECKPOINT before continuing.",
                 "- Access setup records capability status only. The researcher handles VPN/proxy/library/SSO login directly; LongTable must not store passwords, API keys, tokens, PDFs, or full text in setup state.",
-                "- For `$longtable-interview`, use natural-language turns for the interview and reserve MCP option UI for the final research-facing Research Specification checkpoint; First Research Shape is only a shorter handle/resume layer.",
+                "- For `$longtable-start`, use natural-language turns for the interview and reserve MCP option UI for the final research-facing Research Specification checkpoint; First Research Shape is only a shorter handle/resume layer.",
+                "- For `$longtable-interview`, use option-first follow-up choices only after a usable Research Specification exists. Always include an escape hatch such as Other, free text, or one open follow-up question.",
                 "- Do not let unrelated pending Researcher Checkpoints interrupt the interview. Mention them only as separate unresolved checkpoints, and treat them as blocking only when the researcher is confirming, saving, or recording a research decision.",
                 "- When the `mcp__longtable_state__.elicit_question` tool is available, use it first for researcher checkpoints so Codex can show the MCP elicitation UI and LongTable can record the answer as `mcp_elicitation`.",
                 "- Use `longtable question --print --provider codex --prompt \"...\"` only as a fallback when the MCP tool is unavailable, unsupported, declined, canceled, or blocked by the client.",
@@ -106,8 +109,8 @@ function baseSkillSpecs(surface = "compact") {
             ]
         },
         {
-            name: "longtable-interview",
-            description: "Use for `$longtable-interview`: create or continue a LongTable research-start interview inside Codex, then store a Research Specification through MCP/state, with First Research Shape kept as an optional short handle layer.",
+            name: "longtable-start",
+            description: "Use for `$longtable-start`: create or continue a LongTable research-start interview inside Codex, then store a Research Specification through MCP/state, with First Research Shape kept as an optional short handle layer.",
             body: [
                 "## Purpose",
                 "",
@@ -115,7 +118,8 @@ function baseSkillSpecs(surface = "compact") {
                 "",
                 "## When To Use",
                 "",
-                "- The user invokes `$longtable-interview`.",
+                "- The user invokes `$longtable-start`.",
+                "- The user invokes `$longtable-interview` but the workspace has no usable Research Specification.",
                 "- The user wants to start a LongTable research workspace from inside Codex.",
                 "- A workspace exists but `CURRENT.md` or `.longtable/state.json` lacks a usable Research Specification, or has only a First Research Shape.",
                 "",
@@ -230,6 +234,48 @@ function baseSkillSpecs(surface = "compact") {
                 "",
                 "If MCP tools are unavailable, continue the natural-language interview in Codex, but state that durable LongTable state could not be written. Do not pretend a checkpoint, First Research Shape, or Research Specification was recorded."
             ]
+        },
+        {
+            name: "longtable-interview",
+            description: "Use for `$longtable-interview`: run an option-first LongTable follow-up interview after a usable Research Specification exists; route to `$longtable-start` when no spec exists.",
+            body: [
+                "## Purpose",
+                "",
+                "Run a post-start LongTable interview inside Codex. This skill is for structured follow-up decisions after the research has a usable Research Specification.",
+                "",
+                "## Required Routing",
+                "",
+                "- First inspect `CURRENT.md` and `.longtable/state.json` when available.",
+                "- If no usable Research Specification exists, route to `$longtable-start` immediately.",
+                "- If only a First Research Shape exists, route to `$longtable-start` and continue into the next Research Specification question or preview.",
+                "- Do not run an option-only interview before the Research Specification exists.",
+                "",
+                "## When To Use",
+                "",
+                "- The user invokes `$longtable-interview` and a usable Research Specification exists.",
+                "- The user wants to revise, extend, or resolve a decision in an existing Research Specification.",
+                "- The user needs a bounded follow-up interview around a checkpoint, spec patch, evidence boundary, method choice, coding rule, or protected decision.",
+                "",
+                "## Core Flow",
+                "",
+                "1. Read the current Research Specification and identify the decision or section being interviewed.",
+                "2. Present a small option-first choice set tied to the current specification.",
+                "3. Include an escape hatch such as `Other`, free text, or `ask one open question first`.",
+                "4. If the answer changes the specification, propose or apply a Research Specification patch through MCP/state when available.",
+                "5. Record the resulting decision as a `DecisionRecord` or explicit open tension; never silently overwrite conflicting research commitments.",
+                "",
+                "## Option UI Policy",
+                "",
+                "- Use MCP/native structured elicitation when available.",
+                "- Use terminal selector only when the runtime has interactive TTY support.",
+                "- Use numbered/plain text fallback when structured UI is unavailable.",
+                "- Treat UI as transport. The durable product contract remains `QuestionRecord -> DecisionRecord`.",
+                "- Do not require tmux. If a future Codex popup transport is tmux-only, label it as optional and provide fallback.",
+                "",
+                "## Fallback",
+                "",
+                "If MCP tools are unavailable, continue in Codex with explicit options and state that durable LongTable state could not be written."
+            ]
         }
     ];
     const fullOnly = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@longtable/provider-codex",
-  "version": "0.1.50",
+  "version": "0.1.52",
   "private": false,
   "description": "Codex adapter surface for LongTable",
   "type": "module",
@@ -15,9 +15,9 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@longtable/checkpoints": "0.1.50",
-    "@longtable/core": "0.1.50",
-    "@longtable/setup": "0.1.50"
+    "@longtable/checkpoints": "0.1.52",
+    "@longtable/core": "0.1.52",
+    "@longtable/setup": "0.1.52"
   },
   "devDependencies": {
     "@types/node": "^22.10.1",