@rackbops/ac-agent 2.0.0-alpha.39 → 2.0.0-alpha.41

package/data/README.md

@@ -7,11 +7,11 @@ as text (see `../text-plugin.mjs`).
 
 A byte-identical copy of `artifact-console/data/Get-ToolchainInventory.ps1` from
 [`Rackbops/artifacts-console`](https://github.com/Rackbops/artifacts-console) (the 1.x app), pinned
-to commit `7280ae6`:
+to commit `8e33836`:
 
-- 1,397 lines, 77,956 bytes
+- 1,826 lines, 101,592 bytes
 - LF line endings, no BOM, ASCII-only
-- sha256 `28db241b5aa42202c329c115a0de5a28049b04a421d980f9ec463e109e9d0912`
+- sha256 `76b6a712c27f34ea9dc4cec230fc7107fd3c88720e8f24c0c2c933f2a685fea0`
 
 The hash is platform-stable because both repos' `.gitattributes` normalize this file to
 `text=auto eol=lf`, and `toolchain-inventory.test.ts` asserts the embedded text hashes to the value
@@ -25,16 +25,20 @@ the embedding/drift-guard tests (`toolchain-inventory.test.ts`) -- they also pin
 catalog names and schema-version literal, so a re-vendor whose shape moved is caught there, not
 discovered on a card.
 
-**Provenance note (52b, landed 2026-09-13):** `Rackbops/artifacts-console`'s `main` had moved to
-`1e7cfe5` by the time this landed -- 424 lines away from the `7280ae6` pin (`git diff --stat 7280ae6
-1e7cfe5 -- artifact-console/data/Get-ToolchainInventory.ps1`: 414 insertions, 10 deletions). The
-difference is one self-contained feature, a tools-site page-data push (issues #636/#637: seven new
-functions -- `Resolve-ToolchainScpExe`, `Get-ToolchainSidecarFiles`, `New-ToolchainPageManifest`,
-`Resolve-ToolchainGhExe`, `New-ToolchainFiledSnapshot`, `Invoke-ToolchainPageDataPush`,
-`Test-ToolchainPageDataChanged` -- plus a new optional `-PageDataTarget` parameter and a
-null-guard around `$env:SystemRoot` in `Resolve-ToolchainSshExe`) -- none of it touches
-`Publish-ToolchainReport` (the report + sidecar writer) or the local `-OutFile -NoRender` path this
-agent invokes, and the new main-flow block only runs when `-PageDataTarget` is set, which the agent
-never passes. So `7280ae6` and `1e7cfe5` are behaviorally identical for this agent's invocation; the
-pin was kept rather than churned. Re-pinning to a newer 1.x commit is a fleet-pass decision, not
-something this PR does on its own.
+**Provenance note (Tooling#721 F3, landed 2026-09-29):** re-pinned from `7280ae6` to `8e33836`
+(`git diff --stat 7280ae6 8e33836 -- artifact-console/data/Get-ToolchainInventory.ps1`: 456
+insertions, 27 deletions across two 1.x changes -- the #716 JSON-sidecar-per-report work the prior
+pin already predated having actually landed by then is folded in here too, plus
+artifacts-console#742's own #721 F1: a `## Containers` pass, on a Linux side with `docker` on PATH,
+recording each running container's image digest, best-effort package list and catalogued tools.
+That entire feature lives in the SSH/WSL Linux-probing path (`Invoke-RemoteToolchainInventory`, and
+the bash probe text `New-ToolchainProbeScript` builds -- the same probe both the SSH and WSL
+transports run). This agent's own invocation never sets `-SshTargets`, so the SSH leg never runs at
+all; `-WslDistro` is left at the script's own default (`Ubuntu`), so the WSL leg still runs exactly
+as it always has, and if the deploying MACHINE happens to have a registered `Ubuntu` WSL distro with
+`docker` on ITS path, that WSL side would pick up the new Containers section too -- same as any
+other WSL-side tool this script has always probed, not a new risk this sync introduces. What this
+re-vendor changes for a machine with no such WSL/docker setup (the realistic case for the 2.0 fleet
+today) is nothing. Confirmed by `toolchain-inventory.test.ts`'s existing suite passing unchanged (no
+test needed updating for this sync) -- the script's catalog and schema-version literal, which that
+suite pins directly, are both identical to before.