@agentskit/doc-bridge 1.11.0 → 1.11.1

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # Changelog
 
+## 1.11.1
+
+### Patch Changes
+
+- faf29f5: Stop reporting a path an ignore rule rescues as unreproducible.
+  
+  `git check-ignore --verbose` emits a record for every path that *matched* a rule, including the path
+  a `!` negation rescues — and such a path is precisely one Git does not ignore. The reproducibility
+  check read the record without reading the pattern, so `dist/*` plus `!dist/keep.js` reported
+  `dist/keep.js` as a reason the index could not be rebuilt from a clean checkout. The opposite of
+  what the rule says, stated confidently.
+  
+  The window is narrow: `check-ignore` stops reporting a path once it is committed, and a path rescued
+  by a negation is usually committed, which is the point of rescuing it. It shows up while such a path
+  is still untracked — a file added but not yet committed.
+  
+  Found by turning the new `index-reproducible` gate on in this repository, which had to add
+  `!.doc-bridge/index.json` to its own `.gitignore` to commit the index the gate verifies.
+
 ## 1.11.0
 
 ### Minor Changes

package/README.md

@@ -297,19 +297,23 @@ gates without silently rebuilding them. It rejects non-exact package versions.
 See the [Marketplace guide](docs/MARKETPLACE.md).
 
 The guide is pinned to the published stable Action release `v1.7.45`; the
-checked-in package version is `1.8.0`.
+checked-in package version is `1.11.1`.
 
 Coverage is repository-specific. Run `ak-docs doctor --badge` locally to emit
 current handoff and human-bridge badges, or `pnpm coverage:badge` in CI; this
 README intentionally avoids publishing a stale static percentage.
 
-Or locally:
+Or locally, as two steps rather than one, because they answer different questions:
 
 ```bash
-ak-docs index && ak-docs gate run
+ak-docs index     # after changing docs or config — then review and commit the result
+ak-docs gate run  # verifies the committed index, which is what CI verifies
 ```
 
-Gate fails with `Index is stale. Run: ak-docs index` — same check in CI annotations.
+Chaining them (`index && gate run`) cannot report a stale index: it gates an artifact written a
+second earlier against a rebuild of the same tree. The gate's value is that the committed index
+and the repository agree, so run it the way CI does, against what is committed. It fails with
+`Index is stale. Run: ak-docs index` — the same check, and the same annotation, as in CI.
 
 ## Product surface
 

package/action.yml

@@ -20,7 +20,7 @@ inputs:
   package-version:
     description: Exact @agentskit/doc-bridge npm version (kept in sync with this Action release)
     required: false
-    default: '1.11.0'
+    default: '1.11.1'
 
 runs:
   using: composite

package/dist/cli/program.js

@@ -4062,7 +4062,7 @@ var buildLookup = (config, packages, corpus, indexOutFile, humanDocs = {}, root
 };
 
 // src/version.ts
-var PACKAGE_VERSION = "1.11.0";
+var PACKAGE_VERSION = "1.11.1";
 
 // src/index-builder/capabilities.ts
 var renderCapabilitiesJson = (config, index, paths) => {
@@ -8065,7 +8065,7 @@ var checkIndexReproducibility = (root, indexPath, paths) => {
   const ignored = [];
   for (let index = 0; index + 3 < fields.length; index += 4) {
     const [source, line, pattern, path] = [fields[index], fields[index + 1], fields[index + 2], fields[index + 3]];
-    if (!path) continue;
+    if (!path || pattern?.startsWith("!")) continue;
     ignored.push({ path, rule: `${source ?? "?"}:${line ?? "?"}:${pattern ?? "?"}` });
   }
   return { checked: true, ignored: ignored.sort((left, right) => left.path.localeCompare(right.path)) };