@haaaiawd/loom 2.1.0 → 2.1.2

package/docs/PROMPT_CATALOG.md

@@ -12,29 +12,29 @@ order as JSON, so documentation cannot quietly describe a different prompt from
 
 ## Instruction layers
 
-| Layer | Message | Injected when | Purpose |
-|---|---|---|---|
-| Stable core | `layers.stable_core` | Every `loom context` | Durable collaboration judgment: user ownership, evidence classes, question threshold, corrections, reversible delegation |
-| Environment adaptation | `layers.environment_adaptation_available` or `layers.environment_adaptation_unavailable` | Every `loom context` | States whether a human can answer; routes uncertainty through inspection, permitted factual research, clarification, bounded assumption, or block |
-| Runtime adaptation | `layers.runtime_protocol` | Every `loom context` | LOOM-specific disk model, document graph, capability boundaries, Work Map, and three production loops |
-| Project state | `layers.project_state` | Every `loom context` | Dynamic status, uncertainty, assumptions, document/capability inventory, Task counts, and Keeper feedback |
-| Execution protocol | `layers.execution_protocol` | Active Task or `--task` | Recovery, workspace inspection, risk-based testing, progress persistence, exact proof, and delivery boundaries |
-| Current task | `layers.current_task` | Active Task or `--task` | Exact Task JSON followed by the exact contents of every path in `reads` |
+| Layer | Message | Injected when | Purpose |
+|---|---|---|---|
+| Stable core | `layers.stable_core` | Every `loom context` | Durable collaboration judgment: user ownership, evidence classes, question threshold, corrections, reversible delegation |
+| Environment adaptation | `layers.environment_adaptation_available` or `layers.environment_adaptation_unavailable` | Every `loom context` | States whether a human can answer; routes uncertainty through inspection, permitted factual research, clarification, bounded assumption, or block |
+| Runtime adaptation | `layers.runtime_protocol` | Every `loom context` | LOOM-specific disk model, document graph, capability boundaries, Work Map, and three production loops |
+| Project state | `layers.project_state` | Every `loom context` | Dynamic status, uncertainty, assumptions, document/capability inventory, Task counts, and Keeper feedback |
+| Execution protocol | `layers.execution_protocol` | Active Task or `--task` | Recovery, workspace inspection, risk-based testing, progress persistence, exact proof, and delivery boundaries |
+| Current task | `layers.current_task` | Active Task or `--task` | Exact Task JSON followed by the exact contents of every path in `reads` |
 
 This separation is deliberate. Project-specific expertise does not inflate the stable prompt; it lives in
-field dossiers. One-off Task instructions do not become global doctrine. Host permissions and tools are not
-claimed by prompt text.
-
-When the human channel is unavailable, the environment message explicitly forbids fabricated user interaction and
-forbids treating web research as a substitute for user intent, preference, or authority. It preserves factual
-research when the task and host actually permit it, then requires a reversible assumption or block for what cannot
-be learned.
+field dossiers. One-off Task instructions do not become global doctrine. Host permissions and tools are not
+claimed by prompt text.
+
+When the human channel is unavailable, the environment message explicitly forbids fabricated user interaction and
+forbids treating web research as a substitute for user intent, preference, or authority. It preserves factual
+research when the task and host actually permit it, then requires a reversible assumption or block for what cannot
+be learned.
 
 ## Workspace and document messages
 
-`workspace_anchor` is the short block added to `AGENTS.md`. It tells an entering or reset Agent to run
-`loom context`, rerun it before editing after an interruption, persist state at meaningful boundaries rather
-than before every tool call, and keep CLI operation invisible to the human.
+`workspace_anchor` is the short block added to `AGENTS.md`. It tells an entering or reset Agent to run
+`loom context`, rerun it before editing after an interruption, persist state at meaningful boundaries rather
+than before every tool call, and keep CLI operation invisible to the human.
 
 `templates.project_index` creates `.loom/PROJECT.md` as a concise whole and document map. It explicitly
 prevents a large project's systems from being compressed into one file.
@@ -77,12 +77,12 @@ new digest, and another fresh Keeper.
 `evaluation.baseline_condition` gives a normal capable Agent the identical brief and ordinary tools without
 LOOM. It does not weaken the baseline or prohibit normal planning.
 
-`evaluation.loom_condition` gives the same brief, model class, tools, workspace facts, and budget, adding only
-LOOM continuity infrastructure and no extra authority.
-
-`evaluation.unattended_baseline_condition` and `evaluation.unattended_loom_condition` are the same two
-conditions when no user response channel exists. The environment fact is equal in both arms; only the LOOM arm
-uses `loom context --human-channel unavailable`.
+`evaluation.loom_condition` gives the same brief, model class, tools, workspace facts, and budget, adding only
+LOOM continuity infrastructure and no extra authority.
+
+`evaluation.unattended_baseline_condition` and `evaluation.unattended_loom_condition` are the same two
+conditions when no user response channel exists. The environment fact is equal in both arms; only the LOOM arm
+uses `loom context --human-channel unavailable`.
 
 `evaluation.blind_judge` scores anonymized output on intent fidelity, question value, whole coverage,
 professional depth, buildability, reset continuity, implementation evidence, human burden, and cost. It
@@ -92,13 +92,13 @@ penalizes ceremony and runs an order swap.
 
 `composition.normal_resume`, `composition.active_task`, and `composition.keeper_handoff` list the exact block
 order. Keeper receives every design and capability document; a normal active Task receives only its declared
-reads. This difference is intentional: Keeper audits whole-project coverage, while delivery protects context
-focus.
-
-The active Task composition adds `execution_protocol` between the recovered project whole and the exact Task.
-It requires inspection of current workspace/version-control reality, risk-appropriate tests, restartable
-progress, and criterion-level proof. It does not force a unit test for non-code claims or a branch/PR for every
-Task; those are selected when the behavior, human request, or repository workflow makes them meaningful.
+reads. This difference is intentional: Keeper audits whole-project coverage, while delivery protects context
+focus.
+
+The active Task composition adds `execution_protocol` between the recovered project whole and the exact Task.
+It requires inspection of current workspace/version-control reality, risk-appropriate tests, restartable
+progress, and criterion-level proof. It does not force a unit test for non-code claims or a branch/PR for every
+Task; those are selected when the behavior, human request, or repository workflow makes them meaningful.
 
 ## CLI operational messages
 

package/docs/RELEASE_CHECKLIST.md

@@ -31,9 +31,9 @@ already exist in the registry.
 ## 3. Publish deliberately
 
 ```bash
-git tag v2.0.1
+git tag v2.0.1
 git push origin HEAD
-git push origin v2.0.1
+git push origin v2.0.1
 npm publish --access public
 ```
 
@@ -46,7 +46,7 @@ In a clean temporary directory:
 
 ```bash
 npm view @haaaiawd/loom version
-npx @haaaiawd/loom@2.0.1 --version
+npx @haaaiawd/loom@2.0.1 --version
 ```
 
 Then open the GitHub README and npm package page to confirm the SVG header, diagrams, links, and changelog

package/docs/UX_FLOW.md

@@ -56,17 +56,17 @@ details that do not affect the current whole, or framework questions whose only
 | `I don't know` | Research or decide when safe; ask again only if the human owns the missing preference or authority |
 | `Skip questions and continue` | Name the concrete quality or risk loss, record skipped uncertainty, then proceed |
 
-After every answer round, the Agent re-evaluates the whole. If material uncertainty remains, it loops to another adaptive
-round. If only reversible local uncertainty remains, it continues.
-
-### When no human response channel exists
-
-Some unattended, sandboxed, or benchmark runs have no human to answer. The host invokes
-`loom context --human-channel unavailable`; this does not create a synthetic user. The Agent first inspects
-discoverable workspace facts and permitted tools, researches only objective external facts when the task permits it,
-and never treats web research as a substitute for user intent, preference, or authority. It records a bounded
-assumption and selects a safe reversible action, or blocks if the missing answer controls irreversible, high-risk,
-or materially costly work.
+After every answer round, the Agent re-evaluates the whole. If material uncertainty remains, it loops to another adaptive
+round. If only reversible local uncertainty remains, it continues.
+
+### When no human response channel exists
+
+Some unattended, sandboxed, or benchmark runs have no human to answer. The host invokes
+`loom context --human-channel unavailable`; this does not create a synthetic user. The Agent first inspects
+discoverable workspace facts and permitted tools, researches only objective external facts when the task permits it,
+and never treats web research as a substitute for user intent, preference, or authority. It records a bounded
+assumption and selects a safe reversible action, or blocks if the missing answer controls irreversible, high-risk,
+or materially costly work.
 
 ## 3. Build project-specific capability
 
@@ -172,13 +172,13 @@ human authority govern later changes.
 
 ## Primary evaluation question
 
-The causal baseline is a normal capable Agent with no LOOM—not LOOM v1. Both conditions receive the same raw brief, model,
-tools, workspace, human-channel availability, user oracle when one exists, budget, and reset schedule. LOOM v1 may be added as a secondary regression condition, but it does
-not answer whether the framework itself creates value over no framework.
-
-For an unattended external benchmark, both conditions receive `human_channel: unavailable` and no fabricated user
-oracle. A fresh LOOM sidecar sits outside the scored workspace and is passed through `--state-dir` on every LOOM
-command, so framework state cannot alter task files or hidden-test behavior.
+The causal baseline is a normal capable Agent with no LOOM—not LOOM v1. Both conditions receive the same raw brief, model,
+tools, workspace, human-channel availability, user oracle when one exists, budget, and reset schedule. LOOM v1 may be added as a secondary regression condition, but it does
+not answer whether the framework itself creates value over no framework.
+
+For an unattended external benchmark, both conditions receive `human_channel: unavailable` and no fabricated user
+oracle. A fresh LOOM sidecar sits outside the scored workspace and is passed through `--state-dir` on every LOOM
+command, so framework state cannot alter task files or hidden-test behavior.
 
 The anonymization harness must preserve runnable relative layout, record a file/digest manifest, and rerun each condition's
 declared tests and smoke command before judging. Packet-construction failures are eval failures, never evidence against a run.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@haaaiawd/loom",
-  "version": "2.1.0",
-  "description": "LOOM — invisible project understanding and continuity infrastructure for AI agents",
+  "version": "2.1.2",
+  "description": "LOOM — Spec-driven continuity, proof, and project understanding infrastructure for AI coding agents",
   "type": "module",
   "bin": {
     "loom": "cli/bin/loom.js"
@@ -33,11 +33,15 @@
   },
   "keywords": [
     "loom",
-    "agent",
+    "spec-driven",
+    "ai-agent",
+    "ai-coding",
     "continuity",
     "project-understanding",
-    "task-context",
-    "cli"
+    "agent-framework",
+    "context-management",
+    "task-tracking",
+    "llm"
   ],
   "license": "MIT",
   "repository": {