Add v4 path-segment routing repro script

.github/workflows/claude-issue-to-pr.yml

@@ -0,0 +1,77 @@
+name: Claude Issue to PR
+
+# Thin caller of the reusable in HarperFast/ai-review-prompts. The
+# single `uses:` ref pin below controls everything that moves
+# together — workflow logic, auth script, agent prompt, allowed-
+# labels list. Bumping the pin is the entire upgrade motion.
+#
+# Pre-requisites (org-level secrets, configured once on HarperFast):
+#   - HARPERFAST_AI_CLIENT_ID
+#   - HARPERFAST_AI_APP_PRIVATE_KEY
+#
+# Plus the per-repo / inherited:
+#   - ANTHROPIC_API_KEY             (required)
+
+on:
+  issues:
+    types: [labeled]
+
+concurrency:
+  group: claude-issue-${{ github.event.issue.number }}
+  cancel-in-progress: false
+
+jobs:
+  work:
+    uses: HarperFast/ai-review-prompts/.github/workflows/_claude-issue-to-pr.yml@f6daed301f8a7ece74593506de38c6e80820b00b # main 2026-05-06 (post #11/#12/#14)
+    with:
+      # Same SHA as the `uses:` ref above. See the comment in
+      # claude-mention.yml for why the duplication is unavoidable.
+      ai-review-prompts-ref: f6daed301f8a7ece74593506de38c6e80820b00b
+      # Plugin repo — bun is part of the test path.
+      setup-bun: true
+      repo-specific-conventions: |
+        ## OAuth-specific notes
+
+        - `config.yaml` holds the plugin entry point (`pluginModule`)
+          and runtime OAuth defaults. NOT doc-only — any change
+          there is a code/config change.
+        - Tests run under both Node (`npm test`) and Bun
+          (`bun test`); both must pass.
+
+        ## Documentation scope boundary
+
+        Harper maintains authoritative docs at
+        https://docs.harperdb.io covering core, pro, and fabric.
+        This repo's docs should NOT re-explain Harper mechanics
+        those docs already cover — they drift out of sync when the
+        Harper docs update.
+
+        When writing or revising docs here:
+
+        - Document what's specific to THIS component — env var
+          names, config shape, setup flow, integration API.
+        - For anything not component-specific (deployment mechanics,
+          runtime env var handling, Fabric configuration, core
+          Harper behavior, SQL, replication), LINK to the Harper
+          docs rather than re-explaining.
+      pre-commit-validation: |
+        **`config.yaml` is NOT doc-only** — it holds the plugin
+        entry point (`pluginModule`) and runtime OAuth defaults.
+        Any change touching `config.yaml` requires the full
+        validation path regardless of the `claude-fix:*` label.
+
+        - `claude-fix:typo` / `claude-fix:docs` (doc-only changes
+          to `*.md`, `docs/**`, or `package.json`
+          keyword/description fields): run `npm run format:check`
+          and `npm run lint`. Skip `npm run build` / `npm test` /
+          `bun test` — they are not affected and waste turns.
+        - `claude-fix:deps` / `claude-fix:bug` or any change that
+          touches code or `config.yaml`: run
+          `npm run build && npm run lint && npm run format:check && npm test`
+          and `bun test`. Fix anything that fails.
+
+        When in doubt, err toward the fuller validation.
+    secrets:
+      ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+      HARPERFAST_AI_CLIENT_ID: ${{ secrets.HARPERFAST_AI_CLIENT_ID }}
+      HARPERFAST_AI_APP_PRIVATE_KEY: ${{ secrets.HARPERFAST_AI_APP_PRIVATE_KEY }}

.github/workflows/claude-mention.yml

@@ -0,0 +1,86 @@
+name: Claude Mention Handler
+
+# Thin caller of the reusable in HarperFast/ai-review-prompts. The
+# single `uses:` ref pin below controls everything that moves
+# together — workflow logic, parse + auth scripts, agent prompt.
+# Bumping the pin is the entire upgrade motion.
+#
+# Pre-requisites (org-level secrets, configured once on HarperFast):
+#   - HARPERFAST_AI_CLIENT_ID       (the App's Client ID, like Iv23li…)
+#   - HARPERFAST_AI_APP_PRIVATE_KEY (.pem file contents)
+#
+# Plus the per-repo / inherited:
+#   - ANTHROPIC_API_KEY             (required)
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+
+concurrency:
+  group: claude-mention-${{ github.event.issue.number || github.event.pull_request.number }}
+  cancel-in-progress: false
+
+jobs:
+  mention:
+    uses: HarperFast/ai-review-prompts/.github/workflows/_claude-mention.yml@f6daed301f8a7ece74593506de38c6e80820b00b # main 2026-05-06 (post #11/#12/#14)
+    with:
+      # Same SHA as the `uses:` ref above. The reusable uses this to
+      # check out HarperFast/ai-review-prompts (parse + auth scripts)
+      # at the same ref as the workflow logic itself.
+      #
+      # The duplication is unavoidable: reusable workflows can't
+      # introspect their own ref (`github.workflow_ref` resolves to
+      # the CALLER's ref in `workflow_call` context), and `uses: …@<ref>`
+      # is parsed literally so we can't interpolate a variable.
+      ai-review-prompts-ref: f6daed301f8a7ece74593506de38c6e80820b00b
+      # Plugin repo — opt into bun setup so the agent can run
+      # `bun test` and `bun run …` for repo-specific scripts.
+      setup-bun: true
+      repo-specific-conventions: |
+        ## OAuth-specific notes
+
+        - `config.yaml` holds the plugin entry point (`pluginModule`)
+          and runtime OAuth defaults. NOT doc-only — any change there
+          is a code/config change requiring full validation.
+        - Tests run under both Node (`npm test`) and Bun (`bun test`);
+          both must pass before opening / pushing to a PR.
+
+        ## Documentation scope boundary
+
+        Harper maintains authoritative docs at
+        https://docs.harperdb.io covering core, pro, and fabric.
+        This repo's docs should NOT re-explain Harper mechanics
+        those docs already cover — they drift out of sync when the
+        Harper docs update.
+
+        When writing or revising docs here:
+
+        - Document what's specific to THIS component — env var
+          names, config shape, setup flow, integration API.
+        - For anything not component-specific (deployment mechanics,
+          runtime env var handling, Fabric configuration, core
+          Harper behavior, SQL, replication), LINK to the Harper
+          docs rather than re-explaining.
+      pre-commit-validation: |
+        Scale validation to the kind of change you made:
+
+        - Doc-only change (only `*.md`, `docs/**`, or `package.json`
+          keyword/description edits): run `npm run format:check` and
+          `npm run lint`. Do NOT run `npm run build` / `npm test` /
+          `bun test` — they are not affected and waste turns.
+
+          `config.yaml` is NOT doc-only — it holds the plugin entry
+          point (`pluginModule`) and runtime OAuth defaults. Treat
+          any change there as a code/config change.
+        - Code or config change that affects behavior: run `npm ci`
+          first (deps aren't pre-installed in this workflow), then
+          `npm run build && npm run lint && npm run format:check && npm test`
+          and `bun test`. Fix anything that fails.
+
+        When in doubt, err toward the fuller validation.
+    secrets:
+      ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+      HARPERFAST_AI_CLIENT_ID: ${{ secrets.HARPERFAST_AI_CLIENT_ID }}
+      HARPERFAST_AI_APP_PRIVATE_KEY: ${{ secrets.HARPERFAST_AI_APP_PRIVATE_KEY }}