@medicine-wheel/app 0.6.0 → 0.6.2

package/ALPHA.md

@@ -3,25 +3,28 @@
 **Read this before depending on anything here.**
 
 The Medicine Wheel Developer Suite is under active development and is published
-in the open so the work can be examined, discussed, and improved. It is not
-finished software. Publishing early is deliberate — but so is telling you what
-you are installing.
+in the open so the work can be examined, discussed, and improved. It now
+includes a usable app, CLI, MCP server, and a growing set of composable
+libraries, but its public contracts are not yet stable. Publishing early is
+deliberate — and so is telling you what you are installing.
 
 ## What that means concretely
 
-- **APIs change between patch versions.** All packages move in lockstep, so a
-  bump you would normally read as "nothing changed for me" may still change
-  what you depend on. Pin exact versions.
-- **Packages appear, and their boundaries move.** Three packages were added in
-  `0.5.3`. Where a responsibility lives is still being decided.
+- **APIs can change between patch versions.** Most packages move together while
+  the MCP package keeps its own major version, so a bump you would normally read
+  as "nothing changed for me" may still change what you depend on. Pin exact
+  versions.
+- **Packages appear, and their boundaries move.** The suite has grown beyond
+  its first library packages, and where a responsibility lives is still being
+  refined.
 - **Some packages are intentionally small first cuts.** They express an
   intention with a working minimum rather than a finished surface. Their
   READMEs say so where it applies.
 - **Storage shapes are still settling.** Records written by one version may
   need repair by a later one. Do not treat any store here as an archive of
   record yet.
-- **Test coverage is real but uneven.** 210 tests pass at `0.5.3`; that is a
-  floor, not a claim of completeness.
+- **Automated tests and release checks are in place, but coverage is uneven.**
+  Passing checks are a floor, not a claim of completeness.
 
 ## What it does *not* mean
 

package/README.md

@@ -1,6 +1,6 @@
 # Medicine Wheel
 
-> A first experimental TypeScript framework for relational healing, ceremonial inquiry, and Indigenous-aligned software development — grounded in the Four Directions, Wilson's three R's (Respect, Reciprocity, Responsibility), and OCAP® data sovereignty principles.
+> An experimental TypeScript framework for relational healing, ceremonial inquiry, and Indigenous-aligned software development — grounded in the Four Directions, Wilson's three R's (Respect, Reciprocity, Responsibility), and OCAP® data sovereignty principles.
 
 > [!WARNING]
 > **Experimental alpha.** APIs change between patch versions, packages appear and
@@ -8,29 +8,30 @@
 > open so the work can be examined and improved — pin exact versions, and read
 > [ALPHA.md](./ALPHA.md) before depending on any of it.
 
-## NEWS
+## News
 
-* Full postgres (neon) data provider !
+The suite now includes an interactive app, CLI, MCP server, and PostgreSQL/Neon
+storage alongside its composable libraries.
 
 
 ## Architecture
 
 ```
-medicine-wheel-ontology-core          ← Foundation (types, schemas, RDF vocabulary)
-    ├── medicine-wheel-ceremony-protocol    ← Ceremony state & governance
-    ├── medicine-wheel-fire-keeper          ← Ceremony coordination agent
-    ├── medicine-wheel-community-review     ← Elder review & consensus
-    ├── medicine-wheel-consent-lifecycle    ← Relational consent lifecycle
-    ├── medicine-wheel-narrative-engine     ← Beat sequencing & arc validation
-    ├── medicine-wheel-importance-unit      ← Relational unit of knowledge
-    ├── medicine-wheel-relational-index     ← Four-source epistemic indexing
-    ├── medicine-wheel-transformation-tracker ← Wilson validity tracking
-    ├── medicine-wheel-graph-viz            ← Circular layout & visualization
-    ├── medicine-wheel-relational-query     ← Query, traversal & audit
-    ├── medicine-wheel-prompt-decomposition ← Intent extraction & PDE
-    ├── medicine-wheel-ui-components        ← React components
-    ├── medicine-wheel-data-store           ← Shared Redis data access
-    └── medicine-wheel-session-reader       ← Session event data reader
+@medicine-wheel/ontology-core          ← Foundation (types, schemas, RDF vocabulary)
+    ├── @medicine-wheel/ceremony-protocol    ← Ceremony state & governance
+    ├── @medicine-wheel/fire-keeper          ← Ceremony coordination agent
+    ├── @medicine-wheel/community-review     ← Elder review & consensus
+    ├── @medicine-wheel/consent-lifecycle    ← Relational consent lifecycle
+    ├── @medicine-wheel/narrative-engine     ← Beat sequencing & arc validation
+    ├── @medicine-wheel/importance-unit      ← Relational unit of knowledge
+    ├── @medicine-wheel/relational-index     ← Four-source epistemic indexing
+    ├── @medicine-wheel/transformation-tracker ← Wilson validity tracking
+    ├── @medicine-wheel/graph-viz            ← Circular layout & visualization
+    ├── @medicine-wheel/relational-query     ← Query, traversal & audit
+    ├── @medicine-wheel/prompt-decomposition ← Intent extraction & PDE
+    ├── @medicine-wheel/ui-components        ← React components
+    ├── @medicine-wheel/data-store           ← Shared data access
+    └── @medicine-wheel/session-reader       ← Session event data reader
 
 @medicine-wheel/creative-orientation      ← The question asked before the work
     ├── @medicine-wheel/creative-problem-solving ← Signpost — re-exports the above
@@ -42,7 +43,7 @@ medicine-wheel-ontology-core          ← Foundation (types, schemas, RDF vocabu
 > gap analysis is the right instrument. Named none — you are creating, and
 > structural tension is. `mw orient "<outcome>"` asks it from the command line.
 
-## Methodology: RISE Framework
+## Methodology: [RISE Framework](https://llms.jgwill.com/docs/rise-framework.html)
 
 This project utilizes the **RISE** methodology:
 - **Reverse Engineering**: Deconstructing existing patterns to find relational roots.
@@ -52,125 +53,110 @@ This project utilizes the **RISE** methodology:
 
 ## Packages
 
+The sections below introduce the core building blocks. The root
+[`package.json`](package.json) workspace list is the current inventory of the
+full suite.
+
 ### [@medicine-wheel/ontology-core](src/ontology-core)
 Core ontology layer — 50+ TypeScript types, Zod validation schemas, RDF vocabulary (6 custom namespaces), canonical constants (Ojibwe names, seasons, direction colors), and semantic query helpers (Wilson alignment, OCAP® compliance, relational traversal).
 
-- **Version:** 0.2.0
-- **Dependencies:** `zod` ^3.23.0
+- **Dependencies:** `zod`
 
 ### [@medicine-wheel/ceremony-protocol](src/ceremony-protocol)
 Ceremony lifecycle protocol — manages ceremony state, four-phase transitions (opening → council → integration → closure), governance enforcement for protected paths, and ceremony-required change detection.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`
+- **Dependencies:** `@medicine-wheel/ontology-core`
 
 ### [@medicine-wheel/fire-keeper](src/fire-keeper)
 Fire Keeper coordination agent — tends the ceremony fire, ensures relational integrity through gating conditions, permission tier escalation, and maintains Wilson alignment as an active agent that evaluates, gates, routes, and escalates.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`, `medicine-wheel-ceremony-protocol`
+- **Dependencies:** `@medicine-wheel/ontology-core`, `@medicine-wheel/ceremony-protocol`
 
 ### [@medicine-wheel/community-review](src/community-review)
 Community-based ceremonial review protocol — implements Wilson's validation through Elder review circles, consensus-seeking, talking circle protocol, and relational accountability assessment.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`, `medicine-wheel-ceremony-protocol`, `zod`
+- **Dependencies:** `@medicine-wheel/ontology-core`, `@medicine-wheel/ceremony-protocol`, `zod`
 
 ### [@medicine-wheel/consent-lifecycle](src/consent-lifecycle)
 Ongoing relational consent lifecycle — consent as a living relational obligation with lifecycle tracking, renewal, renegotiation, withdrawal cascades, and community-level consent protocols.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`, `medicine-wheel-ceremony-protocol`, `zod`
+- **Dependencies:** `@medicine-wheel/ontology-core`, `@medicine-wheel/ceremony-protocol`, `zod`
 
 ### [@medicine-wheel/narrative-engine](src/narrative-engine)
 Beat sequencing, cadence validation, arc completeness scoring, timeline building, cycle orchestration, and RSIS narrative generators. Tracks four-directional balance and ceremony coverage.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`
+- **Dependencies:** `@medicine-wheel/ontology-core`
 
 ### [@medicine-wheel/importance-unit](src/importance-unit)
 ImportanceUnit — the relational unit of knowledge in Wilson's epistemology. Carries epistemic weight, source dimensions (Land/Dream/Code/Vision), circle depth tracking, and accountability links. Dream-state knowledge starts at 0.85+ weight; rational-filtered inputs start lower.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`, `zod`
+- **Dependencies:** `@medicine-wheel/ontology-core`, `zod`
 
 ### [@medicine-wheel/relational-index](src/relational-index)
 Four-source epistemic dimensional indexing — Land, Dream, Code, Vision traversal with cross-dimensional mapping, convergence/tension detection, and spiral depth metrics.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`
+- **Dependencies:** `@medicine-wheel/ontology-core`
 
 ### [@medicine-wheel/transformation-tracker](src/transformation-tracker)
 Research transformation tracking — Wilson validity criterion: "If research doesn't change you, you haven't done it right." Tracks researcher growth, community impact, relational shifts, reciprocity balance, and seven-generation sustainability.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`, `medicine-wheel-ceremony-protocol`, `zod`
+- **Dependencies:** `@medicine-wheel/ontology-core`, `@medicine-wheel/ceremony-protocol`, `zod`
 
 ### [@medicine-wheel/graph-viz](src/graph-viz)
 Medicine Wheel circular graph visualization — four-direction node positioning, ceremony-aware edges, OCAP® indicators, SVG path generation, data converters, and RSIS visualization utilities (kinship graphs, reciprocity flows, Mermaid export).
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`
-- **Peer:** `react` >=18.0.0
+- **Dependencies:** `@medicine-wheel/ontology-core`
+- **Peer:** `react`
 
 ### [@medicine-wheel/relational-query](src/relational-query)
 Query builder for relational webs — node/edge filtering, ceremony-bounded BFS traversal, OCAP®-compliant path walking, accountability auditing, shortest path, neighborhood discovery, and KuzuDB Cypher query builders.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`
+- **Dependencies:** `@medicine-wheel/ontology-core`
 
 ### [@medicine-wheel/prompt-decomposition](src/prompt-decomposition)
 Ontology-enriched prompt decomposition — Four Directions classification, implicit intent extraction from hedging language, dependency mapping, ceremony guidance, action stacking, and narrative beat generation.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`
+- **Dependencies:** `@medicine-wheel/ontology-core`
 
 ### [@medicine-wheel/ui-components](src/ui-components)
 React UI component library — `DirectionCard`, `BeatTimeline`, `NodeInspector`, `OcapBadge`, `WilsonMeter`. All components use ontology-core types for type-safe, culturally grounded interfaces.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`
-- **Peer:** `react` ^18.0.0 || ^19.0.0
+- **Dependencies:** `@medicine-wheel/ontology-core`
+- **Peer:** `react`
 
 ### [@medicine-wheel/data-store](src/data-store)
 Shared Redis data-access layer — connection management (Upstash, Vercel KV, local), Node/Edge/Ceremony/Accountability CRUD, session-ceremony linking, and generic Redis helpers.
 
-- **Version:** 0.2.0
-- **Dependencies:** `medicine-wheel-ontology-core`, `redis`
+- **Dependencies:** `@medicine-wheel/ontology-core`, `redis`
 
 ### [@medicine-wheel/session-reader](src/session-reader)
 Session event reader — JSONL parsing, session summaries, analytics extraction, and search across agent session data. Zero external dependencies.
 
-- **Version:** 0.2.0
 - **Dependencies:** None (Node.js built-ins only)
 
 ### [@medicine-wheel/creative-orientation](src/creative-orientation)
 The orientation question, asked before the work: *is there a prior state you are restoring?* Yes — this is a fire, route to gap analysis. No — you are creating, route to structural tension. Reads the claim the caller supplies; advises where phrasing and situation disagree, and never refuses.
 
-- **Version:** 0.5.3
 - **Dependencies:** None (Node.js built-ins only)
 
 ### [@medicine-wheel/creative-problem-solving](src/creative-problem-solving)
 Signpost package — re-exports `@medicine-wheel/creative-orientation` and adds `THE_QUESTION`. Holds no logic of its own. It exists because "creative problem solving" is the name people look for, and a signpost carrying the traveller's name is how they find the door.
 
-- **Version:** 0.5.3
 - **Dependencies:** `@medicine-wheel/creative-orientation`
 
 ### [@medicine-wheel/gap-analysis](src/gap-analysis)
 Problem-solving built properly for when something worked and stopped — evidenced baseline, observation, difference, verifiable elimination steps. Root cause, incidents, regressions, troubleshooting. The baseline requirement is what separates a fire from a creating act.
 
-- **Version:** 0.5.3
 - **Dependencies:** `@medicine-wheel/creative-orientation`
 
 ### [@medicine-wheel/brainstorming](src/brainstorming)
 Idea into committed design through approval gates a human holds — `explore → clarify → approaches → design → spec → review → plan`. Every outcome it emits, including its own multiple-choice questions, passes the orientation question before it is spoken.
 
-- **Version:** 0.5.3
 - **Dependencies:** `@medicine-wheel/creative-orientation`
 
 ## Specifications
 
-RISE framework specifications for all 15 packages are in [`rispecs/`](rispecs/). Start with [`medicine-wheel.spec.md`](rispecs/medicine-wheel.spec.md) for the system overview.
+RISE framework specifications are in [`rispecs/`](rispecs/). Start with [`medicine-wheel.spec.md`](rispecs/medicine-wheel.spec.md) for the system overview.
 
 | Package | Spec |
 |---------|------|
@@ -233,11 +219,9 @@ mw directions
 mw node list
 ```
 
-The published app package installs and runs without `@medicine-wheel/mcp`. The `mw`
-CLI uses HTTP against the running server by default; MCP fallback is optional via a
-local `MW_MCP_PATH`.
+The `mw` CLI uses HTTP against the running server by default; MCP fallback is
+available via a local `MW_MCP_PATH`.
 
 ## License
 
 MIT  see [LICENSE](LICENSE)
-

package/app/api/health/route.ts

@@ -7,16 +7,24 @@ export async function GET() {
   try {
     const store = await createProvider();
     
-    // Test basic connectivity
-    const nodes = await store.getAllNodes();
-    const ceremonies = await store.getAllCeremonies();
-    
+    // Test basic connectivity — and answer about the whole store, not a page of
+    // it. `getAllNodes()` / `getAllCeremonies()` default to 100, the same
+    // default `app/api/nodes/route.ts` keeps on purpose for an unfiltered read;
+    // measuring their result reported `min(actual, 100)` under the name
+    // `counts`. That made health agree with any truncated collection response a
+    // caller was using it to check, which is the one thing this endpoint exists
+    // to contradict.
+    const [nodes, ceremonies] = await Promise.all([
+      store.countNodes(),
+      store.countCeremonies(),
+    ]);
+
     return NextResponse.json({
       status: 'healthy',
       provider: providerType,
       counts: {
-        nodes: nodes.length,
-        ceremonies: ceremonies.length,
+        nodes,
+        ceremonies,
       },
       env: {
         MW_STORAGE_PROVIDER: process.env.MW_STORAGE_PROVIDER || 'not set',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@medicine-wheel/app",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "Medicine Wheel — Interactive visual layer for Indigenous relational research with Four Directions, ceremonies, and narrative arcs",
   "bin": {
     "mw": "dist/cli/mw.js",
@@ -85,29 +85,29 @@
     "release:major": "npm run version:major && npm run publish:all && npm run release:commit"
   },
   "dependencies": {
-    "@medicine-wheel/ceremonial-diary": "^0.6.0",
-    "@medicine-wheel/ceremony-protocol": "^0.6.0",
-    "@medicine-wheel/community-review": "^0.6.0",
-    "@medicine-wheel/consent-lifecycle": "^0.6.0",
-    "@medicine-wheel/creative-orientation": "^0.6.0",
-    "@medicine-wheel/data-store": "^0.6.0",
-    "@medicine-wheel/data-store-postgres": "^0.6.0",
-    "@medicine-wheel/fire-keeper": "^0.6.0",
-    "@medicine-wheel/github-ceremony": "^0.6.0",
-    "@medicine-wheel/graph-viz": "^0.6.0",
-    "@medicine-wheel/importance-unit": "^0.6.0",
-    "@medicine-wheel/mcp": "^4.6.0",
-    "@medicine-wheel/narrative-cluster": "^0.6.0",
-    "@medicine-wheel/narrative-engine": "^0.6.0",
-    "@medicine-wheel/ontology-core": "^0.6.0",
-    "@medicine-wheel/perception-layer": "^0.6.0",
-    "@medicine-wheel/prompt-decomposition": "^0.6.0",
-    "@medicine-wheel/relational-index": "^0.6.0",
-    "@medicine-wheel/relational-query": "^0.6.0",
-    "@medicine-wheel/session-reader": "^0.6.0",
-    "@medicine-wheel/storage-provider": "^0.6.0",
-    "@medicine-wheel/transformation-tracker": "^0.6.0",
-    "@medicine-wheel/ui-components": "^0.6.0",
+    "@medicine-wheel/ceremonial-diary": "^0.6.2",
+    "@medicine-wheel/ceremony-protocol": "^0.6.2",
+    "@medicine-wheel/community-review": "^0.6.2",
+    "@medicine-wheel/consent-lifecycle": "^0.6.2",
+    "@medicine-wheel/creative-orientation": "^0.6.2",
+    "@medicine-wheel/data-store": "^0.6.2",
+    "@medicine-wheel/data-store-postgres": "^0.6.2",
+    "@medicine-wheel/fire-keeper": "^0.6.2",
+    "@medicine-wheel/github-ceremony": "^0.6.2",
+    "@medicine-wheel/graph-viz": "^0.6.2",
+    "@medicine-wheel/importance-unit": "^0.6.2",
+    "@medicine-wheel/mcp": "^4.6.2",
+    "@medicine-wheel/narrative-cluster": "^0.6.2",
+    "@medicine-wheel/narrative-engine": "^0.6.2",
+    "@medicine-wheel/ontology-core": "^0.6.2",
+    "@medicine-wheel/perception-layer": "^0.6.2",
+    "@medicine-wheel/prompt-decomposition": "^0.6.2",
+    "@medicine-wheel/relational-index": "^0.6.2",
+    "@medicine-wheel/relational-query": "^0.6.2",
+    "@medicine-wheel/session-reader": "^0.6.2",
+    "@medicine-wheel/storage-provider": "^0.6.2",
+    "@medicine-wheel/transformation-tracker": "^0.6.2",
+    "@medicine-wheel/ui-components": "^0.6.2",
     "@neondatabase/serverless": "^0.10.0",
     "@xyflow/react": "^12.3.0",
     "clsx": "^2.1.1",