@dzhechkov/keysarium 1.5.15 → 1.5.17

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dzhechkov/keysarium",
-  "version": "1.5.15",
+  "version": "1.5.17",
   "description": "AI Case Research Toolkit for Claude Code — full 7-phase pipeline with feature-adr, dream cycles, background workers, multi-platform support, reward learning, and Cloud.ru AI Factory mapping (--ai-factory flag)",
   "main": "src/cli.js",
   "bin": {

package/templates/.claude/skills/feature-adr/SKILL.md

@@ -363,13 +363,13 @@ to Codex — always ASKING first, always with a Claude fallback (never blocks):
 - **Code (Step 7) + tests/QE (Step 8) FALLBACK** → `args.coder: 'codex-fallback'`, `args.qeReviewer:
   'codex-fallback'`: Claude runs first, and only if the **Claude Code limit is exhausted mid-run** (the
   agent returns null) does the SAME task retry on Codex — so a long build never stalls on a rate limit.
-- **Model choice** → `args.codexModel` (`gpt-5-codex` default · `gpt-5` · `o3` · `auto`).
+- **Model choice** → `args.codexModel` (`auto` default (Codex self-selects) · or an id your account exposes (e.g. `gpt-5.5`)).
 
 *Scenario:* an L/XL run hits the session limit during coding → with `coder: 'codex-fallback'` feature-adr
-logs *"Claude unavailable (limit?) — falling back to Codex gpt-5-codex"* and finishes on Codex, no restart.
+logs *"Claude unavailable (limit?) — falling back to Codex auto"* and finishes on Codex, no restart.
 
 *Example:* `Workflow({ scriptPath: '.claude/workflows/feature-adr.js', args: { slug, description, tier:
-'M', planner: 'codex', coder: 'codex-fallback', qeReviewer: 'codex-fallback', codexModel: 'gpt-5-codex' } })`.
+'M', planner: 'codex', coder: 'codex-fallback', qeReviewer: 'codex-fallback', codexModel: 'auto' } })  // 'auto' = Codex picks top; or pin e.g. 'gpt-5.5'`.
 
 Pre-flight, if Codex is `ready` (`codex-companion setup --json`), the orchestrator asks these three
 before launching; plain `/feature-adr` offers the same at the planning checkpoint. Omit the Codex knobs