fix(ci): waive lockfile bake time for pinned harnesses (#22349)

## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - Paperclip Runner ships pinned harnesses that run those agents.
> - Some new models require a new harness release before they can run.
> - The lockfile bot waits three days before it can merge new dependency
versions automatically.
> - That wait held the Claude and Codex refresh in #22231.
> - This PR waives the wait for a fixed set of harness packages so model
updates can ship as soon as npm confirms the releases.

## Linked Issues or Issue Description

Refs #22231, #22278, #14942, #15572, and #18238.

**What happened?**

The refresh in #22231 held 16 new Claude Agent SDK and Codex versions
even though the new model support needed those harness updates.

**Expected behavior**

Verified npm releases of named harness packages can pass the gate
immediately. The gate applies the normal minimum age to other packages.

**Steps to reproduce**

Compare the parent and head of #22231 across the three lockfiles managed
by the bot. Run the gate with the publish times in its hold comment and
a clock within three days of the releases.

## What Changed

- Exempt 28 exact package names from the minimum age. These cover the
Claude Agent SDK, Codex CLI, their provider-specific ACP bridges,
OpenCode, and the Copilot binaries pinned by Runner.
- Take package identities from the Runner manifest and active provider
profiles, then check the managed lockfiles for platform binaries. Codex
platform aliases use the same registry name with a platform suffix on
each version. Pi and Kimi use separate npm locks. Gemini, Grok, the
local Cursor CLI, and Antigravity use separate install paths. The Cursor
Cloud SDK gets model availability from the service.
- Keep the npm publish-time and resolution checks for every entry.
Update the bot report and setup documentation.

## Verification

- Replayed the exact #22231 lockfile diff using the bot's recorded
publish times and a fixed clock. The previous gate held all 16 versions.
The new gate verified all 16 and held zero.
- Ran the workflow CLI against the same three lockfile pairs and the
live npm registry. It wrote `eligible=true` and reported 16 passing
versions.
- Reconciled the 28 exact names with the Runner manifest, provider
profiles, all three bot-managed pnpm lockfiles, and the npm manifests
for Claude Agent SDK 0.3.328, Codex 0.170.0, and OpenCode 1.18.34.
- Ran `node --test '.github/scripts/tests/*.test.mjs'` locally. All 810
tests passed. The new cases cover mixed refreshes, similar names,
registry errors, missing publish times, and non-registry resolutions.
- Ran `git diff --check`.
- GitHub Actions passed the required typecheck, build, test, and e2e
checks on `9c8bccac51`. The Canary runner shut down on the first
attempt, and browser shard 7 had a test-company cleanup error. Both
passed on the failed-jobs retry. [CI attempt
2](https://github.com/paperclipai/paperclip/actions/runs/44610325309/attempts/2)
- Standard Greptile scored the same revision 5/5.
[Review](https://github.com/paperclipai/paperclip/pull/22349#issuecomment-7021573041)

## Risks

An npm release of an allowlisted harness can reach master during its
first three days through the existing automatic merge path. A
compromised release can use that same path. Every added version still
needs an npm publish time and a registry resolution. Review new platform
package names before adding them to the allowlist. Superagent requests
security review for this policy change. [Scanner
finding](https://github.com/paperclipai/paperclip/pull/22349#discussion_r4634801827)

## Model Used

OpenAI GPT-6 in Codex, with shell and code execution. The exact model
snapshot and context window were not reported.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

Co-authored-by: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Nicky LeachandPaperclip authored and GitHub committed 2026-11-19 14:17:32 -08:00
1 parent d8ae55198d
commit 3c32b8d4dc
4 files changed
+91 -10

No files matched your search

@@ -150,6 +150,56 @@ test('holds a version newer than the minimum age', async () => {
assert.match(result.held[0].reason, /0\.5 days ago/);
});
test('gives only named harness releases an exception to the minimum age', async () => {
const harnessKeys = [
'@agentclientprotocol/claude-agent-acp@0.73.0',
'@agentclientprotocol/codex-acp@1.6.2',
'@anthropic-ai/claude-agent-sdk@0.3.328',
'@anthropic-ai/claude-agent-sdk-linux-x64-musl@0.3.328',
'@github/copilot-darwin-arm64@1.0.88',
'@openai/codex@0.170.0',
'@openai/codex@0.170.0-win32-arm64',
'opencode-ai@1.18.34',
'opencode-linux-x64-baseline-musl@1.18.34',
];
const harnesses = addedPackageVersions(lockfile([]), lockfile(harnessKeys));
const other = addedPackageVersions(lockfile([]), lockfile([
'@agentclientprotocol/sdk@1.9.0',
'@anthropic-ai/claude-agent-sdk-lookalike@1.0.0',
'fresh@1.0.1',
]));
const options = { fetchPublishTime: async () => daysAgo(0.5), now, minAgeMs: 3 * DAY_MS };
const result = await checkReleaseAge(harnesses, options);
assert.deepEqual(result, { eligible: true, checked: harnessKeys.length, held: [] });
assert.match(formatReport(result, 3), /passed the release-age gate/);
const mixed = await checkReleaseAge([...harnesses, ...other], options);
assert.equal(mixed.eligible, false);
assert.deepEqual(mixed.held.map(h => h.key), other.map(h => h.key));
});
test('still requires a verified npm release for allowlisted names', async () => {
const entries = addedPackageVersions(lockfile([]), lockfile([
'@openai/codex@0.170.0',
'@openai/codex@0.171.0',
['@openai/codex@0.172.0', '{tarball: https://example.com/codex.tgz}'],
'@openai/codex@https://example.com/codex.tgz',
]));
const result = await checkReleaseAge(entries, {
fetchPublishTime: timesFrom({ '@openai/codex@0.170.0': new Error('npm registry returned 503') }),
now,
minAgeMs: 3 * DAY_MS,
});
assert.equal(result.eligible, false);
assert.deepEqual(result.held.map(h => h.reason), [
'registry lookup failed: npm registry returned 503',
'no publish time on npm',
'not a registry resolution: {tarball: https://example.com/codex.tgz}',
'not a registry version',
]);
});
test('fails closed on lookup errors, missing publish times and non-registry versions', async () => {
const entries = addedPackageVersions(
lockfile([]),