@codyswann/lisa 4.60.4 → 4.60.6

package/plugins/lisa-nestjs-cursor/hooks/block-migration-edits.sh

@@ -2,7 +2,9 @@
 # This file is managed by Lisa.
 # Do not edit directly — changes will be overwritten on the next `lisa` run.
 
-# PreToolUse hook: block Write/Edit on TypeORM migration files.
+# PreToolUse hook: block Write/Edit on TypeORM migration files by default.
+# This scopes direct edit tools; it does not verify approval or establish the
+# provenance of files written through other tools.
 # NestJS projects must use `bun run migration:generate` to create migrations
 # from entity diffs. Hand-written migrations drift from entity metadata and
 # break the schema/migration contract.
@@ -79,8 +81,8 @@ LISA_HOOK_DIR="$(cd "$(dirname "$0")" 2>/dev/null && pwd)"
 # That is what keeps an undeclared project on exactly the command, and exactly
 # the exit status, it had before.
 #
-# ONE PROPERTY, so there is no all-or-nothing question here: this hook proves
-# `migration-provenance` and nothing else.
+# A project may supply its own `migration-provenance` check for these edits.
+# The built-in only refuses the scoped Write/Edit calls.
 # ---------------------------------------------------------------------------
 if [ -n "${CLAUDE_PROJECT_DIR:-}" ] &&
   [ -f "$LISA_HOOK_DIR/lisa-edit-gate.sh" ] &&
@@ -98,7 +100,7 @@ if [ -n "${CLAUDE_PROJECT_DIR:-}" ] &&
 fi
 
 cat >&2 <<EOF
-❌ Blocked: Direct edits to TypeORM migration files are not allowed.
+❌ Blocked: This default hook refuses Write/Edit on TypeORM migration files.
 
 File: $FILE_PATH
 
@@ -110,20 +112,14 @@ artifact — generate them from entity diffs:
   2. Run: bun run migration:generate --name=<DescriptiveName>
   3. Review the generated migration; commit entity + migration together.
 
-If a schema change cannot be expressed via the entity model, the entity
-model is wrong — fix the entity, do not hand-write the migration.
+Out-of-band migrations (backfills, seed data, maintenance) cannot always
+come from entity diffs. A project that supports these edits can declare a
+\`migration-provenance\` check at \`pre-tool\` in .lisa.config.json. The hook
+runs that check and uses its result to permit or refuse the edit.
 
-OUT-OF-BAND MIGRATIONS (seed data, backfills, data transformations,
-one-off cleanup): these genuinely cannot come from entity diffs. They
-are legitimate but they bypass the entity-as-source-of-truth contract.
-
-If you believe this edit is an out-of-band migration:
-  1. STOP and tell the user what change is needed and why it cannot
-     be expressed via the entity model.
-  2. Get explicit approval before proceeding.
-  3. Document the rationale in the migration's class comment.
-
-Do NOT silently hand-write a migration. See the nestjs-rules skill
-for the full rationale.
+Document the migration's rationale and verification in its class comment.
+This default hook cannot verify human approval and does not inspect Bash
+writes. Do not switch tools to evade its refusal. See the nestjs-rules skill
+for the supported project-check path.
 EOF
 exit 2

package/plugins/lisa-nestjs-cursor/skills/nestjs-rules/SKILL.md

@@ -51,11 +51,9 @@ In this project, **entity files (`src/database/entities/*.ts`) are the single so
 2. Run `bun run migration:generate --name=<DescriptiveName>` to produce the migration from the diff.
 3. Review the generated migration, then commit both the entity change and the migration together.
 
-If a schema change cannot be expressed via the entity model, the entity model is wrong — fix the entity, do not hand-write the migration.
+### Generate Schema Migrations
 
-### Never Create Migration Files Manually
-
-Never create or modify a TypeORM migration file directly. Use `migration:generate` from `package.json`:
+Use `migration:generate` from `package.json` for changes represented by entity metadata:
 
 ```bash
 bun run migration:generate --name=<DescriptiveName>
@@ -69,18 +67,15 @@ Some changes genuinely cannot be derived from entity diffs:
 - **Data backfills** (populating a new column from existing rows)
 - **Data transformations** (splitting a column, normalizing values)
 - **One-off cleanup** (deleting orphaned rows before a constraint is added)
+- **Database maintenance** (refreshing planner statistics with `ANALYZE`)
 
-These are legitimate cases for a hand-written migration, but they are **out-of-band** — they bypass the entity-as-source-of-truth contract. When you encounter one:
-
-1. **Stop and tell the user.** Explain what change is needed and why it cannot be expressed via the entity model.
-2. **Get explicit approval** before writing the migration by hand.
-3. Document the rationale in the migration's class comment so future readers understand why this one was not generated.
+Use the project's established migration process for these cases. Document the rationale and verification in the migration's class comment so future readers understand why it was not generated. Apply the authorization already given for the work; the default edit hook does not record or verify human approval.
 
-Do not silently hand-write a migration for a backfill or seed-data change. The user must know that the entity-as-source-of-truth contract is being intentionally bypassed for this case.
+A project that supports direct migration edits can declare its own `migration-provenance` check at `pre-tool` in `.lisa.config.json`. The Claude and Codex hooks run that check for the targeted migration and permit the edit only when it passes. The check must validate the project's migration policy; an unconditional success command proves nothing. Without a declared check, the built-in still refuses the edit. OpenCode's migration adapter currently does not support this exception path and continues to refuse it.
 
 ### Enforcement
 
-The `lisa-nestjs` plugin ships a `PreToolUse` hook (`block-migration-edits.sh`) that blocks `Write`/`Edit` on any path matching `**/migrations/*.ts` or `**/migrations/*.js`. The block surfaces this rule's guidance to remind you to either (a) edit the entity instead, or (b) ask the user before proceeding with an out-of-band migration.
+The `lisa-nestjs` plugin's default `PreToolUse` hook (`block-migration-edits.sh`) refuses `Write`/`Edit` on paths matching `**/migrations/*.ts` or `**/migrations/*.js`. Codex also inspects `apply_patch`; its migration matcher and OpenCode's matcher cover numbered TypeScript migration filenames. These are direct-edit checks, not an audit of migration authorship: they do not inspect Bash writes. Do not switch tools to evade a refusal. Use the supported project check where available.
 
 ### Why Auto-Generation
 

package/plugins/lisa-openclaw/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.60.4",
+  "version": "4.60.6",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/nestjs/hooks/block-migration-edits.sh

@@ -2,7 +2,9 @@
 # This file is managed by Lisa.
 # Do not edit directly — changes will be overwritten on the next `lisa` run.
 
-# PreToolUse hook: block Write/Edit on TypeORM migration files.
+# PreToolUse hook: block Write/Edit on TypeORM migration files by default.
+# This scopes direct edit tools; it does not verify approval or establish the
+# provenance of files written through other tools.
 # NestJS projects must use `bun run migration:generate` to create migrations
 # from entity diffs. Hand-written migrations drift from entity metadata and
 # break the schema/migration contract.
@@ -79,8 +81,8 @@ LISA_HOOK_DIR="$(cd "$(dirname "$0")" 2>/dev/null && pwd)"
 # That is what keeps an undeclared project on exactly the command, and exactly
 # the exit status, it had before.
 #
-# ONE PROPERTY, so there is no all-or-nothing question here: this hook proves
-# `migration-provenance` and nothing else.
+# A project may supply its own `migration-provenance` check for these edits.
+# The built-in only refuses the scoped Write/Edit calls.
 # ---------------------------------------------------------------------------
 if [ -n "${CLAUDE_PROJECT_DIR:-}" ] &&
   [ -f "$LISA_HOOK_DIR/lisa-edit-gate.sh" ] &&
@@ -98,7 +100,7 @@ if [ -n "${CLAUDE_PROJECT_DIR:-}" ] &&
 fi
 
 cat >&2 <<EOF
-❌ Blocked: Direct edits to TypeORM migration files are not allowed.
+❌ Blocked: This default hook refuses Write/Edit on TypeORM migration files.
 
 File: $FILE_PATH
 
@@ -110,20 +112,14 @@ artifact — generate them from entity diffs:
   2. Run: bun run migration:generate --name=<DescriptiveName>
   3. Review the generated migration; commit entity + migration together.
 
-If a schema change cannot be expressed via the entity model, the entity
-model is wrong — fix the entity, do not hand-write the migration.
+Out-of-band migrations (backfills, seed data, maintenance) cannot always
+come from entity diffs. A project that supports these edits can declare a
+\`migration-provenance\` check at \`pre-tool\` in .lisa.config.json. The hook
+runs that check and uses its result to permit or refuse the edit.
 
-OUT-OF-BAND MIGRATIONS (seed data, backfills, data transformations,
-one-off cleanup): these genuinely cannot come from entity diffs. They
-are legitimate but they bypass the entity-as-source-of-truth contract.
-
-If you believe this edit is an out-of-band migration:
-  1. STOP and tell the user what change is needed and why it cannot
-     be expressed via the entity model.
-  2. Get explicit approval before proceeding.
-  3. Document the rationale in the migration's class comment.
-
-Do NOT silently hand-write a migration. See the nestjs-rules skill
-for the full rationale.
+Document the migration's rationale and verification in its class comment.
+This default hook cannot verify human approval and does not inspect Bash
+writes. Do not switch tools to evade its refusal. See the nestjs-rules skill
+for the supported project-check path.
 EOF
 exit 2

package/plugins/src/nestjs/skills/nestjs-rules/SKILL.md

@@ -51,11 +51,9 @@ In this project, **entity files (`src/database/entities/*.ts`) are the single so
 2. Run `bun run migration:generate --name=<DescriptiveName>` to produce the migration from the diff.
 3. Review the generated migration, then commit both the entity change and the migration together.
 
-If a schema change cannot be expressed via the entity model, the entity model is wrong — fix the entity, do not hand-write the migration.
+### Generate Schema Migrations
 
-### Never Create Migration Files Manually
-
-Never create or modify a TypeORM migration file directly. Use `migration:generate` from `package.json`:
+Use `migration:generate` from `package.json` for changes represented by entity metadata:
 
 ```bash
 bun run migration:generate --name=<DescriptiveName>
@@ -69,18 +67,15 @@ Some changes genuinely cannot be derived from entity diffs:
 - **Data backfills** (populating a new column from existing rows)
 - **Data transformations** (splitting a column, normalizing values)
 - **One-off cleanup** (deleting orphaned rows before a constraint is added)
+- **Database maintenance** (refreshing planner statistics with `ANALYZE`)
 
-These are legitimate cases for a hand-written migration, but they are **out-of-band** — they bypass the entity-as-source-of-truth contract. When you encounter one:
-
-1. **Stop and tell the user.** Explain what change is needed and why it cannot be expressed via the entity model.
-2. **Get explicit approval** before writing the migration by hand.
-3. Document the rationale in the migration's class comment so future readers understand why this one was not generated.
+Use the project's established migration process for these cases. Document the rationale and verification in the migration's class comment so future readers understand why it was not generated. Apply the authorization already given for the work; the default edit hook does not record or verify human approval.
 
-Do not silently hand-write a migration for a backfill or seed-data change. The user must know that the entity-as-source-of-truth contract is being intentionally bypassed for this case.
+A project that supports direct migration edits can declare its own `migration-provenance` check at `pre-tool` in `.lisa.config.json`. The Claude and Codex hooks run that check for the targeted migration and permit the edit only when it passes. The check must validate the project's migration policy; an unconditional success command proves nothing. Without a declared check, the built-in still refuses the edit. OpenCode's migration adapter currently does not support this exception path and continues to refuse it.
 
 ### Enforcement
 
-The `lisa-nestjs` plugin ships a `PreToolUse` hook (`block-migration-edits.sh`) that blocks `Write`/`Edit` on any path matching `**/migrations/*.ts` or `**/migrations/*.js`. The block surfaces this rule's guidance to remind you to either (a) edit the entity instead, or (b) ask the user before proceeding with an out-of-band migration.
+The `lisa-nestjs` plugin's default `PreToolUse` hook (`block-migration-edits.sh`) refuses `Write`/`Edit` on paths matching `**/migrations/*.ts` or `**/migrations/*.js`. Codex also inspects `apply_patch`; its migration matcher and OpenCode's matcher cover numbered TypeScript migration filenames. These are direct-edit checks, not an audit of migration authorship: they do not inspect Bash writes. Do not switch tools to evade a refusal. Use the supported project check where available.
 
 ### Why Auto-Generation
 

package/scripts/check-workflow-load-failures.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+import { runCli } from "../all/copy-overwrite/scripts/check-workflow-load-failures.mjs";
+
+runCli();

package/scripts/two-channel-couplings.json

@@ -97,7 +97,7 @@
     "workflows": 23,
     "steps": 781,
     "couplings": 33,
-    "inventory": 80
+    "inventory": 87
   },
   "counts": {
     "package-backed": 10,

package/typescript/copy-overwrite/.prettierignore

@@ -77,6 +77,7 @@ scripts/check-third-party-action-pins.mjs
 scripts/check-third-party-review-evidence.mjs
 scripts/check-threshold-ratchet.mjs
 scripts/check-verification-coverage.mjs
+scripts/check-workflow-load-failures.mjs
 scripts/classify-maestro-failures.mjs
 scripts/lisa-command-envelope.mjs
 scripts/lisa-commit-msg-gates.mjs

package/dist/core/reusable-workflow-load-adapter.d.ts

@@ -1,78 +0,0 @@
-/**
- * Turn GitHub's run endpoints into the pages `core/reusable-workflow-load-scan`
- * expects (CodySwannGT/lisa#3581).
- *
- * The HTTP request is injected. That keeps the endpoint shapes, the paging
- * parameters and the response handling under test against a stub, which is the
- * only way to prove this wiring without a live call whose rate limit decides
- * whether the suite passes — the lesson a sibling lane paid twenty minutes of
- * held-dirty tree to learn.
- *
- * ## Why this needs three endpoints and not one
- *
- * The run LIST gives id, caller path, timestamp and conclusion. It does not
- * give the two facts the verdict actually turns on: `referenced_workflows`
- * comes from the single-run endpoint, and the job count from the run's jobs
- * endpoint. So a full scan is inherently N+1, and reading every run's detail
- * across a wide window is the kind of request volume that gets a scheduled job
- * rate-limited into a false green.
- *
- * The narrowing that makes it affordable is sound rather than convenient: a
- * load failure is only reachable from a conclusion GitHub can produce BEFORE
- * creating a job. Detail is therefore fetched only for those, and a run with
- * any other conclusion keeps zeroes it never fetched.
- *
- * **Those zeroes are not measurements.** For a `success` run they are simply
- * absent evidence, and the classifier's label for such a run is not meaningful
- * — the only verdict this adapter's output supports is `load-failure`, which
- * is the one the scan filters for. Anything that starts reporting per-verdict
- * counts from these pages must fetch detail unconditionally first.
- * @module core/reusable-workflow-load-adapter
- */
-import type { RunPage } from "./reusable-workflow-load-scan.js";
-/** GitHub's default and maximum page size for the runs endpoint. */
-export declare const RUNS_PER_PAGE = 100;
-/** Performs one authenticated GET and returns the decoded JSON body. */
-export type GithubRequest = (path: string) => Promise<unknown>;
-/** What the fetcher needs to address a repository. */
-export interface AdapterOptions {
-    /** Repository in `owner/name` form. */
-    readonly repo: string;
-    /** The injected request function. */
-    readonly request: GithubRequest;
-    /** Page size; defaults to `RUNS_PER_PAGE`. */
-    readonly perPage?: number;
-}
-/**
- * Path for one page of run history, newest first.
- * @param repo - Repository in `owner/name` form
- * @param page - 1-based page number
- * @param perPage - Page size
- * @returns The API path to request
- */
-export declare function runsPath(repo: string, page: number, perPage: number): string;
-/**
- * Path for one run's detail, which is where `referenced_workflows` lives.
- * @param repo - Repository in `owner/name` form
- * @param id - The run id
- * @returns The API path to request
- */
-export declare function runPath(repo: string, id: number): string;
-/**
- * Path for one run's jobs, read only for its `total_count`.
- * @param repo - Repository in `owner/name` form
- * @param id - The run id
- * @returns The API path to request
- */
-export declare function jobsPath(repo: string, id: number): string;
-/**
- * Build the page fetcher `scanForLoadFailures` consumes.
- *
- * `hasMore` is derived from a full page rather than from `total_count`,
- * because a run created while the scan is paging shifts `total_count` under
- * it. A full page means "ask again"; a short page means the history ended.
- * @param options - Repository, request function and page size
- * @returns A fetcher for one 1-based page of run history
- */
-export declare function createRunPageFetcher(options: AdapterOptions): (page: number) => Promise<RunPage>;
-//# sourceMappingURL=reusable-workflow-load-adapter.d.ts.map

package/dist/core/reusable-workflow-load-adapter.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"reusable-workflow-load-adapter.d.ts","sourceRoot":"","sources":["../../src/core/reusable-workflow-load-adapter.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,OAAO,KAAK,EAAE,OAAO,EAAc,MAAM,kCAAkC,CAAC;AAY5E,oEAAoE;AACpE,eAAO,MAAM,aAAa,MAAM,CAAC;AAEjC,wEAAwE;AACxE,MAAM,MAAM,aAAa,GAAG,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;AAE/D,sDAAsD;AACtD,MAAM,WAAW,cAAc;IAC7B,uCAAuC;IACvC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,qCAAqC;IACrC,QAAQ,CAAC,OAAO,EAAE,aAAa,CAAC;IAChC,8CAA8C;IAC9C,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC;CAC3B;AAED;;;;;;GAMG;AACH,wBAAgB,QAAQ,CAAC,IAAI,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,MAAM,CAE5E;AAED;;;;;GAKG;AACH,wBAAgB,OAAO,CAAC,IAAI,EAAE,MAAM,EAAE,EAAE,EAAE,MAAM,GAAG,MAAM,CAExD;AAED;;;;;GAKG;AACH,wBAAgB,QAAQ,CAAC,IAAI,EAAE,MAAM,EAAE,EAAE,EAAE,MAAM,GAAG,MAAM,CAEzD;AA8ED;;;;;;;;GAQG;AACH,wBAAgB,oBAAoB,CAClC,OAAO,EAAE,cAAc,GACtB,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC,OAAO,CAAC,CAqBpC"}

package/dist/core/reusable-workflow-load-adapter.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"reusable-workflow-load-adapter.js","sourceRoot":"","sources":["../../src/core/reusable-workflow-load-adapter.ts"],"names":[],"mappings":"AAiCA;;;;;;;GAOG;AACH,MAAM,qBAAqB,GAAsB,CAAC,SAAS,EAAE,iBAAiB,CAAC,CAAC;AAEhF,oEAAoE;AACpE,MAAM,CAAC,MAAM,aAAa,GAAG,GAAG,CAAC;AAejC;;;;;;GAMG;AACH,MAAM,UAAU,QAAQ,CAAC,IAAY,EAAE,IAAY,EAAE,OAAe;IAClE,OAAO,SAAS,IAAI,0BAA0B,OAAO,SAAS,IAAI,EAAE,CAAC;AACvE,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,OAAO,CAAC,IAAY,EAAE,EAAU;IAC9C,OAAO,SAAS,IAAI,iBAAiB,EAAE,EAAE,CAAC;AAC5C,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,QAAQ,CAAC,IAAY,EAAE,EAAU;IAC/C,OAAO,SAAS,IAAI,iBAAiB,EAAE,kBAAkB,CAAC;AAC5D,CAAC;AAED;;;;;GAKG;AACH,SAAS,KAAK,CAAC,IAAa,EAAE,GAAW;IACvC,IAAI,OAAO,IAAI,KAAK,QAAQ,IAAI,IAAI,KAAK,IAAI;QAAE,OAAO,SAAS,CAAC;IAChE,OAAQ,IAAgC,CAAC,GAAG,CAAC,CAAC;AAChD,CAAC;AAED;;;;GAIG;AACH,SAAS,KAAK,CAAC,KAAc;IAC3B,OAAO,OAAO,KAAK,KAAK,QAAQ,IAAI,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC;AACzE,CAAC;AAED;;;;GAIG;AACH,SAAS,IAAI,CAAC,KAAc;IAC1B,OAAO,OAAO,KAAK,KAAK,QAAQ,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,CAAC;AAChD,CAAC;AAUD;;;;GAIG;AACH,SAAS,UAAU,CAAC,IAAa;IAC/B,MAAM,IAAI,GAAG,KAAK,CAAC,IAAI,EAAE,eAAe,CAAC,CAAC;IAC1C,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC;QAAE,OAAO,EAAE,CAAC;IACpC,OAAO,IAAI,CAAC,GAAG,CAAC,CAAC,GAAY,EAAE,EAAE,CAAC,CAAC;QACjC,EAAE,EAAE,KAAK,CAAC,KAAK,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC;QAC3B,IAAI,EAAE,IAAI,CAAC,KAAK,CAAC,GAAG,EAAE,MAAM,CAAC,CAAC;QAC9B,SAAS,EAAE,IAAI,CAAC,KAAK,CAAC,GAAG,EAAE,YAAY,CAAC,CAAC;QACzC,UAAU,EACR,OAAO,KAAK,CAAC,GAAG,EAAE,YAAY,CAAC,KAAK,QAAQ;YAC1C,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,GAAG,EAAE,YAAY,CAAC,CAAC;YAChC,CAAC,CAAC,IAAI;KACX,CAAC,CAAC,CAAC;AACN,CAAC;AAED;;;;;GAKG;AACH,KAAK,UAAU,UAAU,CACvB,MAAiB,EACjB,OAAuB;IAEvB,MAAM,MAAM,GAAG,MAAM,OAAO,CAAC,OAAO,CAAC,OAAO,CAAC,OAAO,CAAC,IAAI,EAAE,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;IACvE,MAAM,IAAI,GAAG,MAAM,OAAO,CAAC,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,IAAI,EAAE,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;IACtE,MAAM,UAAU,GAAG,KAAK,CAAC,MAAM,EAAE,sBAAsB,CAAC,CAAC;IACzD,OAAO;QACL,GAAG,MAAM;QACT,eAAe,EAAE,KAAK,CAAC,OAAO,CAAC,UAAU,CAAC,CAAC,CAAC,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC;QAClE,QAAQ,EAAE,KAAK,CAAC,KAAK,CAAC,IAAI,EAAE,aAAa,CAAC,CAAC;KAC5C,CAAC;AACJ,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,oBAAoB,CAClC,OAAuB;IAEvB,MAAM,OAAO,GAAG,OAAO,CAAC,OAAO,IAAI,aAAa,CAAC;IAEjD,OAAO,KAAK,EAAE,IAAY,EAAoB,EAAE;QAC9C,MAAM,IAAI,GAAG,MAAM,OAAO,CAAC,OAAO,CAAC,QAAQ,CAAC,OAAO,CAAC,IAAI,EAAE,IAAI,EAAE,OAAO,CAAC,CAAC,CAAC;QAC1E,MAAM,MAAM,GAAG,UAAU,CAAC,IAAI,CAAC,CAAC;QAEhC,MAAM,IAAI,GAAG,MAAM,OAAO,CAAC,GAAG,CAC5B,MAAM,CAAC,GAAG,CAAC,KAAK,EAAE,GAAc,EAAuB,EAAE;YACvD,IACE,GAAG,CAAC,UAAU,KAAK,IAAI;gBACvB,CAAC,qBAAqB,CAAC,QAAQ,CAAC,GAAG,CAAC,UAAU,CAAC,EAC/C,CAAC;gBACD,OAAO,EAAE,GAAG,GAAG,EAAE,eAAe,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,EAAE,CAAC;YACrD,CAAC;YACD,OAAO,UAAU,CAAC,GAAG,EAAE,OAAO,CAAC,CAAC;QAClC,CAAC,CAAC,CACH,CAAC;QAEF,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,MAAM,CAAC,MAAM,KAAK,OAAO,EAAE,CAAC;IACtD,CAAC,CAAC;AACJ,CAAC"}