# Install VOUCH context MCP 0.1.2 locally Use one selected profile or project snapshot in a compatible MCP host. This standalone tool needs **Node 24 or newer and npm**, but no Gen C account, Portal build, cloud credential or full source checkout. It does not sync an account or call a model. Your host determines how supplied context is handled. Gen C supplies this standalone snapshot tool at no charge for personal and internal business use. Gen C retains ownership of its code. Dependencies are installed separately and retain their own notices: MCP core/server are Apache-2.0 and zod is MIT. This notice makes no open-source, redistribution or sublicensing grant, paid-service entitlement or support commitment. This guide describes the versioned download candidate. Check the accompanying release record for availability and qualification; the existence of this file is not evidence of publication, an npm registry release, marketplace listing or hosted OAuth product. Installing it and running the doctor do not establish that a particular host can discover its tools, render a review UI or use context in an answer. Do not use a similarly named registry package as a substitute. Version `0.1.2` identifies this package release. Its unchanged MCP server still advertises protocol-server version `0.1.0`; do not use that runtime version alone to identify installed package bytes. Use the archive digest and installed package manifest for the package identity. The retained `0.1.1` archive rejects profile entries containing the newer optional `context` field. Version `0.1.2` includes the current canonical profile validator and accepts current UI `another-ai` JSON as well as context-free legacy exports. At the ordinary AI/tool boundary it preserves context area and `UNVERIFIED_IMPORT` labels while omitting original quotes, references, source hashes and dates, including when a supplied `another-ai` file contains that owner evidence. Those descriptive labels do not verify facts or grant identity, account access or permission to act. TXT and `personal-backup` JSON remain refused by `--profile`; explicit personal backups keep their original evidence for the owner. The companion download kit contains the `.tgz`, `fictional-profile.json`, `INSTALL.md`, this complete guide as `GUIDE.md`, `manifest.json` and `SHA256SUMS`. The fictional example is also embedded below, so a tarball recipient can follow the same first task without the kit or private source access. ## 1. Verify the package you received Obtain the selected `.tgz`, its expected byte count and SHA-256, exact source commit/tree, and qualification from Gen C's release record or a trusted package handoff. The kit's `manifest.json` records those identities; its `SHA256SUMS` checks the accompanying files. Verify the kit's own digest against the trusted release record before relying on its contents. Keep the records together. A source-only package is not a CI-qualified release; a checksum verifies byte agreement, not authorship or permission. Do not calculate expected values from an untrusted download and treat that as approval. If you already have that handoff, start here. You do **not** need private GitHub access or a fresh three-day CI artifact. Other acquisition paths are described under [Package-owner acquisition options](#package-owner-acquisition-options). Never substitute an unverified registry package with a similar name. Run `node --version` and `npm --version` first. If Node is absent or older than 24, select Node 24 or newer before using the package. Set the three values below from the trusted handoff, then check the unchanged archive: ```sh MCP_ARCHIVE='/absolute/path/to/genc-project-handoff-mcp-0.1.2.tgz' MCP_EXPECTED_BYTES='replace-with-reviewed-byte-count' MCP_EXPECTED_SHA256='replace-with-reviewed-sha256' node --input-type=module - "$MCP_ARCHIVE" "$MCP_EXPECTED_BYTES" "$MCP_EXPECTED_SHA256" <<'NODE' import assert from 'node:assert/strict'; import { createHash } from 'node:crypto'; import { lstatSync, readFileSync } from 'node:fs'; import { isAbsolute } from 'node:path'; const [archive, expectedBytes, expectedHash] = process.argv.slice(2); assert.ok(isAbsolute(archive), 'Choose an absolute archive path.'); const stat = lstatSync(archive); assert.ok(stat.isFile(), 'Choose a regular archive file.'); assert.match(expectedBytes, /^[1-9][0-9]*$/, 'Use the reviewed byte count.'); assert.match(expectedHash, /^[a-f0-9]{64}$/, 'Use the reviewed SHA-256.'); assert.equal(String(stat.size), expectedBytes); const bytes = readFileSync(archive); assert.equal(String(bytes.length), expectedBytes); assert.equal(createHash('sha256').update(bytes).digest('hex'), expectedHash); console.log('Archive bytes match the reviewed handoff.'); NODE ``` Stop on any mismatch. Do not repack, reseal or replace the reviewed input to make it pass. This check reads the archive; it does not execute or install it. ## 2. Install into a separate local project Continue only after verification succeeds. Use a fresh disposable directory: ```sh MCP_PROJECT="$(mktemp -d "${TMPDIR:-/tmp}/genc-mcp-local.XXXXXX")" cd "$MCP_PROJECT" printf '%s\n' '{"name":"private-vouch-context","version":"1.0.0","private":true}' > package.json touch user.npmrc global.npmrc npm install --registry https://registry.npmjs.org \ --userconfig "$MCP_PROJECT/user.npmrc" --globalconfig "$MCP_PROJECT/global.npmrc" \ --engine-strict --ignore-scripts --no-audit --no-fund "$MCP_ARCHIVE" ``` This installs the verified local archive and its locked dependency graph. It may download dependencies from the npm registry and use npm's normal cache; it does not publish the package. The empty project-local npm configuration files avoid using credentials or registry choices from normal user/global npmrc files. Explicit environment-level npm settings still apply; do not supply unrelated authentication settings. No global install or host configuration is needed. **Offline option:** if the owner supplied an already prepared cache containing the locked dependencies **and their registry metadata**, use the same install command with `--offline --cache /absolute/path/to/reviewed-npm-cache`. An empty cache cannot work offline. On `ENOTCACHED`, stop and obtain the reviewed cache or choose the normal registry-backed install deliberately; do not silently remove `--offline`. Neither option requires rebuilding Portal or obtaining a new CI run. ## 3. Try the included fictional profile Use the kit's unchanged `fictional-profile.json`, or create the exact same fictional file in your separate local project with this command. It contains a single made-up goal, not anyone's private profile: ```sh MCP_EXAMPLE="$MCP_PROJECT/fictional-profile.json" # Use a fresh path. Do not overwrite an existing profile or export. (set -C; cat > "$MCP_EXAMPLE" <<'JSON' { "format": "vouch-selected-profile-preview", "formatVersion": 1, "copyBuildId": "vouch-profile-copy-20261016.1", "createdAt": "2026-10-17T05:26:53.776Z", "origin": "unsaved local copy prototype; not an account-saved profile", "authority": "Selected context only. No credentials, access, grants or permission to act.", "selection": [ { "field": "goal", "label": "Current goal", "group": "Current project", "scope": "project", "value": "Build a fictional colour study.", "source": "owner-provided", "localRevision": 1 } ] } JSON ) ``` If the path already exists, stop and compare it with the supplied example or choose a fresh path; do not overwrite it. For an already verified kit example, set `MCP_EXAMPLE` to that file's absolute path instead of creating another copy. ```sh ./node_modules/.bin/genc-project-handoff-doctor --profile "$MCP_EXAMPLE" ``` Continue only on exit `0`. This checks the local package and example; it does not launch a host or prove a tool call. The example's capture time is historical and it is explicitly unsaved, unverified and unsynchronized. Do not substitute private content merely to test installation. ### Choose a different reviewed snapshot Choose the mode that matches the file you explicitly intend to share: - Selected profile JSON: use `--profile`; the read tools are `get_personal_profile` and `list_profile_entries`. - Project or team handoff JSON: use `--handoff`; the read tools are `get_project_handoff` and `list_project_sources`. - A human-selected review flow uses the separate [selected-context companion](#optional-selected-context-companion). Installing the basic read-only server does not activate that companion or approve sharing. For example, check a reviewed profile export without starting a server: ```sh ./node_modules/.bin/genc-project-handoff-doctor --profile /absolute/path/to/reviewed-profile.json ``` For a reviewed project export, use this instead: ```sh ./node_modules/.bin/genc-project-handoff-doctor --handoff /absolute/path/to/reviewed-export.json ``` After the matching doctor exits `0`, a compatible host can launch the same installed server with that reviewed input. To start it directly for a stdio client, use **one** matching command: ```sh ./node_modules/.bin/genc-project-handoff-mcp --profile /absolute/path/to/reviewed-profile.json # Or, for a project/team handoff: ./node_modules/.bin/genc-project-handoff-mcp --handoff /absolute/path/to/reviewed-export.json ``` The server waits for MCP messages on stdin; a waiting terminal is not a failed install. It is also not an assistant session. Continue with your host's supported stdio setup using the exact installed path and selected mode, rather than pasting credentials or profile contents into host settings. Run the doctor before starting the server. Replace the example paths with your installed project and a fictional or reviewed export. If the local doctor command is missing, confirm you are in that installed project before repairing it. The doctor checks Node's version, the local package's required modules and that one input's readability and snapshot validity, then exits promptly. With `--handoff` or `--profile`, exit status **0** means those local checks passed; start the server only after that result. Use `./node_modules/.bin/genc-project-handoff-doctor --help` for command help. The snapshot commands accept `--handoff` or `--profile` followed by one absolute file path. `--help` exits with status `0` without checking readiness. | Exit status | Meaning | Next step | | --- | --- | --- | | `0` | Local runtime, package and snapshot input are ready. | Start the MCP server with the same reviewed input. | | `2` | Command usage is invalid. | Use exactly `--handoff /absolute/path/to/export.json`, `--profile /absolute/path/to/export.json`, or `--help`. | | `3` | Node is older than 24. | Select Node 24 or newer, then run the doctor again. | | `4` | Required local package modules are missing or damaged. | Reinstall the approved tarball in this disposable project; the doctor does not install anything. | | `5` | Input is missing, not a regular file, a final-component symlink, over 1 MiB, or invalid UTF-8/JSON. | Select an absolute regular-file path to a complete valid export; use the actual file rather than a symlink. | | `6` | The input cannot be inspected or read because of permissions or an I/O failure. | Check that your current OS user can read the chosen file, then retry. | | `7` | Snapshot schema, applicable handoff fingerprint or sensitive-value validation failed. | Choose a new reviewed export of a supported format; do not bypass validation or edit/reseal rejected input. | The doctor is strictly offline and does not change the input, install a host, write configuration, read credentials or make network requests. Its fixed diagnostics omit supplied paths, underlying errors, file contents, record IDs, hashes and environment values. It rejects final-component symlinks; parent directories are resolved by the operating system, so this is not a directory sandbox. It checks package layout and required module importability; it does not execute the server entry point or prove server startup or an MCP handshake. A ready result does not prove source freshness, provenance, agent-host installation or hosted readiness. The server writes MCP protocol messages to stdout; it is not an interactive prompt. Use `./node_modules/.bin/genc-project-handoff-mcp --help` to see command usage without starting the server or checking credentials; help works even if runtime modules are missing. A compatible stdio host can launch `node` with the absolute installed entry path `/absolute/path/to/fictional-mcp-project/node_modules/genc-project-handoff-mcp/mcp/server.mjs` and arguments `--handoff`, `/absolute/path/to/reviewed-export.json`. The file must be an absolute regular-file path to a valid, reviewed Portal handoff. Invalid or missing inputs exit with status 1 and fixed stderr advice pointing to the offline doctor with the same input. Missing or damaged runtime modules also exit safely with doctor guidance instead of a raw module stack or installation path. Both read tools accept `{}` and return the startup snapshot; restarting loads a new export. ## 4. Confirm your actual host can use it For a stdio host, the launch command is `node`; its argument array contains the absolute installed server entry, the selected mode and the absolute export path: ```json [ "/absolute/path/to/installed-project/node_modules/genc-project-handoff-mcp/mcp/server.mjs", "--profile", "/absolute/path/to/reviewed-profile.json" ] ``` Use your host's documented setup format. The array is a launch example, not a configuration file to overwrite, and no host is configured by these instructions. Select a Node 24+ executable that the host can resolve. Use `--handoff` with a project/team export instead. Keep fixed selected-file access separate from live account access, OAuth and persistent synchronization. Check the **current chat's advertised tools**, not just a saved configuration: 1. Confirm the intended existing entry and its configured command/input without exposing environment secrets or profile values. 2. Distinguish **configured**, **enabled**, **connected** and **tools exposed**. An enabled entry is not proof that this chat can call it; absence in one chat does not prove absence in another. Do not toggle an already enabled entry or remove/re-add it to guess at a fix. Use the host's supported diagnostics and entry-specific controls; do not restart the whole application as a substitute for identifying the missing step. 3. Confirm the tools for the selected mode appear before making a call. The basic profile server exposes `get_personal_profile` and `list_profile_entries`; the companion exposes review/sharing tools instead. A doctor's READY result or a separate protocol-client test does not establish current host exposure. 4. For a deliberately selected fictional or authorized snapshot, ask the assistant to read it and answer one concrete question using the returned fields. Check that the answer uses the supplied context and preserves its limits. Tool discovery, returned data and actual use in an answer are separate observations. For the companion, `review_profile_context` keeps values out of ordinary model content until the supported explicit include/share action. App-only `prepare_profile_handoff` may not appear in the model-facing catalog. The human must choose and approve the fields in the supported form/UI; model arguments, a scripted approval, a previous approval or a file hash are not a new human choice. A declined request stays declined; do not replay it automatically. A host without the required UI/form support is not accepted for that review flow. ### Codex stdio setup and first useful task This is a concrete Codex CLI setup path, using its `mcp add NAME -- COMMAND...` contract. It configures a local stdio server, not an HTTP endpoint. It requires an existing supported Codex installation in which `codex mcp add --help` shows that syntax. Do not install a similarly named CLI to make the command work. If your Codex installation is not on PATH, use its existing supported CLI route. These commands are instructions for the operator; this release has not executed a fresh host installation or accepted a host/model answer. First inspect `codex mcp list` locally. Choose an unused name and do not overwrite or retarget an existing private registration. The following deliberately uses only the fictional file from step 3. Continue in the same shell after its doctor passes and with Node 24+ selected: ```sh codex mcp add vouch-fictional-snapshot -- "$(command -v node)" \ "$MCP_PROJECT/node_modules/genc-project-handoff-mcp/mcp/server.mjs" \ --profile "$MCP_EXAMPLE" codex mcp get vouch-fictional-snapshot --json ``` The add command changes Codex's MCP configuration. The get command confirms saved configuration only, not a connection. Keep the project and example at those paths while the entry is in use. In an intended Codex session, verify that this server's `get_personal_profile` and `list_profile_entries` tools are actually exposed. Some sessions expose different tools even when configuration is enabled. If absent, use your installed host's documented entry/session controls; do not toggle an already enabled private entry, overwrite configuration or restart the whole app to guess at a fix. Report “configured, tools not exposed” rather than claiming the task worked. When the named tool is available, ask: > Call `get_personal_profile` on `vouch-fictional-snapshot` once with `{}`. > Using only that returned fictional snapshot, state the goal, say whether a > constraint was supplied, and suggest one practical next step. Identify the > snapshot date and lack of synchronization. Do not read a local file as a > fallback, call a different server, save, send or change anything. A grounded answer identifies **“Build a fictional colour study.”**, says no constraint was supplied, and might suggest comparing a small set of palettes. It must distinguish that suggestion from a stored fact and preserve the dated, unsaved/unverified snapshot limits. A plausible answer without the named tool's actual result is not acceptance. Record tool exposure, successful returned data and context use in the answer separately. Stop if a host asks for data or access you did not intend to supply. This read-only fictional workflow does not accept the separate human-selected review UI, authorize private sharing, or prove compatibility with every host. For your own reviewed profile later, a useful task is: “Using only the selected profile context, summarize my stated goal and constraints, then suggest one next step. Mark anything missing as unknown. Do not save, send or change anything.” Choose and authorize that separate input explicitly; do not retarget an existing registration or replay a declined review/share request. ## Selected profile export Use the same local package with a reviewed profile JSON export: ```sh ./node_modules/.bin/genc-project-handoff-doctor --profile /absolute/path/to/export.json ./node_modules/.bin/genc-project-handoff-mcp --profile /absolute/path/to/export.json ``` This mode accepts `vouch-personal-profile-disclosure` version 1 with purpose `another-ai`, or `vouch-selected-profile-preview` formatVersion 1 from copy build `vouch-profile-copy-20261016.1` or `vouch-profile-copy-20261030.1`. Build 30's strict contract is verified against the published pure producer `dist/profile-content.mjs` at source `dabf7507e73642aef2f76385db75e156fb81c240` (5,918 bytes, SHA-256 `ca0c61762443a92f54e2951b7a91c4c5319cb9ba5fd9837392d466350e102fd9`), matched by its owner to the approved published archive. Its six descriptors, in producer order, are display name, tools, help style, task experience, goal and constraint. Any nonempty selected subset is supported. Build 30 also preserves `owner-pasted-ai-excerpt` and `owner-edited-ai-excerpt`, alongside the three original source labels. These labels remain caller-supplied, unverified data; pasted AI text gains no instruction or identity authority. Build 16 retains its original three-source vocabulary. The original 613-byte public download (SHA-256 `a25b941bc2975499a4363220689ba354e18ff9b7268c388fa050b1847a7dd84e`) remains separate evidence; expanded test exports use synthetic values generated by the verified producer, not additional claimed downloads. Only the producer's selected JSON payload is accepted here. Its human-readable TXT rendering is for manual paste, not the `--profile` JSON input. Root/row fields, labels, groups, scopes, ordering and provenance vocabulary remain exact; unknown build IDs, unsafe revisions/values and oversized files remain refused. Drafts, account-content files, private backups, private entries and unknown fields are rejected. The public preview retains its original field, source, local revision and unsaved origin; it gains no canonical entry ID or approved review label. Only `get_personal_profile` and `list_profile_entries` are exposed in this mode. Both accept `{}`. The first returns the selected snapshot in its original schema; the second returns entry metadata without values. The wrapper labels context and source/review claims as untrusted, with unverified provenance and no synchronization. Its file-byte hash detects changed bytes, not authenticated ownership. Imported text grants no identity, account access, permissions, persona or instructions. The process reads only the supplied file at startup. Restart with a newly reviewed export after corrections or deletion; changing the file does not refresh it. Disclosure entries must be current at startup, and both tools fail closed when the earliest included `expiresAt` is reached. The public preview has no expiry field; its creation time does not prove freshness. Neither command discovers profiles, reads an account, calls a model, installs/configures a host or activates an integration. The doctor exits after its offline check; the server waits for stdio. Local installation is separate from npm or marketplace publication. Remove only this project's dependency when finished: ```sh npm uninstall --ignore-scripts --no-audit --no-fund genc-project-handoff-mcp ``` Uninstall removes the package and its local executable links. The export remains yours to retain or remove. These commands use npm's normal cache and project lockfile; they do not remove MCP host settings. If you added the fictional Codex entry, remove only that entry through the host's supported controls when finished. For isolated verification, direct npm's cache and npmrc paths into the temporary project. No global package is required. ### Maintainer-only source checkout Package recipients can skip this section. To use the source checkout directly, retain its complete `mcp/` and `shared/` layout and run these commands from the repository root: ```sh npm ci --prefix mcp --ignore-scripts --no-audit --no-fund node mcp/doctor.mjs --handoff /absolute/path/to/reviewed-export.json node mcp/server.mjs --handoff /absolute/path/to/reviewed-export.json ``` For a selected profile export, replace `--handoff` with `--profile` in both source-checkout doctor/server commands above. For status `4` in a source checkout, restore the reviewed source layout and its locked adapter dependencies before retrying. Both doctor commands perform the same local snapshot checks; neither starts or configures an agent host. For a first fictional check from the repository root, use the committed fixture: ```sh node mcp/doctor.mjs --handoff "$PWD/mcp/test/fixtures/fictional-handoff.json" ``` That fixture stays in the source checkout and is excluded from the installed artifact. Run the doctor again with your chosen reviewed export before starting the snapshot server. The helper includes optional runtime modules when they exist in the reviewed source, including the live adapter. Packaging does not deploy its backend or make live access ready. Live operation requires that source's deployed endpoint, existing permitted customer session and ephemeral process credential, under the [project handoff contract](project-agent-handoff.md). Local fictional stdio tests establish interoperability only; they do not establish hosted acceptance, source freshness or an installed Codex/Claude session. ### Optional selected-context companion The package also includes `genc-profile-review`. Start it deliberately with `--profile /absolute/path/to/reviewed.json` in an existing compatible MCP Apps host. This command uses stdio and opens no HTTP listener. It does not register or install a host. The ordinary handoff MCP command keeps its existing behavior and two profile tools. The companion exposes `review_profile_context`, `prepare_profile_handoff` and `share_selected_profile_context`, plus the read-only UI resource `ui://genc/profile-review/v1.html`. Review values stay in UI metadata until an explicit include action asks the connected host to add the selected snapshot to future model context. No entries start selected. A host response does not prove model use or bind a conversation. The form alternative requires the human to check exact entries and approve their return to the client; a model-supplied hash or selection cannot approve that return. Both accepted public preview builds (build16 and public30) and canonical another-ai disclosures use the existing strict validator. Source and review labels are unverified claims. Files changed, removed, invalidated or expired after startup make the companion unavailable until restart; recipient copies remain unsynchronized. No account import, save, approval or task execution is provided. VOUCH context remains portable, including free selected copy. For a separately authorized attended command-line workflow, run `genc-profile-review --preview --profile /absolute/reviewed.json`, review its values and source byte hash, then run `genc-profile-review --handoff --profile /absolute/reviewed.json --sha256 REVIEWED_SHA256 --select key1,key2`. This prints only the explicitly chosen context. `genc-profile-snapshot --profile /absolute/reviewed.json` prints the existing full selected-export snapshot. These operator commands print private values to stdout; keep their output private. They are not a fallback for a refused or declined host sharing request; do not use them to bypass the human selection flow. Package `source-inventory.json` records the actual emitted closure, original source paths and hashes. It makes no CI, hosted-app, GUI or application qualification claim. ### Source adapter for an existing portable host `mcp/portable-profile-adapter.mjs` is a separate, unbound Source successor. It accepts `--package-root /absolute/reviewed/package --profile /absolute/reviewed.json` and delegates to an existing stdio factory only after matching one of two fixed accepted inventories: `6cea88e` (18 total files) or `b3bc673` (19 total files). The original inventory pin remains `c3a6989f3d5fc19df8982f4638f18b7a5bb4879f94354b6d68526d38b65b7f57`. The additive b3 inventory pin is `a113426e8eb400323bdb9fd3c209c85f289d923add4be9e6d88a782533e59acc`; its retained archive is 56,788 bytes with SHA256 `1e10be0c08dd6cabfcb9326772ae3960a850ef034b027fc2d23addc4f7a62f26`. All 17 or 18 listed emitted files are checked before import. The b3 package contains the historical adapter; this additive loader remains separate from that frozen package, avoiding a self-referential package pin. Regenerated archives are tested against exact inventory and emitted bytes, never relabeled as the retained accepted tarball. Future source packages are not automatically accepted, and callers cannot supply their own inventory pin. This adapter does not retarget an existing registration, install dependencies, discover a profile or start HTTP. Use requires an already available reviewed package and its locked dependencies. The byte check covers package source at the time of checking. It does not attest loaded dependencies, protect against concurrent same-user filesystem changes, establish permission from imported context or prove a host renders the UI. The old portable-v0 script uses the same review resource URI and UI metadata shape. Its reported `review-required` result with no exposed App surface remains a host rendering boundary; this adapter cannot force host capabilities or expand a hidden app card. Host placement and rendered acceptance remain with the existing owner. ### Grouped read-only review The widget groups the accepted six entry kinds and preview fields into “About me,” “How I like help,” and “Current project.” Collapsed summaries show entry and selection counts plus a short excerpt. Open a group with its native keyboard summary control to read full values and unverified source claims. Empty groups explain the selected-export boundary. Group navigation never selects, approves or shares an entry. Prepare a selection, inspect the exact snapshot text, then use the separate include action. This view provides no profile editing, import, account save or writeback. For source-frozen fictional browser receiving through the existing Portal owner's local route, run `node mcp/test/stage-grouped-review-render.mjs --out /absolute/fresh/render-directory`. The command only stages exact widget HTML, two validated fictional export scenarios, a sandboxed static host harness, SHA256 manifest and finite render instructions. It starts no browser or server. The receiver opens `index.html` through its existing authorized static route and follows `RENDER-INSTRUCTIONS.txt` at desktop and mobile sizes. Harness context requests go only to its local fixture recorder. This checks widget presentation and bridge behavior; named-host UI acceptance and actual model use remain `NOT_RUN` until separately observed by the existing host owner. The frozen `6cea88e` 18-file package and `1537c2e` adapter remain historical inputs; this HTML successor does not retarget either one. ## Checked-change learning packets For an explicitly reviewed checked-change learning packet, the existing doctor/server also support: ```sh ./node_modules/.bin/genc-project-handoff-doctor --checked-change /absolute/packet.json --receipt /absolute/return.json --artifact /absolute/output.json ./node_modules/.bin/genc-project-handoff-mcp --checked-change /absolute/packet.json --receipt /absolute/return.json --artifact /absolute/output.json ``` The receipt and output artifact flags are optional. The packet is the existing four-file `import`/`filter` learning contract; an arbitrary JavaScript project cannot be relabeled as that artifact. Two tools accept only `{}`: `get_checked_change_packet` returns the selected packet, original input text and byte hashes; `get_checked_change_result` returns the canonical evidence projection. The package includes the unchanged canonical engineering model. There is no runner registry or execution. Imported PASS claims remain untrusted; v2 effective outcomes remain UNKNOWN. Missing receipt/output stays missing, and stale bindings cannot become current PASS. V1 receipt compatibility requires an actual output artifact. Malformed/tampered input refuses startup. READY confirms readable valid inputs, not passed checks. “Current” means agreement among selected files, not live source freshness. Restart with newly reviewed files after any change. No expiry field, account authority, synchronization, installation or execution is inferred. ## Package-owner acquisition options The recipient installation steps above use an already supplied reviewed archive. These alternatives are for an owner obtaining or preparing that archive. They do not require changing a working host or repeating accepted tests. ### Retained private CI artifacts If the package owner selects the GitHub Actions route, obtain the package from a **completed successful Portal CI run on reviewed main source** in the private repository. This is an optional retrieval route, not a prerequisite for installing an already supplied reviewed archive. Successful full-scope runs that execute MCP packaging retain `portal-mcp--` for **three days**, under the existing GitHub Actions access controls. Confirm that the selected successful run actually contains that named artifact; scoped runs may not package MCP. The artifact contains the installable `.tgz`, `verification.json` and `SHA256SUMS`. Download it from that run's **Artifacts** section, or use an existing authenticated GitHub CLI session with repository/Actions read access: ```sh # Set these three identities together from the reviewed successful main run. MCP_REPOSITORY='OWNER/REPOSITORY' MCP_RUN_ID='replace-with-run-id' MCP_RUN_ATTEMPT='replace-with-attempt' MCP_SOURCE_SHA='replace-with-full-source-sha' mkdir /absolute/path/to/fresh-artifacts gh run download "$MCP_RUN_ID" --repo "$MCP_REPOSITORY" \ --name "portal-mcp-$MCP_RUN_ID-$MCP_RUN_ATTEMPT" --dir /absolute/path/to/fresh-artifacts cd /absolute/path/to/fresh-artifacts gh api "repos/$MCP_REPOSITORY/actions/runs/$MCP_RUN_ID/attempts/$MCP_RUN_ATTEMPT" > run.json node --input-type=module - "$MCP_SOURCE_SHA" <<'NODE' import assert from 'node:assert/strict'; import { readFileSync } from 'node:fs'; const run = JSON.parse(readFileSync('run.json')); const receipt = JSON.parse(readFileSync('verification.json')); assert.equal(run.status, 'completed'); assert.equal(run.conclusion, 'success'); assert.equal(run.head_branch, 'main'); assert.equal(run.path.split('@')[0], '.github/workflows/ci.yml'); assert.ok(['push', 'workflow_dispatch'].includes(run.event)); assert.equal(run.head_sha, process.argv[2]); assert.equal(receipt.source_sha, run.head_sha); assert.equal(receipt.source_tree_sha, run.head_commit.tree_id); assert.equal(receipt.run_id, String(run.id)); assert.equal(receipt.run_attempt, String(run.run_attempt)); assert.equal(receipt.artifact_name, `portal-mcp-${run.id}-${run.run_attempt}`); assert.equal(receipt.result, 'PASS'); console.log('Reviewed run and package receipt match.'); NODE shasum -a 256 -c SHA256SUMS ``` Continue only after both checks pass. The receipt records exact source SHA/tree, run/attempt, tarball bytes/SHA-256/npm integrity/file inventory, source `mcp/package-lock.json` SHA-256, packaged shrinkwrap and installed lock hashes, Node/npm versions and the passing fictional installed doctor/stdio checks. With that reviewed checkout available, compare `git show "${MCP_SOURCE_SHA}:mcp/package-lock.json" | shasum -a 256` to `dependencies.source_lock_sha256`. The uploaded tarball is the exact one tested; it is not repacked after verification. Hashes detect changed bytes; the editable receipt alone does not authenticate GitHub provenance. Keep the authenticated run readback and artifact identity with your private handoff. Expired artifacts cannot be retrieved from that run. A retained, independently verified copy does not expire merely because its GitHub download has expired; retain its original source/run/qualification evidence. If no verified copy is available, ask the existing package owner for the selected delivery route. Do not trigger a new CI run or paid resource merely to follow this guide. GitHub PR artifacts remain integration evidence until their source and release are qualified through the existing owner's supported route. These local checks do not establish live access, host configuration or hosted customer acceptance. ### Reviewed source checkout Package owners with a reviewed complete GenC-Portal checkout can prepare a private tarball. Package recipients do not need the checkout or this step: ```sh node scripts/package-handoff-mcp.mjs --out /absolute/path/to/fresh-artifacts ``` The helper prints the artifact path, SHA-256, integrity and packed file list. Keep that local source/hash receipt with the private tarball. Local packaging is not registry publication or evidence of a successful CI run or configured host. It needs no repository dependency installation. It stages runtime modules and the shared validator as JavaScript, includes the adapter's locked dependency graph as `npm-shrinkwrap.json`, and removes staging afterward. It refuses to replace an existing artifact. Tests, fixtures, Portal/Worker sources, exports, environment files and credentials are excluded. The source `mcp/` directory is not itself a standalone npm artifact; packing it directly omits its shared validator. Node refuses native TypeScript loading beneath `node_modules` (see [Node's dependency restriction](https://nodejs.org/docs/latest-v24.x/api/typescript.html#type-stripping-in-dependencies)).