specrails-hub 1.55.0 → 1.55.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specrails-hub",
-  "version": "1.55.0",
+  "version": "1.55.1",
   "license": "MIT",
   "repository": {
     "type": "git",

package/server/dist/chat-manager.js

@@ -340,12 +340,15 @@ class ChatManager {
             `When creating or updating tickets, write directly to this JSON file.\n\n` +
             `IMPORTANT: Be efficient. Minimize tool calls. Only read files that are directly relevant. ` +
             `Do not explore broadly — focus on the specific task.`;
+        const scopedBase = `${base}\n\n` +
+            `When "Specrails Tickets" or "OpenSpec Specs" sections are present below, treat them as authoritative project context. ` +
+            `For roadmap-style requests like "suggest the next best spec", ground the answer in that context, avoid duplicates, and propose one concrete next spec instead of generic directions.`;
         if (!scope || !this._cwd)
-            return base;
+            return scopedBase;
         const prefix = (0, context_scope_1.buildScopedSystemPromptPrefix)(scope, this._cwd);
         if (!prefix)
-            return base;
-        return `${base}\n\n${prefix}`;
+            return scopedBase;
+        return `${scopedBase}\n\n${prefix}`;
     }
     isActive(conversationId) {
         return this._activeProcesses.has(conversationId);
@@ -434,8 +437,18 @@ class ChatManager {
         const scopeFlags = conversationScope && this._adapter.id === 'claude'
             ? (0, context_scope_1.toolFlagsForScope)(conversationScope).args
             : [];
+        let promptForAdapter = resolvedText;
+        if (conversation.kind === 'explore' && this._adapter.id === 'codex' && conversationScope && this._cwd) {
+            const scopedContext = (0, context_scope_1.buildScopedSystemPromptPrefix)(conversationScope, this._cwd);
+            if (scopedContext) {
+                promptForAdapter =
+                    `Project context selected in Add Spec. Use it to avoid duplicate specs and to make project-specific recommendations.\n\n` +
+                        `${scopedContext}\n\n` +
+                        `## User turn\n\n${resolvedText}`;
+            }
+        }
         let args = this._adapter.buildArgs(action, {
-            prompt: resolvedText,
+            prompt: promptForAdapter,
             systemPrompt,
             model,
             sessionId: conversation.session_id ?? undefined,

package/server/dist/command-resolver.js

@@ -18,6 +18,41 @@ function findHubRoot() {
     return null;
 }
 const HUB_ROOT = findHubRoot();
+function builtInCommand(commandPath, commandArgs) {
+    if (commandPath !== 'specrails:explore-spec')
+        return null;
+    return `You are a senior product engineer helping the user shape one backlog spec inside specrails-hub's Explore Spec experience.
+
+Do not use any local skill, slash-command workflow, or repository-change workflow. Stay inside this chat and shape the draft ticket only. Do not inspect active change folders unless the user explicitly asks about them, and do not create or modify files. The hub commits the final ticket only when the user clicks Create Spec.
+
+Your job is to maintain a live draft. After every assistant turn that changes draft state, end your message with a fenced \`spec-draft\` JSON block. The visible prose should match the user's language. Draft fields must be written in English.
+
+Use this draft schema. Omit fields you do not want to update:
+
+\`\`\`spec-draft
+{
+  "title": "Concise, action-oriented title",
+  "description": "## Problem Statement\\n2-3 sentences.\\n\\n## Proposed Solution\\n3-5 sentences.\\n\\n## Out of Scope\\n- bullet\\n\\n## Technical Considerations\\n- bullet\\n\\n## Estimated Complexity\\nMedium - one sentence justification.",
+  "labels": ["short-label"],
+  "priority": "low | medium | high | critical",
+  "acceptanceCriteria": ["Short, testable criterion"],
+  "chips": ["Up to 3 short replies"],
+  "ready": false
+}
+\`\`\`
+
+Rules:
+- Ask only the clarifying questions genuinely needed to make the spec concrete.
+- Keep visible replies brief.
+- Set \`ready: true\` only when the draft has a title, description, acceptance criteria, and no outstanding clarifying question.
+- Never call \`/specrails:propose-spec\`, \`/specrails:implement\`, or any slash command with side effects.
+
+The user's idea follows below. Begin the Explore Spec conversation.
+
+---
+
+${commandArgs}`.trim();
+}
 /**
  * Try to find a command/skill .md file for the given command path parts
  * within the given base directory. Returns the resolved path or null.
@@ -49,6 +84,9 @@ function resolveCommand(command, cwd) {
     const commandPath = match[1];
     const commandArgs = match[2].trim();
     const parts = commandPath.split(':');
+    const builtIn = builtInCommand(commandPath, commandArgs);
+    if (builtIn)
+        return builtIn;
     // 1. Check the project directory
     let resolvedPath = findCommandFile(cwd, parts);
     // 2. Fallback: check the hub's own directory

package/server/dist/explore-cwd-manager.js

@@ -46,9 +46,9 @@ invoke ticket-creation slash commands.
 
 ## What you must do
 
-- Act as an interactive thinking partner, same stance as
-  \`/specrails:explore-spec\`: investigate just enough, ask only the
-  questions you need, surface trade-offs, propose a concrete shape.
+- Act as an interactive thinking partner for this ticket draft: investigate
+  just enough, ask only the questions you need, surface trade-offs, propose a
+  concrete shape.
 - Maintain the structured live draft via fenced \`spec-draft\` JSON blocks at
   the end of every turn that updates draft state. The hub parses these blocks
   and updates the user's draft pane; the block itself is stripped from the

package/server/dist/project-router.js

@@ -38,6 +38,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.stripSpecMetadataSections = stripSpecMetadataSections;
 exports.extractShortSummary = extractShortSummary;
+exports.deriveFallbackShortSummary = deriveFallbackShortSummary;
 exports.formatDescriptionWithCriteria = formatDescriptionWithCriteria;
 exports.resolveDefaultSpecModel = resolveDefaultSpecModel;
 exports.createProjectRouter = createProjectRouter;
@@ -242,6 +243,22 @@ function extractShortSummary(buffer) {
     const body = m[1].trim();
     return body.length > 0 ? body : null;
 }
+function deriveFallbackShortSummary(title, description) {
+    const plain = description
+        .replace(/```[\s\S]*?```/g, ' ')
+        .replace(/^#{1,6}\s+.*$/gm, ' ')
+        .replace(/^\s*[-*]\s+/gm, '')
+        .replace(/\[[^\]]+\]\([^)]+\)/g, (m) => m.match(/\[([^\]]+)\]/)?.[1] ?? '')
+        .replace(/[`*_>]/g, '')
+        .replace(/\s+/g, ' ')
+        .trim();
+    const source = plain || title.trim();
+    if (!source)
+        return null;
+    const sentence = source.match(/^(.{24,}?[.!?])(?:\s|$)/)?.[1] ?? source;
+    const capped = sentence.length > 160 ? `${sentence.slice(0, 157).trimEnd()}...` : sentence;
+    return (0, ticket_store_1.clampShortSummary)(capped);
+}
 /**
  * Fold an `acceptanceCriteria` array into a ticket description body, writing
  * (or replacing) a `## Acceptance Criteria` section.
@@ -1757,11 +1774,15 @@ function createProjectRouter(registry) {
         const dedupRule = quickScope.specrails
             ? `- The "Specrails Tickets" section above lists every ticket already in the backlog. Do NOT propose a duplicate or a near-duplicate of any of them. If the user's idea is already covered by an existing ticket, say so in "Problem Statement" and pick a *different* angle / sub-feature / next step that builds on the existing one — do not repeat it.\n`
             : '';
+        const backlogRecommendationRule = quickScope.specrails
+            ? `- If the user's idea asks for the "next best spec" or a backlog recommendation, use the existing tickets and OpenSpec context to choose one concrete next spec. Do not respond with generic product directions.\n`
+            : '';
         let baseSystemPrompt = `You are a senior product engineer generating a structured spec proposal.\n\n` +
             (specsPrefix ? `${specsPrefix}\n\n` : '') +
             `RULES:\n` +
             `${codebaseRule}\n` +
             dedupRule +
+            backlogRecommendationRule +
             `- Do NOT create files, tickets, or issues.\n` +
             `- Output ONLY the structured markdown below. No preamble, no explanation.\n\n` +
             `REQUIRED FORMAT:\n` +
@@ -2235,6 +2256,9 @@ function createProjectRouter(registry) {
                     .trim();
             }
         }
+        if (bodyShortSummary === null) {
+            bodyShortSummary = deriveFallbackShortSummary(rawTitle, descriptionForStore);
+        }
         try {
             const filePath = ticketPath(req);
             const now = new Date().toISOString();

package/server/dist/providers/codex-adapter.js

@@ -29,6 +29,7 @@ const CODEX_MODELS = [
     { value: 'gpt-5.3-codex', label: 'GPT-5.3 Codex' },
 ];
 const SANDBOX_FLAGS = ['--sandbox', 'workspace-write'];
+const RAIL_SANDBOX_FLAGS = ['--sandbox', 'danger-full-access'];
 // `codex exec resume` does NOT accept `--sandbox` (the flag only exists on
 // `codex exec`); pass the policy as a `-c` config override instead so the
 // resumed session honours workspace-write even when the per-project
@@ -44,7 +45,21 @@ function fold(systemPrompt, prompt) {
 function buildCodexArgs(action, opts) {
     const args = [];
     switch (action) {
-        case 'chat-turn':
+        case 'chat-turn': {
+            // chat-turn (Explore) spawns codex from the hub-managed explore-cwd,
+            // which already ships an AGENTS.md with the Explore stance. Folding the
+            // hub's system prompt into the positional argv would double-inject the
+            // framing AND, because the user message in Explore is often very short
+            // ("quiero hacer un tetris"), the long system text dominates the prompt
+            // and codex responds to the system instructions instead of the user.
+            // Trust AGENTS.md and pass only the user prompt.
+            args.push('exec', '--json', ...SANDBOX_FLAGS, SKIP_GIT_CHECK);
+            args.push(opts.prompt);
+            args.push('--model', opts.model);
+            if (opts.extraArgs)
+                args.push(...opts.extraArgs);
+            return args;
+        }
         case 'spec-gen':
         case 'agent-refine':
         case 'auto-title':
@@ -56,7 +71,21 @@ function buildCodexArgs(action, opts) {
                 args.push(...opts.extraArgs);
             return args;
         }
-        case 'chat-resume':
+        case 'chat-resume': {
+            if (!opts.sessionId) {
+                throw new Error(`${action} requires sessionId`);
+            }
+            // See chat-turn note: AGENTS.md in explore-cwd carries the Explore
+            // framing; the per-turn argv must stay user-text-only so codex doesn't
+            // mistake the system prompt for the user request.
+            args.push('exec', 'resume', '--json', ...SANDBOX_RESUME_FLAGS, SKIP_GIT_CHECK);
+            args.push(opts.sessionId);
+            args.push(opts.prompt);
+            args.push('--model', opts.model);
+            if (opts.extraArgs)
+                args.push(...opts.extraArgs);
+            return args;
+        }
         case 'setup-enrich-resume': {
             if (!opts.sessionId) {
                 throw new Error(`${action} requires sessionId`);
@@ -70,10 +99,12 @@ function buildCodexArgs(action, opts) {
             return args;
         }
         case 'rail-job': {
-            // Rail-job runs in the project root (a git repo). Sandbox still
-            // workspace-write so codex can apply file changes; skip-git-check kept
-            // for symmetry — harmless when a git repo IS present.
-            args.push('exec', '--json', ...SANDBOX_FLAGS, SKIP_GIT_CHECK);
+            // Rail jobs are headless implementation pipelines. They must run repo
+            // inspection, edits, tests, and git probes without interactive approval.
+            // On Windows, Codex's workspace-write sandbox can fail before the first
+            // shell command with `windows sandbox: spawn setup refresh`; full access
+            // matches the existing fully-autonomous rail contract.
+            args.push('exec', '--json', ...RAIL_SANDBOX_FLAGS, SKIP_GIT_CHECK);
             args.push(fold(opts.systemPrompt, opts.prompt));
             args.push('--model', opts.model);
             if (opts.extraArgs)

package/server/dist/queue-manager.js

@@ -543,7 +543,9 @@ class QueueManager {
         if (/\/(specrails|sr):(implement|batch-implement)\b/.test(commandToRun)) {
             systemAppend += '\n\nIMPORTANT: The ticket/spec data for this project is stored locally in .specrails/local-tickets.json. ' +
                 'You MUST read specs from this file. Do NOT attempt to fetch tickets from Jira, Linear, GitHub Issues, or any other external tracker. ' +
-                'The #<id> references in the command correspond to ticket IDs inside .specrails/local-tickets.json.';
+                'The #<id> references in the command correspond to ticket IDs inside .specrails/local-tickets.json. ' +
+                'Do NOT require jq to inspect this file; on Windows or when jq is unavailable, use PowerShell (`Get-Content .specrails/local-tickets.json -Raw | ConvertFrom-Json`) or Node.js built-ins. ' +
+                'When running tests, use the project-defined scripts and package manager commands as-is; do NOT add Jest-only flags such as --runInBand to Vitest commands.';
             const attachmentContext = this._buildImplementAttachmentContext(commandToRun);
             if (attachmentContext) {
                 systemAppend += attachmentContext;

package/server/dist/util/cli-prompt.js

@@ -56,19 +56,25 @@ function transformClaudeArgsForWindows(args) {
 }
 // Codex `exec` flags we currently use that take a value (rest are
 // boolean). Update if we ever pass new value-bearing flags.
-const CODEX_EXEC_VALUE_FLAGS = new Set(['--model']);
+const CODEX_EXEC_VALUE_FLAGS = new Set(['--model', '--sandbox', '-c']);
 function transformCodexArgsForWindows(args) {
-    // Expected shape: `exec [...flags] <prompt> [...flags]`.
+    // Expected shapes:
+    //   exec [...flags] <prompt> [...flags]
+    //   exec resume [...flags] <sessionId> <prompt> [...flags]
     if (args.length === 0 || args[0] !== 'exec') {
         return { args, stdinPayload: null };
     }
     const out = ['exec'];
+    const isResume = args[1] === 'resume';
+    if (isResume)
+        out.push('resume');
     let stdin = null;
     let promptReplacedIdx = -1;
-    let i = 1;
+    let positionalCount = 0;
+    let i = isResume ? 2 : 1;
     while (i < args.length) {
         const a = args[i];
-        if (a.startsWith('--')) {
+        if (a.startsWith('-') && a !== '-') {
             out.push(a);
             if (CODEX_EXEC_VALUE_FLAGS.has(a) && i + 1 < args.length) {
                 out.push(args[i + 1]);
@@ -78,8 +84,9 @@ function transformCodexArgsForWindows(args) {
             i += 1;
             continue;
         }
-        // First non-flag positional is the prompt.
-        if (stdin === null) {
+        positionalCount += 1;
+        const isPrompt = isResume ? positionalCount === 2 : positionalCount === 1;
+        if (isPrompt && stdin === null) {
             stdin = a;
             promptReplacedIdx = out.length;
             out.push('-');