norn-cli 2.9.7 → 2.9.8

package/NOW.md

@@ -0,0 +1,58 @@
+# NOW — Active Work Board
+
+> **The single source of truth for what we are working on _right now_** — for Peter and
+> for every AI agent (Claude, Codex, Copilot, Cursor, any). Deliberately tool-agnostic:
+> it lives here in the repo, **not** in any one assistant's memory or private notes.
+>
+> We have a lot of planning docs; this board exists so nobody (human or AI) has to guess
+> what's current. If it's on this board, it's the work. If it's not, it isn't — yet.
+
+## How this board works
+
+- **Empty by default.** Nothing is "current" unless it has been explicitly **Accepted**
+  onto this board by Peter. An empty "Active now" means: no directed work in flight —
+  don't start big work off a backlog/plan doc without Peter accepting it here first.
+- **Accepting work:** Peter says "Accept X" (or moves it here). That's the signal it
+  becomes current. Until then, ideas live in the plan/backlog docs, not here.
+- **This board is an _index_, not the detail.** Each item is one or two lines + a link to
+  its real plan doc. Keep the detail in the linked doc; keep this page short and scannable.
+- **Finishing work:** when an item is done, move it to "Recently done" (keep the last
+  handful), then prune. Don't let this page grow.
+- **Agents:** treat items under "Active now" as the current priority order. Do these
+  before picking up anything from the wider `Docs/` set.
+
+---
+
+## Active now
+
+_Accepted 2026-07-03. Two workstreams: build the paid direction, and market it._
+
+### 1. 🔨 Contract & Drift — BUILD (anchor)
+Turn Norn's existing `matchesSchema` into the job the market will pay for: **catch
+breaking API changes on the PR.** Do **Stage 1 → Stage 2 first** (cheap, pure reuse);
+Stage 3 (drift-as-PR-verdict) is the sellable milestone; Stage 4 is fenced off until a
+Stage-3 buyer pays.
+→ Plan: [`Docs/contract_drift_build_plan.md`](Docs/contract_drift_build_plan.md) · Evidence: `Docs/market_signals.md` Signal 004
+**Next step:** build a thin Stage 1 slice, then Peter QA-dogfoods it.
+
+### 2. 📣 Marketing & positioning — Voiden playbook (message + distribution together)
+Sharpen the pitch **and** get it into dev-native rooms — one workstream. Channel
+correction after the LinkedIn flop: copy Voiden's **distribution, not their business
+model**. Phased do → prove → gate: sharpen the drift hook → publish migration essays on
+**dev.to / Reddit / Show HN** (does content travel?) → comparison pages + directories →
+launch on the Stage-3 drift demo → community/open-core (earned, last).
+→ Plan: [`Docs/marketing_plan.md`](Docs/marketing_plan.md) · Evidence: `Docs/market_signals.md` Signal 004 · [[norn-reddit-disclosed-selling]] · spine stays locked ([[norn-messaging-locked]])
+**Next step:** Phase 0 — write the one-paragraph "why Norn, now" hook (the field-rename-caught-on-the-PR story) + 3 headline angles.
+
+---
+
+## Backlog / accepted-but-not-started
+
+_(empty)_
+
+## Recently done
+
+_(empty)_
+
+---
+_Last updated: 2026-07-03_

package/README.md

@@ -1,6 +1,6 @@
 # Norn
 
-Norn keeps API tests, database checks, and Kubernetes runbooks in repeatable, version-controlled files your whole team can trust. Author, inspect, and debug them in VS Code, then run the same files from the CLI and CI.
+Norn keeps API tests and database checks in repeatable, version-controlled files your whole team can trust. Author, inspect, and debug them in VS Code, then run the same files from the CLI and CI.
 
 ### Simple API Requests
 
@@ -27,7 +27,6 @@ That means you can:
 - `.nornenv` files for environments and secrets
 - `.nornapi` files for reusable endpoint definitions
 - `.nornsql` files for database queries and commands
-- `.nornk8s` files for Kubernetes commands and runbooks
 - syntax highlighting, IntelliSense, and diagnostics
 - response inspection, JSON diffing, and click-to-generate assertions
 - tagged and parameterized test execution in VS Code and the CLI
@@ -64,7 +63,6 @@ Use Norn to:
 - run a whole sequence from the editor
 - debug a sequence with breakpoints
 - run test sequences from the Testing view
-- inspect live Kubernetes pods and logs from `.nornk8s` files
 
 ## In The CLI
 
@@ -73,35 +71,8 @@ The CLI uses the same execution model as the extension, so local runs and CI run
 ```bash
 npm install -g norn-cli
 norn ./tests/smoke.norn -e dev
-norn ./runbooks/triage.nornk8s --context prelive
 ```
 
-## Kubernetes Runbooks
-
-`.nornk8s` files turn common kubectl triage commands into reusable runbooks. Standalone
-`get pods`, `describe pod`, and `logs` commands open styled VS Code views with live pod
-and log updates. Helper sequences run explicitly, while `runbook sequence` blocks are
-automatic CLI entry points.
-
-```nornk8s
-namespace {{ordersNs}}
-
-get pods
-logs orders-api-7d9f --tail 500
-
-sequence RestartOrders
-    restart deployment/orders-api
-end sequence
-
-runbook sequence ClusterCheck
-    get pods
-    get pods -n kube-system
-end sequence
-```
-
-Select a Kubernetes context from the VS Code context lens or pass `--context` to the
-CLI. Restart commands require a VS Code confirmation or CLI `--yes`.
-
 ## `.nornenv` Templates And Extends
 
 Use `[template:name]` sections for reusable environment building blocks, then compose selectable `[env:name]` sections with `extends`. Only templates can be extended. Templates are not selectable from the VS Code environment picker or CLI; only `[env:...]` names can be used with `-e`.
@@ -186,7 +157,6 @@ Behavior:
 - QA and automation work that needs readable test flows
 - regression and smoke suites that should run the same way locally and in CI
 - projects that want API requests and API tests to live next to the code
-- teams that want repeatable Kubernetes triage runbooks beside their services
 
 Diff preview test line.
 

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "norn-cli",
   "displayName": "Norn",
-  "description": "Version-controlled API, database, and Kubernetes tests and runbooks. Author in VS Code, then run the same files from the CLI and CI.",
-  "version": "2.9.7",
+  "description": "Version-controlled API and database tests. Author in VS Code, then run the same files from the CLI and CI.",
+  "version": "2.9.8",
   "publisher": "Norn-PeterKrustanov",
   "author": {
     "name": "Peter Krastanov"
@@ -29,10 +29,7 @@
     "api automation",
     "openapi",
     "http",
-    "test automation",
-    "kubernetes",
-    "kubectl",
-    "runbooks"
+    "test automation"
   ],
   "engines": {
     "vscode": "^1.108.1"
@@ -219,6 +216,20 @@
       ]
     },
     "menus": {
+      "commandPalette": [
+        {
+          "command": "norn.k8s.runLine",
+          "when": "false"
+        },
+        {
+          "command": "norn.k8s.runSequence",
+          "when": "false"
+        },
+        {
+          "command": "norn.k8s.selectContext",
+          "when": "false"
+        }
+      ],
       "explorer/context": [
         {
           "command": "norn.createStarterCatalog",
@@ -435,7 +446,7 @@
         "id": "norn.chat",
         "name": "norn",
         "fullName": "Norn",
-        "description": "Ask questions about Norn syntax, generate requests and runbooks, explain sequences, and convert cURL/HTTP to Norn",
+        "description": "Ask questions about Norn syntax, generate requests, explain sequences, and convert cURL/HTTP to Norn",
         "isSticky": true,
         "commands": [
           {