[arjitj2]

Closes #159

Records Cursor's docs-only commit 019a6a2 as excluded and explains its checker assumptions. This distribution retains its own documentation checks and curated entry points. README.md is unchanged under the owner-approval rule.

Only UPSTREAM.md and the decision ledger change. The incorporated release baseline stays at 1b80080; review coverage advances through 019a6a2 with 52 final decisions. The package remains identical to v1.17.5, so no version, release or installation change is needed.

Validation: exact-head CI passed 993 Bun tests, with five platform skips and zero failures. Documentation checks, 16 documentation tests, 27 maintenance tests and ledger coverage passed. The actual audit reports the 11 excluded README/guide paths; preview finds no unreviewed source commits. The new upstream script was inspected without execution.

Independent exact-head Shipping review returned PASS+NOTES. It verified the maintenance commands, unchanged package, and all 238 installed Codex files. Runtime and native-host evidence from #158 is retained through unchanged hashes; these hosts were not retested for this metadata-only patch. The earlier local suite remains recorded as failed. Comment review found no eligible comments or required deletions. Copilot was requested but produced no pending reviewer or verdict; this is not approval.

Related ongoing monitor #1. Broader metadata and upstream tooling work remains separate in #87.

[arjitj2]

PR #160 independent Shipping verdict

PASS+NOTES at head 5a07d1041fb16ff3dbfd2c5f92c541f9558e83d3 against base ff5bdb273df33bccd397b627be2e0cb398a580cc.

Stable patch ID: 7a9b03eac6c7410b2baad72947951eb84bb96219.
Canonical forge repository: arjitj2/open-pstack; base branch: main.
Origin CLI is unavailable; read-only forge inspection used GitHub CLI. The origin fetch and push URLs both name https://github.com/arjitj2/open-pstack.git.

Observed behavior

The exact two-file patch changes only UPSTREAM.md and maintenance/upstream-ledger.json. It records source 019a6a20592c10bf92869e5740368f578a9997fd as excluded, advances review coverage to that source, and retains the incorporated package baseline 1b800800583ee8ff7f2676caf7a5cb7f0804be85.

I read the upstream documentation diff and the new checker without executing the checker. Source skills, agents, and plugin manifest are unchanged. The checker hardcodes the Cursor pstack/ tree, guide path, external built-ins, renamed babysit command, complete README inventories, and setup-based model names. Keeping the distribution’s existing owning-document checks is justified. The source guide includes substantive corrections as well as prose edits; exclusion does not claim those corrections are automatically imported. Its external guide remains an upstream reference.

The root README and AGENTS files are unchanged. No README approval was assumed. Existing documentation tooling work in #87 remains separate.

I exercised the actual final-head maintenance commands, with Python bytecode writes disabled:

• python3 scripts/check-docs.py: exit 0, check-docs: ok.
• python3 scripts/fork-maintenance.py check-ledger: exit 0, 52 entries and coverage checked.
• python3 scripts/upstream-audit.py --port 5a07d1041fb16ff3dbfd2c5f92c541f9558e83d3 --upstream 019a6a20592c10bf92869e5740368f578a9997fd: exit 0. Its 11 distribution-review paths exactly match the source’s README and ten guide paths.
• python3 scripts/fork-maintenance.py preview --base 5a07d1041fb16ff3dbfd2c5f92c541f9558e83d3 --target 019a6a20592c10bf92869e5740368f578a9997fd: exit 0, no new commits to catalogue. This no-op path performs no proposal construction.

The audit is correctly nonempty: exclusion advances review coverage while retaining the earlier incorporated package baseline. An empty audit is not a completion requirement here.

Package and evidence checks

The package tree at the base, final head, release v1.17.5, and retained runtime CI head fba49ec98eb4a8002ce3d8de1df313725be1a0a4 is identically e678abcef184b3b6b05115eb2affe75b2bb94d14. The scripts, GitHub workflows and project verification tree also match across those heads.

All 238 files in the local Codex 1.17.5 cache match final-head Git blobs, with no extra files. Codex configuration enables pstack@open-pstack and retains the unpinned arjitj2 Git marketplace source. No version change, release or installation update is needed for this patch. I did not launch a host or provider or repeat unchanged native tests. Hash equality supports retention of prior evidence; it does not create fresh native-host proof.

Parent-retained logs report 16 documentation tests and 27 maintenance tests passing. I read these logs, rather than rerunning suites that create disposable repositories. Prior full local Bun failures remain failures, not a claimed local pass.

Fresh exact-head CI run 39081595574 completed successfully. The retained exact-package CI 39081105030 also reports success. CI status is distinct from this independent verdict.

Landing limits

At inspection, GitHub reports PR #160 OPEN, non-draft, mergeable, head exactly as recorded, base main at the recorded base SHA, and both autoMergeRequest and mergeQueueEntry null. I armed and merged nothing. The parent must recheck head, base, checks and queue state immediately before its expected-head guarded merge.

Issue #159 is currently open and is fully scoped to this assessment. Close it only after the reviewed patch merges and final validation remains satisfied. Monitor #1 and broader tooling issue #87 continue independently.

The worktree remained clean. My only file write is this assigned verdict. Prompt-level worker instructions are guidance, not OS-confinement proof.