@agentrhq/webcmd 0.2.2 → 0.2.3

package/dist/src/release-notes.js

@@ -1,4 +1,11 @@
-export const RELEASE_NOTE_SECTIONS = ['Highlights', 'Improvements', 'Fixes', 'Contributors', 'Reverts'];
+export const RELEASE_NOTE_SECTIONS = [
+    'Highlights',
+    'Improvements',
+    'Fixes',
+    'Adapters',
+    'Contributors',
+    'Reverts',
+];
 const SQUASH_MERGE_PR_NUMBER_PATTERN = /\(#(?<number>\d+)\)\s*$/;
 const MERGE_COMMIT_PR_NUMBER_PATTERN = /^Merge pull request #(?<number>\d+) /;
 const RELEASE_PLEASE_TITLE_PATTERN = /^chore(?:\([^)]+\))?: release(?:\s|$)/;
@@ -13,6 +20,39 @@ function formatSectionContent(content) {
     const trimmed = content?.trim();
     return trimmed && trimmed.length > 0 ? trimmed : 'None.';
 }
+function escapeRegExp(value) {
+    return value.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+}
+function formatReleaseNotesForChangelog(notes) {
+    const trimmed = notes.trim();
+    if (!trimmed)
+        return '### Highlights\nNone.';
+    return trimmed.replace(/^##\s+/gm, '### ');
+}
+export function releaseVersionFromTag(tag) {
+    const value = tag.trim();
+    if (value.startsWith('webcmd-v'))
+        return value.slice('webcmd-v'.length);
+    if (value.startsWith('v'))
+        return value.slice(1);
+    return value;
+}
+export function replaceChangelogReleaseNotes(changelog, tag, notes) {
+    const version = releaseVersionFromTag(tag);
+    const headingPattern = new RegExp(`^## \\[${escapeRegExp(version)}\\]\\([^\\n]+\\) \\([^\\n]+\\)\\s*$`, 'm');
+    const headingMatch = headingPattern.exec(changelog);
+    if (!headingMatch) {
+        throw new Error(`Could not find CHANGELOG.md entry for ${version}`);
+    }
+    const headingEnd = headingMatch.index + headingMatch[0].length;
+    const remaining = changelog.slice(headingEnd);
+    const nextReleaseMatch = /\n## \[/.exec(remaining);
+    const releaseEnd = nextReleaseMatch ? headingEnd + nextReleaseMatch.index : changelog.length;
+    const before = changelog.slice(0, headingEnd).trimEnd();
+    const after = changelog.slice(releaseEnd);
+    const suffix = after ? after.replace(/^\n+/, '\n\n') : '\n';
+    return `${before}\n\n${formatReleaseNotesForChangelog(notes)}${suffix}`;
+}
 export function extractPullRequestNumber(message) {
     const firstLine = message.split(/\r?\n/, 1)[0] ?? message;
     const squashMatch = firstLine.match(SQUASH_MERGE_PR_NUMBER_PATTERN);
@@ -92,6 +132,9 @@ export function buildReleaseNotesPrompt(context) {
         'Use only the supplied pull requests below. Do not invent changes or pull in information from elsewhere.',
         `Required sections: ${RELEASE_NOTE_SECTIONS.map((section) => `## ${section}`).join(', ')}.`,
         'Each section must be present in the final notes.',
+        'In this project, CLI commands and adapters are the same thing. Treat any PR that adds, removes, or changes files under clis/** as an adapter change, even if the PR title says "CLI" instead of "adapter".',
+        'Put new site adapters/CLIs, adapter promotions, adapter hardening, adapter output changes, selector/API updates, and site-specific workflow improvements in ## Adapters.',
+        'Use ## Improvements for non-adapter product, runtime, CLI, docs, or workflow improvements.',
         '',
         `Pull requests included for this release:`,
         prSummaries,

package/dist/src/release-notes.test.js

@@ -1,5 +1,5 @@
 import { describe, expect, it } from 'vitest';
-import { RELEASE_NOTE_SECTIONS, buildReleaseNotesPrompt, extractPullRequestNumber, filterReleasePullRequests, normalizeReleaseNotes, } from './release-notes.js';
+import { RELEASE_NOTE_SECTIONS, buildReleaseNotesPrompt, extractPullRequestNumber, filterReleasePullRequests, normalizeReleaseNotes, replaceChangelogReleaseNotes, } from './release-notes.js';
 describe('release notes helpers', () => {
     it('extracts PR numbers from squash and merge commit messages', () => {
         expect(extractPullRequestNumber('feat: add release notes (#123)')).toBe(123);
@@ -29,10 +29,44 @@ describe('release notes helpers', () => {
         for (const section of RELEASE_NOTE_SECTIONS) {
             expect(normalized).toContain(`## ${section}`);
         }
+        expect(normalized).toContain('## Adapters\nNone.');
         expect(normalized).toContain('## Improvements\nNone.');
         expect(normalized).toContain('## Contributors\n- @alice\n- @bob');
         expect(normalized).toContain('## Reverts\nNone.');
     });
+    it('replaces a matching changelog release entry with generated notes', () => {
+        const changelog = [
+            '# Changelog',
+            '',
+            '## [0.2.3](https://github.com/agentrhq/webcmd/compare/webcmd-v0.2.2...webcmd-v0.2.3) (2026-07-09)',
+            '',
+            '',
+            '### Features',
+            '',
+            '* release-please generated note',
+            '',
+            '## [0.2.2](https://github.com/agentrhq/webcmd/compare/webcmd-v0.2.1...webcmd-v0.2.2) (2026-07-08)',
+            '',
+            '### Bug Fixes',
+            '',
+            '* older note',
+            '',
+        ].join('\n');
+        const notes = [
+            '## Highlights',
+            '- Better release notes.',
+            '',
+            '## Adapters',
+            '- Improved district checkout.',
+        ].join('\n');
+        const updated = replaceChangelogReleaseNotes(changelog, 'webcmd-v0.2.3', notes);
+        expect(updated).toContain('## [0.2.3]');
+        expect(updated).toContain('### Highlights\n- Better release notes.');
+        expect(updated).toContain('### Adapters\n- Improved district checkout.');
+        expect(updated).not.toContain('release-please generated note');
+        expect(updated).toContain('## [0.2.2]');
+        expect(updated).toContain('* older note');
+    });
     it('builds a prompt grounded in the exact release range and PR list', () => {
         const context = {
             tag: 'v0.2.0',
@@ -56,6 +90,10 @@ describe('release notes helpers', () => {
         expect(prompt).toContain('PR #42: feat: add docs scaffold');
         expect(prompt).toContain('docs/docs.json');
         expect(prompt).toContain('## Highlights');
+        expect(prompt).toContain('## Adapters');
+        expect(prompt).toContain('CLI commands and adapters are the same thing');
+        expect(prompt).toContain('files under clis/** as an adapter change');
+        expect(prompt).toContain('Put new site adapters/CLIs, adapter promotions, adapter hardening');
         expect(prompt).toContain('## Reverts');
     });
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentrhq/webcmd",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "Turn websites, browser sessions, desktop apps, and local tools into deterministic CLI surfaces for humans and AI agents.",
   "engines": {
     "node": ">=20.0.0"

package/scripts/generate-release-notes.ts

@@ -1,4 +1,5 @@
 import { execFileSync } from 'node:child_process';
+import { readFileSync, writeFileSync } from 'node:fs';
 import { pathToFileURL } from 'node:url';
 import { GoogleGenAI } from '@google/genai';
 import {
@@ -6,6 +7,7 @@ import {
   extractPullRequestNumber,
   filterReleasePullRequests,
   normalizeReleaseNotes,
+  replaceChangelogReleaseNotes,
   type PullRequestDetails,
   type ReleaseContext,
 } from '../src/release-notes.js';
@@ -195,12 +197,41 @@ function contributorHandles(pullRequests: PullRequestDetails[]): string[] {
   return pullRequests.flatMap((pr) => (pr.author?.login ? [pr.author.login] : []));
 }
 
+function updateChangelog(tag: string | undefined, notesPath: string | undefined, changelogPath: string | undefined, io: Io): number {
+  if (!tag || !notesPath) {
+    io.writeStderr('Usage: generate-release-notes --update-changelog <tag> <notes-file> [changelog-file]\n');
+    return 1;
+  }
+
+  const targetChangelogPath = changelogPath ?? 'CHANGELOG.md';
+
+  try {
+    const notes = readFileSync(notesPath, 'utf8');
+    const changelog = readFileSync(targetChangelogPath, 'utf8');
+    const updated = replaceChangelogReleaseNotes(changelog, tag, notes);
+    if (updated !== changelog) {
+      writeFileSync(targetChangelogPath, updated);
+    }
+
+    io.writeStdout(`Updated ${targetChangelogPath} for ${tag}\n`);
+    return 0;
+  } catch (error) {
+    const message = error instanceof Error ? error.message : String(error);
+    io.writeStderr(`CHANGELOG.md update failed: ${message}\n`);
+    return 1;
+  }
+}
+
 export async function runGenerateReleaseNotes(
   argv: string[] = process.argv,
   env: NodeJS.ProcessEnv = process.env,
   deps: RunDependencies = {},
   io: Io = DEFAULT_IO,
 ): Promise<number> {
+  if (argv[2] === '--update-changelog') {
+    return updateChangelog(argv[3], argv[4], argv[5], io);
+  }
+
   const tag = argv[2];
   if (!tag) {
     io.writeStderr('Usage: generate-release-notes <tag>\n');

package/skills/webcmd-adapter-author/SKILL.md

@@ -194,6 +194,14 @@ Check these off step by step:
         [ ] `fixtures/<cmd>-<YYYYMMDDHHMM>.json`: save one complete endpoint response sample after removing cookies, tokens, and private user fields. Use it for later field comparison and offline replay.
         [ ] If debugging dumped temporary files in the repo or adapter directory, such as `.dbg-*.html`, `raw-*.json`, or similar, **delete them before commit**. Those belong in `~/.webcmd/sites/<site>/fixtures/` or `/tmp/`.
 
+[ ] 13. **First command for this site? Stop and ask before building more.**
+        [ ] If this was the site's first command, do not silently keep scaffolding more commands. Ask the user what use cases they have in mind for this site — who the persona is, what they're trying to accomplish end to end.
+        [ ] From the use cases, propose the full set of commands you'd recommend adding, not just the obvious next one. Cover the whole journey the use cases imply (discovery, single-item detail, comparison, account/write actions, etc.), not only what's cheapest to build.
+        [ ] If that set is small (roughly ≤6-8 commands), list it flat and ask the user to confirm or trim it.
+        [ ] If it's large, bucket the commands into named groups (e.g. "Discovery", "Single-item evaluation", "Account actions requiring login") and ask the user which bucket(s) to build first — do not dump an unbucketed wall of commands.
+        [ ] Flag any bucket that needs a capability not yet solved (login/OTP, write access, payment) as its own decision point — e.g. "these need login — how do you want to handle auth?" — separate from the command list itself.
+        [ ] Do not scaffold additional commands until the user has confirmed which ones to build.
+
 ---
 
 ## Fallback Paths
@@ -247,6 +255,7 @@ Check these off step by step:
 - **Persistent sessions keep stale DOM between commands.** `siteSession: 'persistent'` shares one tab per site; leftover modals/drawers from the previous command leak into the next one. State-sensitive write commands (checkout flows) should add `freshPage: true` (new tab, same lease — cookies/login/location survive). Verify session-scoped context (login, selected city/date) *before* side effects, and embed such context in URLs/IDs your command emits for sibling commands. See `references/adapter-template.md` and "Persistent Sessions and State Hygiene" in `docs/authoring.mdx`.
 - For private adapters, write `~/.webcmd/clis/<site>/<name>.js` to avoid a build. Copy to `clis/<site>/<name>.js` only when preparing a PR.
 - Write site memory every round: no memory -> use skill -> produce memory -> next time becomes a five-minute task.
+- **After a site's first command passes verify, stop and ask the user for their use cases before recommending next set of commands.** See Runbook Step 13.
 - **Raw dumps, packet captures, and HTML samples from debugging may only be written to `~/.webcmd/sites/<site>/fixtures/` or `/tmp/`. Never leave `.dbg-*.html`, `raw-*.json`, `sample.*`, or similar temporary files in the repo root, `clis/<site>/`, or the current working directory.**
 - **JSDOM unit-test fixtures (`clis/<site>/__fixtures__/<command>.html`) are the exception.** They are intentional review artifacts committed to the repo, not temporary dumps. Because of that, the quality bar is higher: complete the five steps in `references/jsdom-fixture-pattern.md`, including the mandatory `awk 'NF>0'` blank-line tightening, and reverse-validate once to prove the regression guard can fail.