@longtable/provider-codex 0.1.57 → 0.1.59

package/dist/index.js

@@ -14,7 +14,7 @@ export const CODEX_PROVIDER_CAPABILITIES = {
         "Installed prompt files are not guaranteed to become slash commands in current Codex builds.",
         "Native parallel subagents may exist in an interactive session, but the npm CLI must not require them.",
         "Sequential panel fallback is the stable provider-neutral path.",
-        "MCP elicitation can present Researcher Checkpoints when the Codex client exposes granular MCP elicitations; numbered prompts remain the fallback."
+        "Attached tmux sessions can use a LongTable-owned tmux_popup renderer first; MCP elicitation and numbered prompts remain fallback transports."
     ]
 };
 export function getCodexProviderCapabilities() {

package/dist/skills.js

@@ -101,9 +101,8 @@ function baseSkillSpecs(surface = "compact") {
                 "- 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.",
-                "- In attached tmux Codex sessions where the OMX question renderer is available, use the tmux popup first for researcher checkpoints; if it cannot run, disclose that transport degradation before falling back.",
-                "- When the `mcp__longtable_state__.elicit_question` tool is available, use it after the tmux popup path, or first when tmux popup is unavailable, 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 tmux popup and MCP elicitation are unavailable, unsupported, declined, canceled, or blocked by the client.",
+                "- 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.",
                 "- If `CURRENT.md` shows a pending required checkpoint, ask the researcher for a selection and wait. Do not choose or record `longtable decide --question <id> --answer <value>` unless the researcher explicitly provides that value.",
                 "- Preserve open tensions and authorship instead of forcing closure.",
                 "- Label unsupported external claims as inference or estimate."
@@ -270,12 +269,11 @@ function baseSkillSpecs(surface = "compact") {
                 "",
                 "## Option UI Policy",
                 "",
-                "- Use attached-tmux popup transport first for Codex terminal sessions when the OMX renderer is available.",
-                "- Use MCP/native structured elicitation when available after the popup path, or first when no attached tmux popup can run.",
+                "- 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 copy OMX renderer code or make OMX runtime state the LongTable contract; disclose no-tmux degradation and provide fallback.",
+                "- Do not require tmux. If a future Codex popup transport is tmux-only, label it as optional and provide fallback.",
                 "",
                 "## Fallback",
                 "",
@@ -310,12 +308,12 @@ function baseSkillSpecs(surface = "compact") {
                 "",
                 "- Do not collapse disagreement too early.",
                 "- Use a Researcher Checkpoint before treating a high-stakes research decision as settled.",
-                "- `longtable panel --provider codex --native-workers` should be tried first for Codex panel execution when attached tmux and `codex` are available; add `--wait <ms>` when a bounded command should wait for terminal result files. `--native-subagents` remains a compatibility adapter for provider-native subagents.",
-                "- If terminal native workers are unavailable and Codex native subagents/Agents are available, use them as the provider-native execution adapter; if not, run the same roles sequentially and disclose the fallback.",
+                "- `longtable panel --provider codex --native-workers` may launch durable LongTable-native role workers when the CLI/runtime supports it; add `--wait <ms>` when a bounded command should wait for terminal result files. `--native-subagents` remains a compatibility adapter for provider-native subagents.",
+                "- If Codex native subagents are available, they may be used as a provider-native execution adapter; if not, run the same roles sequentially and disclose the fallback.",
                 "- Sequential fallback is always the stable degradation path; native workers and native subagents must normalize final role outputs back into `PanelResult`.",
                 "- Do not use OMX `$team` or worker vocabulary as the LongTable product contract. LongTable panel records are the source of truth.",
-                "- For panel checkpoints, prefer attached-tmux popup transport when available, then `mcp__longtable_state__.elicit_question`, then numbered fallback.",
-                "- Use `longtable question --print --provider codex --prompt \"...\"` only as the numbered fallback when popup transport and MCP elicitation are unavailable or not accepted.",
+                "- If the `mcp__longtable_state__.elicit_question` tool is available, prefer it for the panel checkpoint before synthesizing or revising.",
+                "- Use `longtable question --print --provider codex --prompt \"...\"` only as the numbered fallback when MCP elicitation is unavailable or not accepted.",
                 "- Use `longtable panel --print --prompt \"...\"` only as an optional canonical prompt aid, not as the user's primary interface.",
                 "- Terminal native worker runs (`completed` or `blocked`) are recorded by `longtable panel --native-workers --wait`, `longtable panel status --wait`, or `longtable panel resume --wait`; blocked role outputs remain blocked in the handoff. For external/provider results outside that lifecycle, persist structured role outputs with `longtable panel record --invocation <id> --result-file <json>` before generating `longtable handoff`.",
                 "- A result file should contain final role summaries, claims, objections, open questions, and evidence refs only; do not persist hidden reasoning, raw tool traces, or tmux logs."

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@longtable/provider-codex",
-  "version": "0.1.57",
+  "version": "0.1.59",
   "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.57",
-    "@longtable/core": "0.1.57",
-    "@longtable/setup": "0.1.57"
+    "@longtable/checkpoints": "0.1.59",
+    "@longtable/core": "0.1.59",
+    "@longtable/setup": "0.1.59"
   },
   "devDependencies": {
     "@types/node": "^22.10.1",