norn-cli 4.3.2 → 4.5.0

package/README.md

@@ -27,7 +27,7 @@ That means you can:
 - `.nornenv` files for environments and secrets
 - `.nornapi` files for reusable endpoint definitions
 - `.nornsql` files for database queries and commands
-- `.nornagent` files for contract-checked AI agents and model-directed delegation
+- `.nornai` or `.nornagent` files for contract-checked AI agents and model-directed delegation
 - 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
@@ -140,7 +140,7 @@ Norn can call MCP tools from sequences without leaving the `.norn` runtime. MCP
 
 A server can be declared in two places, and an alias resolves through them in this order:
 
-1. an `mcp <Alias> ... end mcp` block in a `.nornagent` sidecar the file imports — see
+1. an `mcp <Alias> ... end mcp` block in a `.nornai` sidecar the file imports — see
    [Contract-Checked Agent Graphs](#contract-checked-agent-graphs), and prefer this when agents
    use the server too, because the file then says what it connects to;
 2. `mcp.servers` in the nearest `norn.config.json`.
@@ -194,7 +194,7 @@ Behavior:
 
 ## Contract-Checked Agent Graphs
 
-Define agents in an imported `.nornagent` sidecar. An agent can grant another
+Define agents in an imported `.nornai` or `.nornagent` sidecar. Both extensions use the same syntax and behavior. An agent can grant another
 agent through `agents`; the callee then appears to the calling model as an
 ordinary tool. Its `accepts` schema constrains and validates the generated tool
 input, and its `returns` schema validates the result before it travels back up
@@ -277,7 +277,7 @@ Deterministic `run mcp` steps resolve the same aliases, so a server can be prove
 with no model and no cost:
 
 ```norn
-import "./agents.nornagent"
+import "./agents.nornai"
 
 test sequence ServersUp
     var tools = run mcp list House
@@ -290,7 +290,7 @@ shape end to end: a browser agent, a backend agent narrowed on the same custom s
 reporter, and a `judge` over the expected test cases.
 
 A prompt that outgrows its sidecar can live in its own file instead. `describe`
-and `system` both accept `file <path>`, resolved relative to the `.nornagent`
+and `system` both accept `file <path>`, resolved relative to the agent sidecar
 file just like an import:
 
 ```nornagent
@@ -309,7 +309,7 @@ Run the graph from an ordinary sequence; the same nested contract and retry
 trace appears in VS Code and the CLI:
 
 ```norn
-import "./agents.nornagent"
+import "./agents.nornai"
 
 test sequence RouteTicket
     var ticket = run readJson "./ticket.json"
@@ -370,7 +370,7 @@ fixture. `--from` accepts a unique agent name or canonical path such as
 onward runs live against the current graph.
 
 **Norn: Show Agent Graph**, or the CodeLens on any agent block, draws the graph
-for a `.nornagent` file: who calls whom, the `accepts`/`returns` contract on each
+for an agent sidecar: who calls whom, the `accepts`/`returns` contract on each
 boundary, and how each one turned out. Hover an agent or a boundary for the full
 detail — models, timings, usage, prompts, payloads, contract issues.