abelworkflow 0.6.3 → 0.6.4

package/.gitignore

@@ -13,3 +13,4 @@ skills/dev-browser/tmp/
 .codex/
 *pycache*/
 .codex
+openspec/

package/commands/oc/plan.md

@@ -77,7 +77,7 @@ argument-hint: [change_name]
 - Use `openspec list --specs` to check for conflicts with existing specifications.
 - Search existing patterns with `rg -n "INVARIANT:|PROPERTY:|Constraint:" openspec/` before defining new ones.
 - For complex proposals, consider running steps 2-4 iteratively on sub-components.
-- Use `AskUserQuestions` for ANY ambiguity—do not assume or guess.
+- Ask the user directly for ANY ambiguity—do not assume or guess.
 
 **Exit Criteria**
 A proposal is ready to exit the Plan phase only when:

package/commands/oc/research.md

@@ -26,7 +26,7 @@ Produce constraint sets that narrow the solution space, plus measurable success
 
 ## Phase 0 — Requirement Intake Gate (MANDATORY)
 - **MUST** confirm the user’s requirement exists and is clear **before** any research/action.
-- If missing/unclear, **MUST** use `AskUserQuestions` to collect: goal, in-scope area, top scenarios, non-goals, known constraints, success signals.
+- If missing/unclear, **MUST** ask the user directly in a concise grouped message to collect: goal, in-scope area, top scenarios, non-goals, known constraints, success signals.
 - **MUST NOT** run `/opsx:new`, any codebase retrieval, spawn subagents, or generate artifacts until the user confirms a brief requirement summary.
 
 ---
@@ -97,7 +97,7 @@ All explore subagents MUST return valid JSON using this schema:
 
 ## Phase 7 — User Interaction for Ambiguity Resolution
 - Compile prioritized list of open questions from aggregated reports.
-- Use `AskUserQuestions` tool to present questions systematically:
+- Present questions directly to the user in a concise grouped message:
   * Group related questions together.
   * Provide context for each question.
   * Suggest default answers when applicable.
@@ -122,5 +122,5 @@ All explore subagents MUST return valid JSON using this schema:
   - `openspec status --change <name>` - Check artifact completion status
   - `openspec instructions proposal --change <name>` - Get proposal instructions
 - Validate subagent outputs conform to template before aggregation.
-- Use `AskUserQuestions` for ANY ambiguity—do not assume or guess.
-<!-- OC:RESEARCH:END -->
+- Ask the user directly for ANY ambiguity—do not assume or guess.
+<!-- OC:RESEARCH:END -->

package/lib/cli.mjs

@@ -1871,8 +1871,8 @@ function buildCodexConfigContent(currentContent, {
     content = mergeCodexTemplateDefaults(content, effectiveTemplateContent);
   }
   const lineEnding = detectLineEnding(content);
-  if (includeSubagentDefaults && readTopLevelTomlString(content, "approvals_reviewer") === "guardian_subagent") {
-    content = updateTopLevelTomlField(content, "approvals_reviewer", "reviewer");
+  if (includeSubagentDefaults && readTopLevelTomlString(content, "approvals_reviewer") === "reviewer") {
+    content = updateTopLevelTomlField(content, "approvals_reviewer", "guardian_subagent");
   }
   content = updateTopLevelTomlField(content, "model_provider", providerId);
   content = updateTopLevelTomlField(content, "preferred_auth_method", "apikey");

package/lib/templates/codex/config-base.toml

@@ -2,7 +2,7 @@ personality = "pragmatic"
 model_provider = "abelworkflow"
 disable_response_storage = true
 preferred_auth_method = "apikey"
-approvals_reviewer = "reviewer"
+approvals_reviewer = "guardian_subagent"
 approval_policy = "on-request"
 sandbox_mode = "workspace-write"
 service_tier = "fast"

package/package.json

@@ -1,8 +1,11 @@
 {
   "name": "abelworkflow",
-  "version": "0.6.3",
+  "version": "0.6.4",
   "description": "Install AbelWorkflow into ~/.agents and create Claude/Codex symlinks.",
   "type": "module",
+  "scripts": {
+    "test:contracts": "node --test test/runtime-doc-contracts.test.mjs"
+  },
   "bin": {
     "abelworkflow": "bin/abelworkflow.mjs"
   },