Publish by OIDC trusted publishing instead of the expired npm token

.agents/pm/history/pm-linear-9hw2.jsonl

@@ -0,0 +1,2 @@
+{"ts":"2026-08-26T19:33:42.360Z","author":"claude","author_source":"asserted","agent_harness":"claude-code","agent_instance":"f559dcd5a5f387bc7221097a","agent_provenance":{"model":null,"effort":{"value":"xhigh","source":"environment"},"role":{"value":"implementer","source":"argv"},"topic":null},"op":"create","patch":[{"op":"replace","path":"/body","value":"Trusted publishing replaces the stored credential. The registry mints a short lived credential from the workflow OIDC identity, so there is no secret left to expire. Requires a one time configuration on npmjs.com binding this package to unbraind/pm-linear and the release.yml workflow."},{"op":"add","path":"/metadata/id","value":"pm-linear-9hw2"},{"op":"add","path":"/metadata/title","value":"The release job authenticated with a stored npm token that expired, so publishing stopped while every other gate stayed green"},{"op":"add","path":"/metadata/description","value":"The Publish npm package step read NODE_AUTH_TOKEN from the repository secret NPM_TOKEN. That credential began being rejected on 2026-08-17. From then until 2026-08-26 every daily release run reached the publish step and failed with npm code E404 on PUT to the registry, which is how npm reports a rejected write credential rather than a missing package. Rotating the secret on 2026-08-22 did not help, and the copy of the credential on the maintainer host answers 401 to npm whoami, so the token is dead rather than mis-stored. Because the version bump and the release commit both land before the publish step, main advanced to 2026.8.26 with no matching tag and no published artifact while npm still serves 2026.8.16. Sixteen of the eighteen published fleet packages are in the same state."},{"op":"add","path":"/metadata/type","value":"Issue"},{"op":"add","path":"/metadata/status","value":"in_progress"},{"op":"add","path":"/metadata/priority","value":0},{"op":"add","path":"/metadata/tags","value":["npm","release","supply-chain"]},{"op":"add","path":"/metadata/created_at","value":"2026-08-26T19:33:42.360Z"},{"op":"add","path":"/metadata/updated_at","value":"2026-08-26T19:33:42.360Z"},{"op":"add","path":"/metadata/deadline","value":"2026-09-02T00:00:00.000Z"},{"op":"add","path":"/metadata/assignee","value":"claude"},{"op":"add","path":"/metadata/author","value":"claude"},{"op":"add","path":"/metadata/estimated_minutes","value":90},{"op":"add","path":"/metadata/acceptance_criteria","value":"No release workflow references NODE_AUTH_TOKEN NPM_TOKEN or secrets.NPM outside a comment; the publish job carries id-token write; npm is raised to at least 11.5.1 before the publish step because the npm bundled with node 22 cannot exchange an OIDC token; a test fails closed if a stored token is reintroduced or the npm upgrade is removed"},{"op":"add","path":"/metadata/comments","value":[{"created_at":"2026-08-26T19:33:42.360Z","author":"claude","text":"Guards verified as non-vacuous: reintroducing NODE_AUTH_TOKEN fails the OIDC test and deleting the npm upgrade step fails the npm-version test, while the unmodified tree passes both."}]},{"op":"add","path":"/metadata/notes","value":[{"created_at":"2026-08-26T19:33:42.360Z","author":"claude","text":"Root cause was found by comparing npm view against the branch, not by reading CI. Every job except publish was green for ten days."}]},{"op":"add","path":"/metadata/learnings","value":[{"created_at":"2026-08-26T19:33:42.360Z","author":"claude","text":"A release pipeline that bumps and commits the version before it publishes hides a credential outage indefinitely. Registry state, not workflow state, is the definition of released."}]},{"op":"add","path":"/metadata/files","value":[{"path":".github/workflows/release.yml","scope":"project"}]},{"op":"add","path":"/metadata/tests","value":[{"command":"npx tsx --test test/release-workflow.test.ts","scope":"project"}]},{"op":"add","path":"/metadata/docs","value":[{"path":"https://docs.npmjs.com/trusted-publishers","scope":"project","note":"npm trusted publishing setup"}]}],"before_hash":"3cc22dff72be7b14824654a7a64ea62b04799939b2fee54c1b5f52ca60bf6df0","after_hash":"c51f990e183e114675baa961549af9fea545c8c55f7b65e5ff5340837207cb81","item_hash_version":2,"message":"Record the npm credential outage and migrate this package to trusted publishing","context":{"agent_provenance_outcomes":{"model":{"status":"failed","reason":"resolver_failed","resolver":"claude_session_file","rule_version":"v1"},"version":{"status":"failed","reason":"resolver_failed","resolver":"claude_session_file","rule_version":"v1"}}}}
+{"ts":"2026-08-26T23:06:26.276Z","author":"codex","author_source":"configured","agent_harness":"claude-code","agent_instance":"66f51baccd944ab11404f28c","agent_provenance":{"model":null,"effort":{"value":"xhigh","source":"environment"},"role":{"value":"implementer","source":"argv"},"topic":null},"op":"update","patch":[{"op":"replace","path":"/metadata/updated_at","value":"2026-08-26T23:06:26.276Z"},{"op":"replace","path":"/metadata/description","value":"The Publish npm package step read NODE_AUTH_TOKEN from the repository secret NPM_TOKEN. That credential began being rejected on 2026-08-17 UTC. From then until 2026-08-26 UTC every daily release run reached the publish step and failed with npm code E404 on PUT to the registry, which is how npm reports a rejected write credential rather than a missing package. Rotating the secret on 2026-08-22 UTC did not help, and the copy of the credential on the maintainer host answers 401 to npm whoami, so the token is dead rather than mis-stored. Because the version bump and the release commit both land before the publish step, main advanced to 2026.8.26 with no matching tag and no published artifact while npm still serves 2026.8.16. Sixteen of the eighteen published fleet packages are in the same state."}],"before_hash":"c51f990e183e114675baa961549af9fea545c8c55f7b65e5ff5340837207cb81","after_hash":"2f5792b5c686612d0c45e08f4dc57cbb7b863ab8464bbfe5f805ba90785eb8c5","item_hash_version":2,"context":{"agent_provenance_outcomes":{"model":{"status":"failed","reason":"resolver_failed","resolver":"claude_session_file","rule_version":"v1"},"version":{"status":"failed","reason":"resolver_failed","resolver":"claude_session_file","rule_version":"v1"}}}}