norn-cli 1.10.5 → 1.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.kanbn/index.md +30 -0
- package/.kanbn/tasks/book-first-mentor-session.md +13 -0
- package/.kanbn/tasks/decide-what-success-in-a-pilot-looks-like.md +9 -0
- package/.kanbn/tasks/do-5-customer-conversations.md +9 -0
- package/.kanbn/tasks/finalise-the-one-line-pitch.md +11 -0
- package/.kanbn/tasks/interview-script.md +49 -0
- package/.kanbn/tasks/make-a-list-of-10-people-to-speak-to.md +11 -0
- package/.kanbn/tasks/prepare-your-customer-interview-questions.md +11 -0
- package/.kanbn/tasks/recruit-2/342/200/2233-pilot-users.md +9 -0
- package/.kanbn/tasks/refine-your-pitch.md +9 -0
- package/.kanbn/tasks/write-down-repeated-wording.md +9 -0
- package/.kanbn/tasks/write-the-one-pager.md +27 -0
- package/CHANGELOG.md +34 -0
- package/README.md +75 -1132
- package/dist/cli.js +20855 -3573
- package/package.json +36 -1
- package/schemas/norn.mcp.schema.json +125 -0
- package/scripts/generate-coding-bed.mjs +243 -0
package/.kanbn/index.md
ADDED
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
---
|
|
2
|
+
startedColumns:
|
|
3
|
+
- 'In Progress'
|
|
4
|
+
completedColumns:
|
|
5
|
+
- Done
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Norn
|
|
9
|
+
|
|
10
|
+
## Backlog
|
|
11
|
+
|
|
12
|
+
- [do-5-customer-conversations](tasks/do-5-customer-conversations.md)
|
|
13
|
+
- [write-down-repeated-wording](tasks/write-down-repeated-wording.md)
|
|
14
|
+
- [refine-your-pitch](tasks/refine-your-pitch.md)
|
|
15
|
+
- [recruit-2–3-pilot-users](tasks/recruit-2–3-pilot-users.md)
|
|
16
|
+
- [decide-what-success-in-a-pilot-looks-like](tasks/decide-what-success-in-a-pilot-looks-like.md)
|
|
17
|
+
- [interview-script](tasks/interview-script.md)
|
|
18
|
+
|
|
19
|
+
## Todo
|
|
20
|
+
|
|
21
|
+
- [finalise-the-one-line-pitch](tasks/finalise-the-one-line-pitch.md)
|
|
22
|
+
- [make-a-list-of-10-people-to-speak-to](tasks/make-a-list-of-10-people-to-speak-to.md)
|
|
23
|
+
- [prepare-your-customer-interview-questions](tasks/prepare-your-customer-interview-questions.md)
|
|
24
|
+
|
|
25
|
+
## In Progress
|
|
26
|
+
|
|
27
|
+
## Done
|
|
28
|
+
|
|
29
|
+
- [book-first-mentor-session](tasks/book-first-mentor-session.md)
|
|
30
|
+
- [write-the-one-pager](tasks/write-the-one-pager.md)
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
created: 2026-04-09T22:55:34.350Z
|
|
3
|
+
updated: 2026-04-12T12:19:50.345Z
|
|
4
|
+
assigned: ""
|
|
5
|
+
progress: 0
|
|
6
|
+
tags:
|
|
7
|
+
- 'Week One'
|
|
8
|
+
due: 2026-04-12T00:00:00.000Z
|
|
9
|
+
started: 2026-04-12T09:08:33.269Z
|
|
10
|
+
completed: 2026-04-12T12:19:50.345Z
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
# Book first mentor session
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
---
|
|
2
|
+
created: 2026-04-09T23:25:42.568Z
|
|
3
|
+
updated: 2026-04-09T23:25:42.565Z
|
|
4
|
+
assigned: ""
|
|
5
|
+
progress: 0
|
|
6
|
+
tags: []
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Interview Script
|
|
10
|
+
|
|
11
|
+
This is the important bit. You are not trying to impress them. You are trying to learn where the pain is.
|
|
12
|
+
Opening
|
|
13
|
+
“Thanks for taking the time. I’m working on a VS Code-native API testing and automation tool called Norn. I’m speaking to people to understand how teams currently handle API testing, bug reproduction, and automation. I’m not here to hard-sell you anything — I mainly want to learn how you do things today and where the pain is.”
|
|
14
|
+
Warm-up
|
|
15
|
+
“Can you tell me a bit about your role and how involved you are with API testing or debugging?”
|
|
16
|
+
Current workflow
|
|
17
|
+
“How do you currently test APIs day to day?”
|
|
18
|
+
“What tools do you use for exploratory API work?”
|
|
19
|
+
“What tools do you use for repeatable automated API tests?”
|
|
20
|
+
“Are those the same tools, or different?”
|
|
21
|
+
“Who usually owns API regression coverage in your team?”
|
|
22
|
+
“When there’s a bug, how do developers usually reproduce it?”
|
|
23
|
+
Pain discovery
|
|
24
|
+
“What’s the most annoying part of your current setup?”
|
|
25
|
+
“Where does the process break down?”
|
|
26
|
+
“Do developers and QA use the same tools or mostly different ones?”
|
|
27
|
+
“Have you ever had useful API tests or requests trapped in one place where other people don’t really use them?”
|
|
28
|
+
“What becomes hard to maintain as the project grows?”
|
|
29
|
+
“If you could magically remove one frustration from your API workflow, what would it be?”
|
|
30
|
+
Team and buying context
|
|
31
|
+
“If a new tool genuinely improved this, who would care most?”
|
|
32
|
+
“Who would likely use it first?”
|
|
33
|
+
“Who would need to approve it?”
|
|
34
|
+
“Would this be more of a team decision, an engineering decision, or something individuals would adopt first?”
|
|
35
|
+
Reaction to the concept
|
|
36
|
+
After you’ve listened first, say this:
|
|
37
|
+
“I’m building something that lets developers and QA write readable requests, reusable definitions, environments, assertions, and multi-step sequences directly in VS Code, with the aim of reducing the gap between exploratory work and automation. Based on what you’ve said, what parts of that sound useful and what parts don’t?”
|
|
38
|
+
Then ask:
|
|
39
|
+
“What would make you want to try something like that?”
|
|
40
|
+
“What would make you ignore it?”
|
|
41
|
+
“What would you compare it against immediately?”
|
|
42
|
+
“What would it need to do well before you’d take it seriously?”
|
|
43
|
+
Pilot questions
|
|
44
|
+
“If I gave you access to try this on a real workflow, what would be the best use case to test first?”
|
|
45
|
+
“What would success look like for you in a pilot?”
|
|
46
|
+
“What would need to happen for you to keep using it after the trial?”
|
|
47
|
+
“If it worked well, would you see this as something for just you, or for your wider team?”
|
|
48
|
+
Close
|
|
49
|
+
“This has been really useful. Would you be open to a follow-up once I’ve tightened the product and pilot setup?”
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
---
|
|
2
|
+
created: 2026-04-09T22:56:55.687Z
|
|
3
|
+
updated: 2026-04-09T23:14:25.954Z
|
|
4
|
+
assigned: ""
|
|
5
|
+
progress: 1
|
|
6
|
+
tags:
|
|
7
|
+
- 'Week One'
|
|
8
|
+
due: 2026-04-12T00:00:00.000Z
|
|
9
|
+
completed: 2026-04-10T00:00:00.000Z
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
# Write the one pager
|
|
13
|
+
|
|
14
|
+
Before your first mentor call, write one page with only these headings:
|
|
15
|
+
What Norn is
|
|
16
|
+
Who it is for
|
|
17
|
+
What problem it solves
|
|
18
|
+
What people use today instead
|
|
19
|
+
Why those alternatives are painful
|
|
20
|
+
What is already built
|
|
21
|
+
What proof you have so far
|
|
22
|
+
What you need help deciding next
|
|
23
|
+
|
|
24
|
+
## Comments
|
|
25
|
+
|
|
26
|
+
- date: 2026-04-09T23:11:55.306Z
|
|
27
|
+
https://docs.google.com/document/d/10L0HINdu6bvcKK5FhMBthPHUQYFKo7ix8OBFo-CcodU/edit?usp=sharing
|
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,40 @@ All notable changes to the "Norn" extension will be documented in this file.
|
|
|
4
4
|
|
|
5
5
|
## [Unreleased]
|
|
6
6
|
|
|
7
|
+
## [1.11.0] - 2026-04-19
|
|
8
|
+
|
|
9
|
+
### Added
|
|
10
|
+
- **Deterministic MCP Tools (Extension + CLI)**:
|
|
11
|
+
- Added `norn.mcp.json` project config with nearest-file resolution, stdio and HTTP transports, and shared alias-based runtime behavior.
|
|
12
|
+
- Added `run mcp list <alias>` and `run mcp call <alias> <tool>(name: value)` with variable capture support in both VS Code and the CLI.
|
|
13
|
+
- Added deterministic MCP session reuse per resolved config file plus alias for the lifetime of a sequence run, including nested and imported sequences.
|
|
14
|
+
- Added MCP tool output-schema validation, paginated `tools/list` draining, dedicated CLI/report output, response-panel rendering, and regression fixtures for stdio and HTTP MCP servers.
|
|
15
|
+
|
|
16
|
+
### Improved
|
|
17
|
+
- **Project Setup UX (VS Code)**:
|
|
18
|
+
- Added `Create SQL starter files` and `Create MCP starter config` commands to the Norn sidebar and Explorer folder context menu.
|
|
19
|
+
- Added starter `norn.mcp.json` content with inline `_comment` guidance fields for alias usage, local vs remote servers, and optional config fields.
|
|
20
|
+
- Added MCP-specific response panel styling so MCP steps no longer reuse SQL visuals.
|
|
21
|
+
|
|
22
|
+
### Fixed
|
|
23
|
+
- **Array Count Path Access**:
|
|
24
|
+
- Fixed structured path resolution so array values can be asserted with `.count` consistently across captured variables, response-body paths, and MCP tool lists.
|
|
25
|
+
|
|
26
|
+
### Changed
|
|
27
|
+
- **Website Docs**:
|
|
28
|
+
- Added MCP documentation to the website, including config setup, `run mcp` usage, CLI parity notes, and VS Code project-setup flows.
|
|
29
|
+
|
|
30
|
+
## [1.10.6] - 2026-03-28
|
|
31
|
+
|
|
32
|
+
### Fixed
|
|
33
|
+
- **Structured Variable Storage**:
|
|
34
|
+
- Kept structured runtime values as real objects instead of JSON strings so the debugger, assertions, and path access all see the same types.
|
|
35
|
+
- Preserved compatibility for existing string-backed values when resolving paths.
|
|
36
|
+
|
|
37
|
+
### Changed
|
|
38
|
+
- **Docs**:
|
|
39
|
+
- Updated the advanced website docs to note that structured values stay as objects in memory.
|
|
40
|
+
|
|
7
41
|
## [1.10.5] - 2026-03-28
|
|
8
42
|
|
|
9
43
|
### Improved
|