Skip to content

feat(nkb): adoption stats CLI#17

Merged
wranngle merged 3 commits into
mainfrom
feat/r2-nkb-stats
May 19, 2026
Merged

feat(nkb): adoption stats CLI#17
wranngle merged 3 commits into
mainfrom
feat/r2-nkb-stats

Conversation

@wranngle
Copy link
Copy Markdown
Owner

Summary

Adds scripts/nkb-stats.mjs — a small CLI that reads a JSONL telemetry
stream (default fixtures/telemetry-sample.jsonl) and prints the top-N
knowledge-base patterns by view count. Default top-10, supports
--input, --top, and --format text|json.

Output is deterministic: ranked by count descending with an alphabetical
tie-break on the pattern slug, so test assertions can pin row order even
when two patterns share a count. Malformed JSON lines and records without
a pattern field are skipped into a skipped meta counter rather than
aborting the run.

Round-2 features in this PR queue collectively give the knowledge base a
write path (#13 submit), a machine-readable export (#14 jsonld), a dedupe
gate (#15), a try-before-you-merge sandbox (#16), and now a read-out of
which patterns are actually getting used.

Proof

Running the CLI against the bundled fixture:

$ node scripts/nkb-stats.mjs
# nkb adoption stats — top 10 of 12 patterns
# events tallied: 58

 1. 10  slack-retry-storm
 2.  9  http-retry-idempotency
 3.  8  webhook-dedup-key
 4.  7  voice-agent-elevenlabs-patterns
 5.  6  stripe-idempotency-key
 6.  5  airtable-rate-limit-backoff
 7.  4  queue-backpressure-fanout
 8.  3  error-monitoring-fanout
 9.  2  google-sheets-batched-append
10.  2  shopify-orders-webhook

tests/stats.bats (8 cases, all green locally):

$ bats tests/stats.bats
1..8
ok 1 stats: top-10 ordering matches highest-count patterns from telemetry fixture
ok 2 stats: rank 1 is the pattern with the most events (slack-retry-storm @ 10)
ok 3 stats: exactly 10 ranked rows when --top 10 with 12 distinct patterns
ok 4 stats: ties at count=2 break alphabetically (google-sheets... before shopify-...)
ok 5 stats: header reports total events tallied (58 in fixture)
ok 6 stats --format json: emits parseable JSON with descending counts
ok 7 stats: malformed JSON lines and records lacking pattern are skipped, not fatal
ok 8 stats: missing input file exits non-zero with message on stderr

The ordering test (#1) is the central-promise check: rank 1 is the
highest-count pattern, rank 10 is the lowest of the top-10, and ties
are resolved deterministically. The JSON-format test verifies the rows
are monotonically descending so downstream consumers can trust the
contract regardless of renderer.

Round-1 dependency

Designed to slot into the unified scripts/nkb.mjs dispatcher established
in round-1 PR #3 (feat(nkb): local full-text search CLI over knowledge base). Until #3 re-lands on main, this script is invokable standalone
via node scripts/nkb-stats.mjs; once the dispatcher merges, it becomes
the nkb stats subcommand sitting next to nkb search, nkb submit
(#13), nkb export (#14), nkb dedupe (#15), and nkb run (#16).

Test plan

@github-actions github-actions Bot added the pr-needs-issue PR has no Closes/Fixes/Resolves reference; auto-applied by pr-link-check label May 15, 2026
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c50c7e2dfc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread scripts/nkb-stats.mjs
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

1 similar comment
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

@wranngle wranngle enabled auto-merge (squash) May 19, 2026 03:06
@wranngle wranngle force-pushed the feat/r2-nkb-stats branch from da7647e to 98af268 Compare May 19, 2026 03:20
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

1 similar comment
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

@wranngle wranngle force-pushed the feat/r2-nkb-stats branch from f820fd2 to d203444 Compare May 19, 2026 03:29
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

3 similar comments
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

wranngle added a commit that referenced this pull request May 19, 2026
## Summary

Adds `scripts/nkb-graph.mjs` — emits a Mermaid graph of
pattern→dependency
edges parsed from a `## Depends-on` section in each
`workflow-patterns/*.md`
doc. The `--check` flag exits non-zero when any pattern references a
slug
with no matching `.md` file in the scanned directory.

This is the **structural** half of the citation-graph convention started
in
round-1 PR #5 (`feat(nkb): citation lint + Sources backfill on pattern
docs`):
PR #5 made every doc cite its external sources via `## Sources`; this PR
makes every doc declare its internal cross-pattern dependencies via
`## Depends-on`, and proves they all resolve. Both lints share the same
fail-closed posture so CI can wire either as a required check.

The schema is minimal — `## Depends-on` is followed by a bullet list of
slugs, one per line, where each slug is the basename of a sibling `.md`
in the same directory. A pattern with no dependencies either omits the
section entirely or leaves it empty. The existing
`voice-agent-elevenlabs-
patterns.md` doc parses cleanly under this schema with zero edges, so
the
new convention is strictly additive — no backfill required on `main`.

### Fixtures

`fixtures/graph/{ok,broken}/` follows the same convention as the dedupe
fixture set (#15) and the stats fixture (#17):

- `ok/` — three-pattern chain (`webhook-dedup-key →
http-retry-idempotency
  → error-monitoring-fanout`). All edges resolve.
- `broken/` — same chain plus a dangling edge to `nonexistent-upstream`.
  This is the negative-path fixture for `--check`.

### Proof

Mermaid render of the ok fixture:

```
$ node scripts/nkb-graph.mjs --dir fixtures/graph/ok
\`\`\`mermaid
graph LR
  error_monitoring_fanout["error-monitoring-fanout"]
  http_retry_idempotency["http-retry-idempotency"]
  webhook_dedup_key["webhook-dedup-key"]
  http_retry_idempotency --> error_monitoring_fanout
  webhook_dedup_key --> http_retry_idempotency
\`\`\`
```

Fail-closed broken-link check:

```
$ node scripts/nkb-graph.mjs --dir fixtures/graph/broken --check
nkb-graph check: 1 broken link(s):
  - webhook-dedup-key → nonexistent-upstream (no such pattern)
$ echo $?
1
```

Real `workflow-patterns/` directory on `main` (additive, doesn't
regress):

```
$ node scripts/nkb-graph.mjs --check
nkb-graph check: ok — 1 pattern(s), 0 edge(s), 0 broken
```

`tests/graph.bats` (10 cases, all green locally):

```
$ bats tests/graph.bats
1..10
ok 1 graph: mermaid output lists every pattern in the ok fixture as a node
ok 2 graph: edges in mermaid mirror Depends-on declarations
ok 3 graph --check: ok fixture passes with exit 0
ok 4 graph --check: broken fixture fails with exit 1 and names the missing slug
ok 5 graph --check --format json: ok fixture reports ok:true, broken:[]
ok 6 graph --check --format json: broken fixture reports the from/to edge
ok 7 graph: --format json (no --check) dumps every pattern with its deps list
ok 8 graph: pattern with no Depends-on section produces zero edges from it
ok 9 graph: missing --dir target exits non-zero with stderr message
ok 10 graph: mermaid output marks missing dep edges with dotted-arrow annotation
```

The broken-link check (#4) is the central-promise test: it asserts both
the non-zero exit and that the offending edge (`webhook-dedup-key →
nonexistent-upstream`) is named verbatim in the failure output.

### Round-1 / round-2 dependencies

Sits next to the other `scripts/nkb-*.mjs` round-2 deliverables — submit
(#13), JSON-LD export (#14), dedupe (#15), sandbox runner (#16),
adoption
stats (#17) — and will slot under the unified `scripts/nkb.mjs`
dispatcher
established by round-1 #3 once that lands on `main`. Until then it is
invokable standalone as `node scripts/nkb-graph.mjs`. Citing round-1 #5
specifically because that PR establishes the precedent of a fail-closed
CI lint over `workflow-patterns/*.md`; this PR extends that pattern
along the internal-link axis.

## Test plan

- [x] `bats tests/graph.bats` — all 10 outcome tests pass
- [x] `node scripts/nkb-graph.mjs --check` against real
`workflow-patterns/` exits 0
- [x] `node scripts/nkb-graph.mjs --dir fixtures/graph/broken --check`
exits 1 and names the bad edge
- [ ] Reviewer confirms `## Depends-on` schema is acceptable to bolt
onto existing pattern docs
- [ ] Reviewer decides whether to wire `--check` into
`.github/workflows/lint.yml` alongside the round-1 #5 citation lint

Co-authored-by: Cody Arnold <cody@wranngle.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
wranngle added a commit that referenced this pull request May 19, 2026
## Summary

Adds `scripts/nkb-graph.mjs` — emits a Mermaid graph of
pattern→dependency
edges parsed from a `## Depends-on` section in each
`workflow-patterns/*.md`
doc. The `--check` flag exits non-zero when any pattern references a
slug
with no matching `.md` file in the scanned directory.

This is the **structural** half of the citation-graph convention started
in
round-1 PR #5 (`feat(nkb): citation lint + Sources backfill on pattern
docs`):
PR #5 made every doc cite its external sources via `## Sources`; this PR
makes every doc declare its internal cross-pattern dependencies via
`## Depends-on`, and proves they all resolve. Both lints share the same
fail-closed posture so CI can wire either as a required check.

The schema is minimal — `## Depends-on` is followed by a bullet list of
slugs, one per line, where each slug is the basename of a sibling `.md`
in the same directory. A pattern with no dependencies either omits the
section entirely or leaves it empty. The existing
`voice-agent-elevenlabs-
patterns.md` doc parses cleanly under this schema with zero edges, so
the
new convention is strictly additive — no backfill required on `main`.

### Fixtures

`fixtures/graph/{ok,broken}/` follows the same convention as the dedupe
fixture set (#15) and the stats fixture (#17):

- `ok/` — three-pattern chain (`webhook-dedup-key →
http-retry-idempotency
  → error-monitoring-fanout`). All edges resolve.
- `broken/` — same chain plus a dangling edge to `nonexistent-upstream`.
  This is the negative-path fixture for `--check`.

### Proof

Mermaid render of the ok fixture:

```
$ node scripts/nkb-graph.mjs --dir fixtures/graph/ok
\`\`\`mermaid
graph LR
  error_monitoring_fanout["error-monitoring-fanout"]
  http_retry_idempotency["http-retry-idempotency"]
  webhook_dedup_key["webhook-dedup-key"]
  http_retry_idempotency --> error_monitoring_fanout
  webhook_dedup_key --> http_retry_idempotency
\`\`\`
```

Fail-closed broken-link check:

```
$ node scripts/nkb-graph.mjs --dir fixtures/graph/broken --check
nkb-graph check: 1 broken link(s):
  - webhook-dedup-key → nonexistent-upstream (no such pattern)
$ echo $?
1
```

Real `workflow-patterns/` directory on `main` (additive, doesn't
regress):

```
$ node scripts/nkb-graph.mjs --check
nkb-graph check: ok — 1 pattern(s), 0 edge(s), 0 broken
```

`tests/graph.bats` (10 cases, all green locally):

```
$ bats tests/graph.bats
1..10
ok 1 graph: mermaid output lists every pattern in the ok fixture as a node
ok 2 graph: edges in mermaid mirror Depends-on declarations
ok 3 graph --check: ok fixture passes with exit 0
ok 4 graph --check: broken fixture fails with exit 1 and names the missing slug
ok 5 graph --check --format json: ok fixture reports ok:true, broken:[]
ok 6 graph --check --format json: broken fixture reports the from/to edge
ok 7 graph: --format json (no --check) dumps every pattern with its deps list
ok 8 graph: pattern with no Depends-on section produces zero edges from it
ok 9 graph: missing --dir target exits non-zero with stderr message
ok 10 graph: mermaid output marks missing dep edges with dotted-arrow annotation
```

The broken-link check (#4) is the central-promise test: it asserts both
the non-zero exit and that the offending edge (`webhook-dedup-key →
nonexistent-upstream`) is named verbatim in the failure output.

### Round-1 / round-2 dependencies

Sits next to the other `scripts/nkb-*.mjs` round-2 deliverables — submit
(#13), JSON-LD export (#14), dedupe (#15), sandbox runner (#16),
adoption
stats (#17) — and will slot under the unified `scripts/nkb.mjs`
dispatcher
established by round-1 #3 once that lands on `main`. Until then it is
invokable standalone as `node scripts/nkb-graph.mjs`. Citing round-1 #5
specifically because that PR establishes the precedent of a fail-closed
CI lint over `workflow-patterns/*.md`; this PR extends that pattern
along the internal-link axis.

## Test plan

- [x] `bats tests/graph.bats` — all 10 outcome tests pass
- [x] `node scripts/nkb-graph.mjs --check` against real
`workflow-patterns/` exits 0
- [x] `node scripts/nkb-graph.mjs --dir fixtures/graph/broken --check`
exits 1 and names the bad edge
- [ ] Reviewer confirms `## Depends-on` schema is acceptable to bolt
onto existing pattern docs
- [ ] Reviewer decides whether to wire `--check` into
`.github/workflows/lint.yml` alongside the round-1 #5 citation lint

Co-authored-by: Cody Arnold <cody@wranngle.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Cody Arnold and others added 2 commits May 18, 2026 23:41
Add `scripts/nkb-stats.mjs` — reads `fixtures/telemetry-sample.jsonl` and
prints the top-N (default 10) knowledge-base patterns by view count, with a
deterministic descending-count / ascending-slug tie-break so ordering is
testable. Supports `--input`, `--top`, `--format text|json`, and `--help`.

Tally is robust to malformed JSON lines and records missing the `pattern`
field; those are counted into a `skipped` meta field and the run continues.

Designed to slot into the unified `scripts/nkb.mjs` dispatcher established
in round-1 PR #3 (`feat(nkb): local full-text search CLI`); invokable
standalone via `node scripts/nkb-stats.mjs` until that dispatcher merges.

Outcome test suite at `tests/stats.bats` (8 cases) asserts:
- top-10 ordering matches the highest-count patterns in the fixture
- rank 1 is `slack-retry-storm` with count 10
- ties break alphabetically at rank 9/10
- exactly 10 ranked rows when `--top 10` against 12 distinct patterns
- `--format json` is parseable and counts are monotonically descending
- malformed + pattern-less lines are skipped, not fatal
- missing input file exits non-zero with a stderr message
## Summary

Adds `scripts/nkb-graph.mjs` — emits a Mermaid graph of
pattern→dependency
edges parsed from a `## Depends-on` section in each
`workflow-patterns/*.md`
doc. The `--check` flag exits non-zero when any pattern references a
slug
with no matching `.md` file in the scanned directory.

This is the **structural** half of the citation-graph convention started
in
round-1 PR #5 (`feat(nkb): citation lint + Sources backfill on pattern
docs`):
PR #5 made every doc cite its external sources via `## Sources`; this PR
makes every doc declare its internal cross-pattern dependencies via
`## Depends-on`, and proves they all resolve. Both lints share the same
fail-closed posture so CI can wire either as a required check.

The schema is minimal — `## Depends-on` is followed by a bullet list of
slugs, one per line, where each slug is the basename of a sibling `.md`
in the same directory. A pattern with no dependencies either omits the
section entirely or leaves it empty. The existing
`voice-agent-elevenlabs-
patterns.md` doc parses cleanly under this schema with zero edges, so
the
new convention is strictly additive — no backfill required on `main`.

### Fixtures

`fixtures/graph/{ok,broken}/` follows the same convention as the dedupe
fixture set (#15) and the stats fixture (#17):

- `ok/` — three-pattern chain (`webhook-dedup-key →
http-retry-idempotency
  → error-monitoring-fanout`). All edges resolve.
- `broken/` — same chain plus a dangling edge to `nonexistent-upstream`.
  This is the negative-path fixture for `--check`.

### Proof

Mermaid render of the ok fixture:

```
$ node scripts/nkb-graph.mjs --dir fixtures/graph/ok
\`\`\`mermaid
graph LR
  error_monitoring_fanout["error-monitoring-fanout"]
  http_retry_idempotency["http-retry-idempotency"]
  webhook_dedup_key["webhook-dedup-key"]
  http_retry_idempotency --> error_monitoring_fanout
  webhook_dedup_key --> http_retry_idempotency
\`\`\`
```

Fail-closed broken-link check:

```
$ node scripts/nkb-graph.mjs --dir fixtures/graph/broken --check
nkb-graph check: 1 broken link(s):
  - webhook-dedup-key → nonexistent-upstream (no such pattern)
$ echo $?
1
```

Real `workflow-patterns/` directory on `main` (additive, doesn't
regress):

```
$ node scripts/nkb-graph.mjs --check
nkb-graph check: ok — 1 pattern(s), 0 edge(s), 0 broken
```

`tests/graph.bats` (10 cases, all green locally):

```
$ bats tests/graph.bats
1..10
ok 1 graph: mermaid output lists every pattern in the ok fixture as a node
ok 2 graph: edges in mermaid mirror Depends-on declarations
ok 3 graph --check: ok fixture passes with exit 0
ok 4 graph --check: broken fixture fails with exit 1 and names the missing slug
ok 5 graph --check --format json: ok fixture reports ok:true, broken:[]
ok 6 graph --check --format json: broken fixture reports the from/to edge
ok 7 graph: --format json (no --check) dumps every pattern with its deps list
ok 8 graph: pattern with no Depends-on section produces zero edges from it
ok 9 graph: missing --dir target exits non-zero with stderr message
ok 10 graph: mermaid output marks missing dep edges with dotted-arrow annotation
```

The broken-link check (#4) is the central-promise test: it asserts both
the non-zero exit and that the offending edge (`webhook-dedup-key →
nonexistent-upstream`) is named verbatim in the failure output.

### Round-1 / round-2 dependencies

Sits next to the other `scripts/nkb-*.mjs` round-2 deliverables — submit
(#13), JSON-LD export (#14), dedupe (#15), sandbox runner (#16),
adoption
stats (#17) — and will slot under the unified `scripts/nkb.mjs`
dispatcher
established by round-1 #3 once that lands on `main`. Until then it is
invokable standalone as `node scripts/nkb-graph.mjs`. Citing round-1 #5
specifically because that PR establishes the precedent of a fail-closed
CI lint over `workflow-patterns/*.md`; this PR extends that pattern
along the internal-link axis.

## Test plan

- [x] `bats tests/graph.bats` — all 10 outcome tests pass
- [x] `node scripts/nkb-graph.mjs --check` against real
`workflow-patterns/` exits 0
- [x] `node scripts/nkb-graph.mjs --dir fixtures/graph/broken --check`
exits 1 and names the bad edge
- [ ] Reviewer confirms `## Depends-on` schema is acceptable to bolt
onto existing pattern docs
- [ ] Reviewer decides whether to wire `--check` into
`.github/workflows/lint.yml` alongside the round-1 #5 citation lint

Co-authored-by: Cody Arnold <cody@wranngle.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@wranngle wranngle force-pushed the feat/r2-nkb-stats branch from d6faa48 to dc63de3 Compare May 19, 2026 03:41
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

1 similar comment
@github-actions
Copy link
Copy Markdown

This PR needs an issue link.

Add Closes #N / Fixes #N / Resolves #N to the description — or file an issue first via gh-issue.sh. Convention: every PR has an audit trail back to a problem statement.

@wranngle wranngle merged commit 2c1f148 into main May 19, 2026
13 checks passed
@wranngle wranngle deleted the feat/r2-nkb-stats branch May 19, 2026 03:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-needs-issue PR has no Closes/Fixes/Resolves reference; auto-applied by pr-link-check

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant