---

summary: "Context-packer code-provider migration and validation." read_when:

• "Working on the ripwire-only integration." system4d: container: "Read-only context-packer package in pi-extensions." compass: "Remove the old code provider without implied replacement consent." engine: "Plan, bound, verify, and report explicit omissions." fog: "Package verification is not proof of model task performance."

---

@tryinget/pi-context-packer

Ripwire is the only code provider. Automatic selection is not approved; use explicit providers.ripwire: "required" after operator provisioning. Set PI_CONTEXT_PACKER_RIPWIRE_DISABLED=1 to block all ripwire invocation. See rollout and evidence.

Read-only context planning and packet assembly for Pi. Instructions, Markdown/docs-list, Git posture, and session metadata remain available. Prompt Vault, AK, and FCOS remain owner-routed. Ripwire is available for explicit, read-only code discovery:

{"objective":"Find the provider capability checks","providers":{"ripwire":"required"}}

Filename seeds are optional. Known symbol/path seeds are ranking hints, not scope restrictions; hints that exceed the query limit are reported as omissions. auto does not yet activate ripwire. The operator must provision the supported executable and set PI_CONTEXT_PACKER_RIPWIRE_BIN to its absolute path. See the stack contract for the pinned build, digest, approved-corpus policy, and Linux support boundary. The package never installs a tool or changes agent settings. Ordinary Pi read/search remains available when discovery is unavailable or insufficient.

Start using it from source

Supported acquisition platform: Linux. macOS and Windows currently refuse code acquisition; installing on those systems does not remove that boundary. Tested Pi host line: 0.84.3 (historical). The 0.84.4 development baseline is not yet tested. Automatic provider selection remains off.

From an updated pi-extensions checkout, install the package into an existing Pi:

pi install "$PWD/packages/pi-context-packer"

Provision ripwire from the pinned source revision (a C++23 compiler, CMake >=3.24 and Git are required). This explicit operator step does not install upstream agent skills:

# Run in a directory where a new ripwire-pinned checkout may be created.
git clone https://github.com/redhat-et/ripwire.git ripwire-pinned
git -C ripwire-pinned checkout --detach 93c8edaafdb5499e89939cc2cebd0429e278e86f
cmake -S ripwire-pinned -B ripwire-pinned/build -DCMAKE_BUILD_TYPE=Release
cmake --build ripwire-pinned/build --target ripwire -j2
export PI_CONTEXT_PACKER_RIPWIRE_BIN="$(realpath ripwire-pinned/build/ripwire)"
export PI_CONTEXT_PACKER_RIPWIRE_SHA256="$(sha256sum "$PI_CONTEXT_PACKER_RIPWIRE_BIN" | cut -d' ' -f1)"

The digest above records the bytes you built from the reviewed source; it is not an independent upstream attestation. Use these environment variables in the shell that starts Pi. If the binary is already provisioned, export its absolute path and approved digest instead. No automatic download or fallback installation occurs.

Keep TMPDIR (when set) outside the target repository. Source-local temporary storage is refused before snapshot creation, including aliases pointing inside it.

Start a fresh Pi from the target repository with those variables set. In Pi, run:

/ripwire-context Find where provider execution eligibility is decided

The prompt explicitly asks for the context_pack tool and the ripwire provider. It is not an always-on map injection. An already-running Pi needs /reload after package installation; environment variables changed in another shell require a new Pi process. Failure messages are actionable omissions, not a request to authorize another backend. Normal Pi tools handle edits and validation separately.

Migration

SCI is removed from this package's runtime, routing, prompts, and active experiments. Remove providers.sci and its provider budget from saved requests; obsolete configuration is rejected, never silently mapped to permission to execute another tool. No installed software or user .ontology data is removed. Historical code and evidence are archived at docs/archive/pi-context-packer/pre-ripwire in the monorepo, outside this package artifact. Other independently owned monorepo packages are not removed by this migration.

Input and workflow safeguards

JavaScript/TypeScript module variants .mjs, .cjs, .mts, and .cts are included alongside .js and .ts. Both tools describe discovery, expansion, refresh and stale-selection recovery; /ripwire-context is a prompt helper, not a nested tool. After changing source, rediscover before expanding an old selection. Always inspect error/omission signals; retrieval remains heuristic and automatic selection stays off.

Budget values must be non-negative safe integers. Invalid fields are rejected rather than replaced with larger defaults. An explicit reserve is never lowered; a reserve that consumes the budget prevents code acquisition, including with a host tokenizer. The installed result contract identifies this revision as ripwire-context-v2.

Verification

Run the canonical gate from the monorepo root:

bash scripts/package-quality-gate.sh ci packages/pi-context-packer

Run npm run release:check from this package for isolated installed-Pi verification. The quick release check skips Pi smoke and is not proof of activation. npm run dogfood:gate -- --gate RW-01 --candidate-sha <SHA> --output-dir <EXTERNAL_DIR> checks an exact clean candidate and emits an independently rerunnable receipt. An offline registered-tool smoke is not a model-task benchmark or independent authorship.

The package does not apply edits, run validation commands, install tools, or move task authority.

Focused source expansion

After discovery, call context_pack with providers.ripwire: "required" and code: { mode: "expand", selection: { path, name, line, contentSha256 } }. Copy the repo-relative path, literal symbol, line and source SHA-256 from the discovery packet. The adapter rechecks source content and requires exactly one matching body; a stale hash, mismatched line or ambiguous definition refuses instead of guessing. Body and ancillary-context omissions are explicit. Redacted output is not editable source.

Optional private cache

PI_CONTEXT_PACKER_RIPWIRE_CACHE_ROOT is an operator setting, not a model argument. Use an absolute, user-owned mode-0700 directory outside source repositories with no symlink ancestors. Leave it unset to disable caching. Entries are mode 0600 and may contain source-derived text. Each request revalidates binary and corpus bytes before reuse; uncommitted changes and scope policy affect identity. Corrupt entries cause a fresh run. Post-write pruning targets 32 entries/32 MiB; concurrent in-flight writes can temporarily exceed the aggregate target. Source acquisition is individually stable, not an atomic filesystem snapshot.

Active working set

The extension inspects Pi's active, compaction-aware session entries for successful context_pack results. Only visible, non-metadata source items contribute content keys. Keys bind repository, location, file bytes and served representation. Matching unchanged items become brief references; code: { mode: "discover", refresh: true } forces serving. A new session or compacted-away original does not inherit a loaded claim. This does not inspect arbitrary native read output or guarantee visibility after unrelated extensions transform the final prompt. Without active-entry support, deduplication is unavailable.