Skip to main content
Welcome. This site supports keyboard navigation and screen readers. Press ? at any time for keyboard shortcuts. Press [ to focus the sidebar, ] to focus the content. High-contrast themes are available via the toolbar.
serard@dev00:~/cv

Sources and Verification

The article is accompanied by runnable scripts and an independent provider. Verification uses isolated configuration and disposable Git repositories. It does not alter the user's pumps configuration, profile or working repository.

Reproduce the checks

From this series directory, set the actual engine path:

$library = 'C:/code/FrenchExDev/FrenchExDev_i2/PoSh/FrenchExDev/FrenchExDev.OutputPumps.PoSh'
./scripts/Collect-Sources.ps1 -LibraryRoot $library
./scripts/Test-Provider.ps1 -LibraryRoot $library
./scripts/Invoke-Examples.ps1 -LibraryRoot $library

PowerShell 7.4+ Core and the installed Git and ripgrep tools are required. Configuration uses powershell-yaml. The provider suite uses Pester 6.2.0 with experimental parallelism and its unused registry fixture disabled. The runners reuse the checkout's cached modules when available; they do not install anything.

To refresh the RTK manifest from the pinned commit, run Collect-Sources.ps1 -RefreshRtk with network access. The default local collection updates the engine/provider manifest without accessing the network.

Runnable artifacts

File Purpose
Collect-Sources.ps1 Hash current engine/provider/DevPoSh sources and optionally retrieve pinned RTK source hashes.
Initialize-Examples.ps1 Activate only the four walkthrough providers using isolated YAML and inventory.
New-Walkthrough.ps1 Generate the 2 KiB main task caller or the reuse caller.
Invoke-FreshProcess.ps1 Initialize and execute the walkthrough in a separate Core process.
Test-Provider.ps1 Run the provider's parser and contribution suite.
Invoke-Examples.ps1 Entry point for the complete disposable execution.
Invoke-Verification.ps1 Fixture setup, assertions, task-budget cases and evidence regeneration.
Build-SupportPages.ts Render the provider's three supporting Markdown documents with the existing site renderer, outside the chapter TOC.
Verify-Navigation.cjs Browser checks for eight children, expansion/collapse, chapter pages and linked artifacts.
GitWorktrees provider Manifest, bounded reducer, contribution, fixtures and generated discovery documents.

The task callers are generated .ps1 files and remove themselves after execution. The committed generator remains reproducible. External values use ArgumentList; task blocks do not depend on a transported closure.

Source manifests

output-pumps-snapshot.json records current local paths, provider manifests, command identifiers and SHA-256 hashes for the engine, five existing providers and optional DevPoSh setup.

rtk-snapshot.json pins the RTK repository revision, collection time, source links and content hashes. The comparison relies on its README, contribution guide, command and filter documentation, Git handler, recovery code and savings explanation. It is a source inspection, not an RTK execution benchmark.

Git's worktree parsing contract comes from the official worktree manual (ouvre dans une nouvelle fenêtre). Other tool formats are grounded in their provider software sheets and primary documentation, including ripgrep's guide (ouvre dans une nouvelle fenêtre), Podman ps (ouvre dans une nouvelle fenêtre) and pnpm list (ouvre dans une nouvelle fenêtre).

Execution evidence

Evidence What is checked
verification.json Named assertions and runner outcome.
provider-tests.json Parser fixtures and isolated session contribution.
registration.json Documentary validation and catalogue generation.
scaffold.json Execution of the actual New-OPumperModule generator.
walkthrough.json One 2 KiB task, three steps and the requested projection.
reuse.json A second request using the same registered provider.
measurements.json Separate output-byte, caller-generation, execution and retry observations; unmeasured authoring and RTK costs are explicit.
fresh-process.json Separate process, isolated initialization and one generated task result.
streaming-preview.json Exact ripgrep count with one retained line.
malformed-stream.json Parser failure leaves the analysis uncertified.
native-timeout.json Actual process timeout remains distinct.
budget-assigned-failures.json Twenty assigned failures, one document, 1 KiB budget.
budget-late-failure.json Failure after nineteen truncated previews.
budget-timeout.json Timeout status retained under the aggregate budget.
budget-duplicate-envelopes.json Repeated envelope emission does not double-count steps.

The checks assert meaningful provider fields, unusual paths, bare/detached states, malformed records, unsupported arguments and native failures. They verify bounded reducer storage, complete counts with small previews, unknown counts after incomplete analysis, exactly one JSON document and accurate twenty-step counters with explicit diagnostic omissions.

Fixture paths in execution evidence identify disposable directories. They are not stable user configuration.

Site verification

Use this repository's existing scripts from its root:

pnpm --silent run validate:links --only=blog/rtk-vs-pumps --json
pnpm --silent run build:toc

Rebuild the index, all eight chapters and pages embedding the sidebar with the existing static builder. Then run the supporting-document renderer and the browser check, using the repository's existing static server:

pnpm --silent exec tsx content/blog/rtk-vs-pumps/scripts/Build-SupportPages.ts
pwsh -NoProfile -File content/blog/rtk-vs-pumps/scripts/Prune-ObsoleteArtifacts.ps1
pnpm --silent run work serve --static --port 4019
node content/blog/rtk-vs-pumps/scripts/Verify-Navigation.cjs

The browser check verifies the rendered parent has eight children, collapse and expansion affect the child container, and chapter pages and linked artifacts load. It writes navigation.json. A corrected Markdown parent alone is insufficient evidence that already generated HTML has been refreshed.

The article does not include an engine enhancement, a deployment, or a measured RTK-versus-Pump-Me performance result. Its evidence establishes the executed provider and task contract.

Previous: RTK and Pump-Me · Series index

⬇ Download