@unbrained/pm-cli 2026.7.8 → 2026.7.10

package/docs/AGENT_GUIDE.md

@@ -116,9 +116,12 @@ pm release <item-id>
 | Open work only | `pm search "<keywords>" --status open` (drops closed-history noise; did-you-mean on typos) |
 | Scope search like list | `pm search "<keywords>" --type Task --assignee <name> --parent <id>` (full `pm list` filter parity) |
 | Items changed since last window | `pm list-all --updated-after <prev-run-ISO> --brief` (relative `-2h`/`-7d` also work) |
+| Open items changed today | `pm list-open --today --brief` (local-midnight shorthand; mutually exclusive with `--updated-after`) |
+| Items changed recently | `pm list-all --recent --brief` (last seven days; mutually exclusive with `--updated-after`) |
 | Single item | `pm get <id>` |
 | Full machine payload | `pm get <id> --full --json` |
 | Command flags | `pm <command> --help --json` |
+| Command intent map | `pm contracts --summary --json` (one command plus terse intent per row; use before command-scoped contracts) |
 | Low-noise machine contracts | `pm contracts --command <command> --flags-only --json` |
 | Semantic index refresh | `pm reindex --mode semantic --progress` (stale-first by default; add `--full` to force full rebuild; requires the `search-advanced` package) |
 | Timeline | `pm activity --id <id> --limit 20` |

package/docs/COMMANDS.md

@@ -7,6 +7,7 @@ Tracked implementation updates: [pm-52eh](../.agents/pm/features/pm-52eh.toon),
 ```bash
 pm <command> --help
 pm <command> --help --json
+pm contracts --summary --json
 pm contracts --command <command> --flags-only --json
 ```
 
@@ -15,7 +16,7 @@ pm contracts --command <command> --flags-only --json
 - Prefer `pm context`, `pm search`, and narrow list commands before mutation.
 - Prefer TOON for reading and `--json` for strict parsing.
 - Use the [guide topic map](README.md#guide-topic-map) when optional `pm guide` local docs routing is needed.
-- Use `pm contracts` for machine clients.
+- Use `pm contracts --summary --json` for the cheapest command map, then narrow with command-scoped contracts.
 - Every mutation writes history.
 
 Tracked documentation work: [pm-u9d0](../.agents/pm/epics/pm-u9d0.toon).
@@ -49,6 +50,8 @@ Tracked documentation work: [pm-u9d0](../.agents/pm/epics/pm-u9d0.toon).
 ```bash
 pm init
 pm init --defaults --with-packages
+pm init --workspace ./new-project --defaults
+pm init ./sandbox-tracker --defaults
 pm init --agent-guidance status
 pm init --agent-guidance add
 pm config project list
@@ -57,6 +60,7 @@ pm telemetry status
 ```
 
 `pm init` creates `.agents/pm`. `pm health --check-only --summary --json` gives the smallest machine-readable health gate without refreshing optional search artifacts.
+Use `pm init --workspace <dir>` when `<dir>` is a project root; it creates `<dir>/.agents/pm`. A path-like positional remains the advanced tracker-root form and writes tracker files directly at that path. Both explicit target forms return `target.mode`, `target.tracker_root`, and tracker-scoped executable `next_steps` so agents can run the suggestions from any working directory.
 `pm init --agent-guidance ask` is the default behavior: prompt in TTY only when AGENTS/CLAUDE guidance is missing and no decline is recorded.
 Use `--agent-guidance add` to write guidance, `--agent-guidance skip` to persist a decline without writing, and `--agent-guidance status` to inspect guidance state.
 Use `--with-packages` for one-step agent setup when bundled package commands should be active immediately.
@@ -77,6 +81,7 @@ pm upgrade --cli-only --repair
 ```
 
 `pm install` and `pm package` are the preferred package-first workflow. `pm package` and `pm extension` bare invocations default to `--explore` so agents can list installed packages without remembering an action flag. `pm install '*'`, shell-expanded `pm install *`, and `pm install all` install bundled first-party packages. `pm extension` remains as a compatibility command for direct extension lifecycle operations.
+Install output includes a light `verification` summary with target tracker root, activation state, registered commands/actions/item types, and an `ok|degraded` health verdict. Runtime activation failure sets the command result and process exit status to failure; inspect `activation_diagnostics` and `command_discovery.next_steps` for the exact recovery path.
 When package-owned commands are unavailable, usage guidance includes an install-ready retry (for example `pm install calendar`, `pm install search-advanced`, `pm install governance-audit`, or `pm install guide-shell`).
 
 ## Triage
@@ -129,6 +134,10 @@ pm list-all --updated-after 2026-06-04T15:18:32Z --brief
 pm list-open --updated-after=-2h --brief
 pm list-all --created-after=-7d --status open
 
+# Common list windows avoid date math (`list-open` keeps the view open-only).
+pm list-open --today --brief
+pm list-all --recent --brief
+
 # Search scoped to open work only (drops closed-history noise); statuses accept
 # all (no lifecycle restriction), open/closed/canceled aliases, or configured
 # ids, comma-separated, with a did-you-mean hint on typos.
@@ -141,6 +150,8 @@ pm search "reminder validation" --status all --limit 10
 pm search "calendar" --type Task --assignee alice --updated-after=-7d --parent pm-abcd
 ```
 
+Use only one updated-at window per list call: `--today`, `--recent`, and `--updated-after` are mutually exclusive. `--today` starts at local midnight; `--recent` is the same as `--updated-after=-7d`.
+
 `pm get`, `pm history`, and `pm search` also accept command-local `--format json|toon`. `--format json` is equivalent to the global `--json` flag for that command, while `--format toon` keeps the default agent-readable output. Do not combine global `--json` with `--format toon`.
 
 `list`/`search` full and fields projections echo full filter metadata. Compact mode emits only active filters (plus runtime schema filters when present) and omits the default projection/sorting/now trailer keys for lower token cost.
@@ -171,7 +182,7 @@ pm search "auth tag:area:auth status:open"        # query "auth" + --tag area:au
 pm search "ranking type:Task priority:1"          # query "ranking" + --type Task --priority 1
 ```
 
-Precedence: an **explicit `--flag` always wins** over a conflicting inline token. When both are supplied, the flag value is used and the result carries a `search_inline_filter_ignored:<field>:flag_takes_precedence` warning so the override is observable. On the CLI, an unquoted `tag:value` token is already rewritten to `--tag value` by argument normalization; the in-query parser additionally covers quoted multi-word queries and the `pm_search` MCP tool, where the whole query arrives as a single string. A query consisting solely of inline tokens (no keyword terms) is rejected — use `pm list` with the equivalent `--tag`/`--status`/`--type`/`--priority` flags for pure filtering.
+Precedence: an **explicit `--flag` always wins** over a conflicting inline token. When both are supplied, the flag value is used and the result carries a `search_inline_filter_ignored:<field>:flag_takes_precedence` warning so the override is observable. On the CLI, both unquoted inline tokens (`status:all scene`) and quoted multi-word queries (`"status:all scene"`) stay query input so the search parser can remove inline filters and preserve the remaining keywords. The same parser covers the `pm_search` MCP tool, where the whole query arrives as a single string. A query consisting solely of inline tokens (no keyword terms) is rejected — use `pm list` with the equivalent `--tag`/`--status`/`--type`/`--priority` flags for pure filtering.
 
 Pass `--highlight` to emit per-field matched-text snippets on each hit (off by default for token efficiency). Each matched field gets a `{ field, snippet }` entry under `highlights`, with the matching token runs wrapped in `«…»` and a `…` ellipsis where the field text was windowed:
 
@@ -413,6 +424,8 @@ Use `pm close <duplicate-id> --duplicate-of <canonical-id>` to close duplicates.
 
 `pm close` accepts short aliases for the common flags: `-m` (`--message`), `-r` (`--reason`), and `-d` (`--duplicate-of`). When `governance.require_close_reason` is enabled and no positional/`--reason` text is given, the close reason is derived from the next-best signal in priority order — explicit reason text, then `--duplicate-of` (`Duplicate of <id>`), then `--resolution` — so a single `pm close <id> --resolution "<summary>"` no longer hard-blocks. The resolution is still written to the item's `resolution` field.
 
+`pm create --blocked-by <id>` and `pm update --blocked-by <id>` keep the scalar `blocked_by` field as the latest/primary blocker for compatibility. When the value resolves to a real item, the command also appends a `blocked_by` dependency edge so `pm deps` and reverse dependency scans see the full blocker graph. Repeating `pm update --blocked-by` with a different blocker preserves the prior blocker edge and appends the new one; repeating the same blocker is deduplicated. Use `pm update <id> --unset blocked-by` to clear the scalar and all `blocked_by` dependency edges.
+
 When closing a blocker, `pm close` scans reverse `blocked_by` edges and auto-unblocks dependent items only when every resolvable blocker is now terminal. Each unblocked item is updated through the normal audited mutation path, gets an `unblock_note`, and the close result reports compact `auto_unblocked:<id>:resolved_blockers=<ids>` warnings. Items with another active blocker remain blocked.
 
 Over MCP the mutation tools (`pm_create`/`pm_update`/`pm_close`/`pm_run` append/update-many) are compact by default; pass `fullChangedFields=true` to restore the full `changed_fields` delta, or `idOnly=true` for single-item id/status output.
@@ -858,12 +871,14 @@ Invariants:
 
 ```bash
 pm contracts --json
+pm contracts --summary --json
 pm contracts --command create --flags-only --json
 pm contracts --action create --schema-only --json
 pm help create --json
 ```
 
 Agents should use runtime contracts instead of hard-coding flag lists. Contract output includes extension-provided command surfaces when active.
+Use `pm contracts --summary --json` first when bootstrapping in a tight context window; it emits one command and terse intent per row before the agent requests heavier command-specific flags or schemas.
 
 ## Completion
 

package/docs/EXTENSIONS.md

@@ -40,7 +40,9 @@ pm install kanban --project
 
 `pm install '*'`, `pm install all`, and shell-expanded `pm install *` are normalized to the same bundled install-all request. First-party package aliases come from each package manifest, with a fallback derived from the `packages/pm-*` directory name.
 
-External registry packages are installed by exact package name. If `npm:<name>` returns a registry 404, JSON error output includes `fallback_candidates` and `next_best_command`; unpublished first-party packages fall back to `pm install --project github.com/unbraind/<name>`. Install results include package-owned `command_paths`, `action_paths`, and `command_discovery`; agents should read `details.command_discovery.command_paths` and `details.command_discovery.help_commands` instead of guessing from the package name.
+External registry packages are installed by exact package name. If `npm:<name>` returns a registry 404, JSON error output includes `fallback_candidates` and `next_best_command`; unpublished first-party packages fall back to `pm install --project github.com/unbraind/<name>`. Install results include package-owned `command_paths`, `action_paths`, `command_discovery`, and a light `verification` block covering the target tracker, activation status, registered commands/actions/item types, and health verdict. Agents should consume those fields instead of guessing from the package name or immediately spending another invocation on doctor. A failed runtime activation returns `ok: false`, `activated: false`, a non-zero CLI exit, and actionable diagnostics; missing SDK resolution adds an explicit dependency recovery step.
+
+An explicit `--pm-path` scopes project installs to that tracker root, including extension files, managed state, settings, type-folder scaffolding, and verification output. This is the safe form for temporary package testing from inside another repository checkout.
 
 ```bash
 npm search "pm-cli pm-package"

package/docs/SDK.md

@@ -106,6 +106,14 @@ Command/action contract exports:
 - `PmClient` / `runAction` (high-level in-process action execution for custom tools, bots, CI, and embedded runtimes)
 - Typed read primitives on `PmClient`: `get`, `list`, `search`, `context`, `next`, `aggregate`, and `stats`
 - Read primitive option/result contracts: `GetOptions` / `GetResult`, `ListOptions` / `ListResult`, `SearchOptions` / `SearchResult`, `ContextOptions` / `ContextResult`, `NextOptions` / `NextResult`, `AggregateOptions` / `AggregateResult`, `StatsCommandOptions` / `StatsResult`
+- Context relevance primitives: `defaultScoreContextCandidates`, `scoreContextCandidates`, `scoreContextCandidatesWithActiveExtensions`, `evaluateContextRanking`, `runContextEvaluationScenario`, `runContextEvaluationCorpus`, and `summarizeContextEvaluationReports`
+- Context relevance contracts: `ContextRelevanceCandidate`, `ContextRelevanceSignals`, `ContextRelevanceScorer`, `ContextRelevanceReport`, `ContextEvaluationReader`, `ContextEvaluationScenario`, `ContextEvaluationScenarioReport`, `ContextEvaluationThresholds`, and `ContextEvaluationCorpusReport`
+- Typed annotation and relationship primitives on `PmClient`: `comments`, `notes`, `learnings`, `files`, `filesDiscover`, `docs`, `deps`, and `append`
+- Annotation and relationship option/result contracts: `CommentsCommandOptions` / `CommentsResult`, `NotesCommandOptions` / `NotesResult`, `LearningsCommandOptions` / `LearningsResult`, `FilesCommandOptions` / `FilesResult`, `FilesDiscoverOptions` / `FilesDiscoverResult`, `DocsCommandOptions` / `DocsResult`, `DepsCommandOptions` / `DepsResult`, `AppendCommandOptions` / `AppendResult`
+- Typed customization primitives on `PmClient`: `init`, `config`, `schema`, `schemaList`, `schemaShow`, `schemaAddType`, `schemaRemoveType`, `schemaAddStatus`, `schemaRemoveStatus`, `schemaAddField`, `schemaRemoveField`, `schemaListFields`, `schemaShowField`, `schemaApplyPreset`, `schemaInferTypes`, `schemaShowStatus`, `profile`, `profileList`, `profileShow`, `profileApply`, and `profileLint`
+- Customization primitive option/result contracts: `InitCommandOptions` / `InitResult`, `ConfigCommandOptions` / `ConfigResult`, `SchemaSubcommand` / `SchemaResult` / `SchemaInspectResult`, `SchemaListResult`, `SchemaShowResult`, `SchemaAddTypeResult`, `SchemaRemoveTypeResult`, `SchemaAddStatusResult`, `SchemaRemoveStatusResult`, `SchemaAddFieldResult`, `SchemaRemoveFieldResult`, `SchemaListFieldsResult`, `SchemaShowFieldResult`, `SchemaApplyPresetResult`, `SchemaAddTypeInferResult`, `SchemaShowStatusResult`, `ProfileSubcommand` / `ProfileResult`, `ProfileListResult`, `ProfileShowResult`, `ProfileApplyResult`, `ProfileLintResult`
+- Typed governance and maintenance primitives on `PmClient`: `validate`, `health`, and `gc`
+- Governance and maintenance option/result contracts: `ValidateCommandOptions` / `ValidateResult`, `RunHealthOptions` / `HealthResult`, `GcCommandOptions` / `GcResult`
 - Typed package and extension lifecycle primitives on `PmClient`: `extension`, `extensionList`, `extensionActivate`, `extensionDeactivate`, `package`, `packageList`, `packageInstall`, `packageUninstall`, `packageDoctor`, `packageManage`, `packageDescribe`, `packageReload`, `packageCatalog`, `packageActivate`, `packageDeactivate`, and `upgrade`
 - Lifecycle primitive option/result contracts: `ExtensionCommandOptions` / `ExtensionCommandResult`, `PackageCommandOptions` / `PackageCommandResult`, `UpgradeCommandOptions` / `UpgradeResult`
 - `PM_CORE_COMMAND_NAMES`
@@ -450,6 +458,14 @@ const open = await pm.list({ status: "open", limit: "20" });
 const recommendation = await pm.next({ readyOnly: true });
 const grouped = await pm.aggregate({ groupBy: "status", count: true });
 const stats = await pm.stats({ metadataCoverage: true });
+await pm.comments(created.item.id, { add: "Investigation context captured." });
+await pm.files(created.item.id, { add: ["src/index.ts"], note: "entrypoint" });
+await pm.docs(created.item.id, { add: ["docs/SDK.md"], note: "authoring reference" });
+const graph = await pm.deps(created.item.id, { format: "graph" });
+const types = await pm.schemaList();
+const profiles = await pm.profileList();
+const validation = await pm.validate({ checkResolution: true });
+const health = await pm.health({ checkOnly: true, summary: true });
 const packages = await pm.packageList({ project: true });
 const doctor = await pm.packageDoctor({ project: true, isolated: true });
 const plannedUpgrade = await pm.upgrade(undefined, { dryRun: true, cliOnly: true });
@@ -501,6 +517,105 @@ payload shape with vocabulary-appropriate SDK signatures. `UpgradeResult` is the
 same structured payload rendered by the CLI, so embedded tools can own their
 presentation layer while sharing pm's package/install/doctor semantics.
 
+Annotation and relationship convenience methods turn "project management =
+context management" into a typed SDK surface. Use `pm.comments`, `pm.notes`,
+`pm.learnings`, `pm.files`, `pm.docs`, `pm.deps`, and `pm.append` when an
+embedded agent, package, or custom UI needs to add durable rationale, link
+changed files/docs/tests, or inspect the item graph. `pm.filesDiscover` exposes
+the same file-candidate discovery used by the CLI, so a custom tool can present
+reviewable link suggestions instead of scraping git output itself.
+
+Customization convenience methods are the SDK baseline for project-specific pm
+tools. `pm.init` stages a tracker, `pm.config` reads/writes settings,
+`pm.schema*` methods manage types/statuses/fields/presets, and `pm.profile*`
+methods list, inspect, apply, and lint project archetypes. These helpers let a
+package or app construct an opinionated project-management experience while
+staying on the same schema/profile primitives the CLI and MCP use.
+`pm.init` accepts `workspace` to initialize `<workspace>/.agents/pm`; path-target
+calls retain tracker-root semantics. `InitResult.target` exposes the resolved
+mode, tracker root, and optional workspace root, while every explicit-target
+`next_steps` command carries `--pm-path` so embedded tools can display runnable
+recovery without depending on the caller's current directory.
+
+Package install results include `details.verification`, a light doctor-equivalent
+projection of activation, registered commands/actions/item types, target tracker
+root, and health verdict. Treat `ok: false` or `verification.status: "degraded"`
+as an install failure even when files were copied successfully; use
+`activation_diagnostics` and `command_discovery.next_steps` for remediation.
+
+Governance and maintenance convenience methods expose the operational floor a
+custom PM host should run before it trusts or publishes tracker state.
+`pm.validate` checks resolution/history invariants, `pm.health` performs
+read-only diagnostics, and `pm.gc` runs dry-run or explicit cleanup paths through
+the same bounded maintenance engine as the CLI. Prefer these typed calls over
+shelling out when building CI, editor integrations, or long-running agent
+runtimes.
+
+### Context relevance and evaluation
+
+Tracked by [pm-4k6b](../.agents/pm/features/pm-4k6b.toon),
+[pm-h3no](../.agents/pm/tasks/pm-h3no.toon), and
+[pm-atfm](../.agents/pm/features/pm-atfm.toon).
+
+`pm context` and `pm next` share the public deterministic relevance model.
+Candidate order is the structural baseline; normalized metadata signals add
+explainable weighted contributions. Package authors can call
+`scoreContextCandidates` with a scorer callback, while installed extensions can
+register the governed `context_relevance` service override. A malformed or
+throwing override degrades to the deterministic default and emits an
+`extension_context_relevance_invalid_result` warning instead of breaking the
+read path.
+
+Use `--explain-ranking --json` on `pm context` or `pm next` to include the model,
+available signals, baseline rank, final rank, score, and per-signal
+contributions. Explanation data is opt-in so default agent output stays bounded.
+
+Custom tools can evaluate the same behavior without shelling out:
+
+```ts
+import {
+  PmClient,
+  runContextEvaluationCorpus,
+  type ContextEvaluationScenario,
+  type ContextEvaluationThresholds,
+} from "@unbrained/pm-cli/sdk";
+
+const pm = new PmClient({
+  pmRoot: ".agents/pm",
+  author: "context-quality-ci",
+});
+
+const scenarios: ContextEvaluationScenario[] = [
+  {
+    id: "returning-agent",
+    surface: "context",
+    options: { limit: "5" },
+    judgments: { "pm-current": 3, "pm-support": 2 },
+    required_ids: ["pm-current"],
+    continuity_ids: ["pm-current", "pm-support"],
+    token_budget: 1200,
+    rationale: "Resume claimed work with its supporting context.",
+  },
+];
+
+const thresholds: ContextEvaluationThresholds = {
+  ndcg: 0.9,
+  reciprocal_rank: 0.9,
+  required_recall: 1,
+  continuity_coverage: 1,
+  token_budget_adherence: 1,
+};
+
+const report = await runContextEvaluationCorpus(scenarios, pm, thresholds);
+if (!report.passed) throw new Error(report.failures.join(", "));
+```
+
+The evaluator calls only the public `context()` / `next()` reader contract. It
+scores nDCG, reciprocal rank, required-item recall, returning-agent continuity,
+and deterministic `ceil(UTF-8 JSON bytes / 4)` token-budget adherence. Reports
+retain attribution only for served items, while token accounting measures the
+normal packet without the opt-in ranking explanation.
+
 `PmClient` and `runAction` share the same process-wide extension activation
 queue as MCP. Calls from one process are serialized across extension load,
 activation, dispatch, cleanup, and deactivate so active extension registries stay

package/docs/TESTING.md

@@ -2,7 +2,7 @@
 
 This page describes safe local tests, linked tests, coverage, and release-readiness checks.
 
-Tracked implementation updates: [pm-52eh](../.agents/pm/features/pm-52eh.toon), [pm-mcxr](../.agents/pm/issues/pm-mcxr.toon), [pm-u42x](../.agents/pm/issues/pm-u42x.toon).
+Tracked implementation updates: [pm-52eh](../.agents/pm/features/pm-52eh.toon), [pm-mcxr](../.agents/pm/issues/pm-mcxr.toon), [pm-u42x](../.agents/pm/issues/pm-u42x.toon), [pm-atfm](../.agents/pm/features/pm-atfm.toon), [pm-xmp5](../.agents/pm/tasks/pm-xmp5.toon).
 
 ## Agent Quick Context
 
@@ -109,6 +109,45 @@ Fixture authoring notes:
 
 CI currently runs this gate in advisory mode (`continue-on-error: true`), so failures do not block merges by default; treat failing nDCG as a quality signal to investigate, not as a silent ignore.
 
+## Context Quality Evaluation
+
+The required context relevance gate proves that `pm context` and `pm next`
+assemble the right bounded working set, not only that search returns relevant
+documents.
+
+Fixture and baseline sources:
+
+- `tests/context-eval/golden-scenarios.json` — reviewable scratch,
+  real-shaped, synthetic-scale, and returning-agent continuity judgments.
+- `tests/context-eval/baseline.json` — committed aggregate and per-scenario
+  metrics from the accepted structural/scorer behavior.
+
+Run the required gate locally:
+
+```bash
+pnpm build
+pnpm quality:context-eval
+```
+
+The gate creates isolated temporary trackers through `PmClient`, reads them only
+through the public `context()` / `next()` SDK primitives, and reports nDCG,
+reciprocal rank, required-item recall, continuity coverage, token-budget
+adherence, and served-item signal attribution. It fails when an explicit corpus
+threshold is missed or any aggregate metric regresses below the committed
+baseline.
+
+When a deliberate ranking change improves or intentionally redefines the golden
+judgments, review the scenario-level diff first, then refresh the baseline:
+
+```bash
+pnpm quality:context-eval -- --update
+pnpm quality:context-eval
+```
+
+Do not update the baseline merely to make CI green. Change judgments and
+rationales in the corpus when product intent changes, and commit the corpus,
+baseline, scorer tests, and SDK documentation together.
+
 ## Linked Tests
 
 Add tests to the item that owns the work:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@unbrained/pm-cli",
-  "version": "2026.7.8",
+  "version": "2026.7.10",
   "description": "Git-native project management CLI for humans and agents.",
   "type": "module",
   "packageManager": "pnpm@11.10.0",
@@ -80,7 +80,9 @@
     "lint:complexity:baseline": "eslint . --suppress-rule complexity",
     "lint:duplicates": "jscpd --config .jscpd.json",
     "lint:codefactor": "pnpm quality:static",
-    "quality:static": "node scripts/release/static-quality-gate.mjs --min-docstring-coverage 92.93 --min-exported-docstring-coverage 84.41 --min-member-docstring-coverage 13.655",
+    "quality:static": "pnpm build && node scripts/release/static-quality-gate.mjs --min-docstring-coverage 92.93 --min-exported-docstring-coverage 84.41 --min-member-docstring-coverage 13.655 && node scripts/release/token-budget-gate.mjs",
+    "quality:token-budget": "node scripts/release/token-budget-gate.mjs",
+    "quality:context-eval": "node scripts/release/context-eval-gate.mjs",
     "quality:docs-skills": "node scripts/release/docs-skills-gate.mjs",
     "quality:docs-links": "node scripts/release/docs-skills-gate.mjs --links-only",
     "contracts:update": "node scripts/contracts-snapshot.mjs --update",

package/dist/cli-bundle/chunks/append-CDPAYYSB.js

@@ -1,11 +0,0 @@
-import {
-  runAppend
-} from "./chunk-GSQVQINP.js";
-import "./chunk-WW4E2DC3.js";
-import "./chunk-CGDUIPJL.js";
-import "./chunk-BPJ5NYSJ.js";
-import "./chunk-2BVD4ZD2.js";
-export {
-  runAppend
-};
-//# sourceMappingURL=append-CDPAYYSB.js.map