litcodex-ai 0.3.20 → 0.3.21

package/README.md

@@ -29,6 +29,9 @@
 npx --yes litcodex-ai install
 ```
 
+Current npm release: `litcodex-ai@0.3.20`. This release deepens bare Hyperplan
+invocation context while keeping `lit start work` as an explicit safe handoff.
+
 This registers the marketplace + plugin and installs the hook into Codex, preserving your existing
 `~/.codex/config.toml` — it backs up before any change and never overwrites unrelated keys. Preview
 the plan first with `npx --yes litcodex-ai --dry-run install`.

package/node_modules/@litcodex/lit-loop/directives/lit-plan.md

@@ -156,13 +156,14 @@ user amends scope, fold it in and re-present the brief. This gate replaces any
 automatic interview-to-plan transition.
 
 # Phase 3 — Generate the plan (only after approval)
-1. **Gap analysis (mandatory):** spawn the `litcodex-metis` agent —
+1. **Gap analysis (mandatory):** when `multi_agent_v1` is exposed, spawn the `litcodex-metis` agent —
    `multi_agent_v1.spawn_agent({"message":"TASK: act as a gap-analysis
    reviewer and review this planning session for gaps. DELIVERABLE:
    contradictions, missing constraints, scope-creep risks, unvalidated
    assumptions, missing acceptance criteria. SCOPE: this planning session.
    VERIFY: each gap names a concrete fix.","fork_context":false})`. Fold the
-   findings in silently.
+   findings in silently. If `multi_agent_v1` is not exposed, do not block; run
+   the same gap analysis directly and record the limitation in the plan evidence.
 2. If native Codex Plan Mode is active, return ONE complete
    `<proposed_plan>...</proposed_plan>` using the template below and do not write
    a file. Otherwise write ONE plan to `.litcodex/plans/<slug>.md`. No
@@ -252,13 +253,17 @@ able to execute every todo from the file alone, with no memory of this
 interview.
 
 # Codex subagent reliability
-Every `multi_agent_v1.spawn_agent` message is self-contained and starts with
+When `multi_agent_v1` is exposed, every `multi_agent_v1.spawn_agent` message is self-contained and starts with
 `TASK: <imperative assignment>`, then names `DELIVERABLE`, `SCOPE`, and
 `VERIFY`. State that it is an executable assignment, not a context handoff. Use
 `fork_context: false` unless full history is truly required; paste only the
 context the child needs. Name any skills the child needs directly inside its
 `message`.
 
+If `multi_agent_v1` is not exposed in the current Codex session, continue with
+direct read-only lanes instead of blocking on missing subagent tools. Record that
+host limitation and preserve the same evidence standard.
+
 Prefer exact installed LitCodex role names when the host accepts `agent_type`:
 `litcodex-explorer`, `litcodex-librarian`, `litcodex-plan`, `litcodex-metis`,
 `litcodex-momus`, and `litcodex-litwork-reviewer`. If the tool exposes no

package/node_modules/@litcodex/lit-loop/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@litcodex/lit-loop",
-	"version": "0.3.20",
+	"version": "0.3.21",
 	"description": "LitCodex Lit-Loop runtime: durable repo-native multi-goal orchestration with embedded success criteria and observable evidence audit.",
 	"type": "module",
 	"bin": {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "litcodex-ai",
-	"version": "0.3.20",
+	"version": "0.3.21",
 	"description": "Codex loop harness installer. Run `npx litcodex-ai install` to set up the LitCodex Codex platform: the bare `lit` hook and the durable lit-loop runtime.",
 	"keywords": ["codex", "litcodex", "lit-loop", "ai-agents", "orchestration"],
 	"author": "LitCodex Authors",
@@ -15,7 +15,7 @@
 	},
 	"files": ["bin", "dist", "model-catalog.json", "README.md", "LICENSE"],
 	"dependencies": {
-		"@litcodex/lit-loop": "0.3.20"
+		"@litcodex/lit-loop": "0.3.21"
 	},
 	"bundledDependencies": ["@litcodex/lit-loop"],
 	"scripts": {