Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .agents/pm/history/pm-7zs0.jsonl
Original file line number Diff line number Diff line change
Expand Up @@ -283,3 +283,5 @@
{"ts":"2026-08-07T17:13:56.914Z","author":"harness:claude-code","author_source":"detected","agent_harness":"claude-code","agent_model":"claude-opus-5","agent_model_source":"probe","agent_instance":"42d376a0ebc79212ad1dd49b","agent_provenance":{"model":{"value":"claude-opus-5","source":"probe"},"effort":{"value":"xhigh","source":"environment"},"role":{"value":"1","source":"environment"},"topic":null,"version":{"value":"2.1.224","source":"probe"}},"op":"comment_add","patch":[{"op":"add","path":"/metadata/comments/137","value":{"created_at":"2026-08-07T17:13:56.914Z","author":"harness:claude-code","text":"Evening re-verification 2026-08-07, after the morning pass already recorded the three-run picture for this UTC day. State unchanged and still exactly one release for the day: npm dist-tag latest 2026.8.7, tag v2026.8.7 present and unique, package.json 2026.8.7, and the [Unreleased] changelog section empty. The 04:36Z scheduled run failed on sentry-telemetry-gate, the 10:12Z dispatch cut the tag, the 10:24Z dispatch skipped on release_already_cut_today.\n\nOne addition the morning entry does not carry: the trigger asymmetry that makes the scheduled path the least-verified one. On workflow_dispatch, push defaults to false and dry_run to false; on schedule, INPUT_PUSH is hardcoded true. A dispatch run at the default therefore exercises every gate but not the commit-tag-push path, and a dispatch run with push=true exercises a path whose same-day guard then blocks it. Neither dispatch shape reproduces the scheduled shape exactly, and the scheduled shape is the only one the daily guarantee depends on. The two most recent scheduled failures were both repaired and then released by dispatch, so no scheduled run has completed successfully at HEAD since the repairs landed. Rate evidence recorded on pm-e70zh5; the same-day guard's trigger-blindness remains on pm-uenmu9."}},{"op":"replace","path":"/metadata/updated_at","value":"2026-08-07T17:13:56.914Z"}],"before_hash":"942eb5da191947cbbf8441043bdb9331f1c9258c42c83f92c4dcdfa0ffabdd89","after_hash":"45a15f51883d5ca7fdb5d5ab6133612e972a3540fecaa542d50b7e6cc13b8e88"}
{"ts":"2026-08-08T14:06:54.631Z","author":"harness:codex","author_source":"detected","agent_harness":"codex","agent_instance":"311a8aed9ab7c477f6e67245","agent_provenance":{"model":null,"effort":null,"role":null,"topic":null},"op":"comment_add","patch":[{"op":"add","path":"/metadata/comments/138","value":{"created_at":"2026-08-08T14:06:54.631Z","author":"harness:codex","text":"2026-08-08 release-health proof: PRs #935 and #938 shipped as the sole v2026.8.8 cut. Auto Release 31259981172 and downstream Release 31260405095 succeeded; npm latest=2026.8.8 and independent npm/npx/bunx/pm-mcp/GitHub verification passed. The initial issue-recovery run 31258567364 failed on a date-specific packaged test assertion and is tracked/fixed by pm-7ipajv. Closing GH #934 triggered guarded run 31261020199, which completed in 50s using the recorded retry/same-day guard and did not create another tag. Live Sentry critical/high=0/0; telemetry error rate=0.99%, missing error-code rows=0; local flush drained cleanly."}},{"op":"replace","path":"/metadata/updated_at","value":"2026-08-08T14:06:54.631Z"}],"before_hash":"45a15f51883d5ca7fdb5d5ab6133612e972a3540fecaa542d50b7e6cc13b8e88","after_hash":"348ba508cce6966eed6d864f9cc4d5bc019c7375b3f04c5ac397f01116608e5d"}
{"ts":"2026-08-08T22:04:38.418Z","author":"harness:claude-code","author_source":"detected","agent_harness":"claude-code","agent_model":"claude-opus-5","agent_model_source":"probe","agent_instance":"c8444ba62ea3e20f4e5098f6","agent_provenance":{"model":{"value":"claude-opus-5","source":"probe"},"effort":{"value":"xhigh","source":"environment"},"role":{"value":"1","source":"environment"},"topic":null,"version":{"value":"2.1.226","source":"probe"}},"op":"comment_add","patch":[{"op":"add","path":"/metadata/comments/139","value":{"created_at":"2026-08-08T22:04:38.418Z","author":"harness:claude-code","text":"Release health 2026-08-08: 2026.8.8 is live on npm as latest and on GitHub Releases, and the published artifact runs under both npx and bunx at that version. The scheduled run at 03:52Z failed the reliability gate on two unresolved high issues (PM-CLI-2S host-capacity ENOSPC, owned by pm-3lhth4; PM-CLI-2Q a correct usage refusal whose event predates the contract-tag producer, now filed as pm-h75tjh). Both were resolved by hand and the cut happened through a manual dispatch at 13:37Z. One release for the day; the same-day guard compares parsed date components rather than a prefix glob, and a tracker-only change set skips the pipeline instead of cutting."}},{"op":"replace","path":"/metadata/updated_at","value":"2026-08-08T22:04:38.418Z"}],"before_hash":"348ba508cce6966eed6d864f9cc4d5bc019c7375b3f04c5ac397f01116608e5d","after_hash":"614022fcd0d2146228a709af4bae4e6ad3d076ad1654b194894c5c09b62a1137"}
{"ts":"2026-08-09T02:03:23.996Z","author":"harness:codex","author_source":"detected","agent_harness":"codex","agent_instance":"b328d74ff33d5397acdbcabe","agent_provenance":{"model":null,"effort":null,"role":null,"topic":{"value":"pm-7zs0","source":"argv"}},"op":"comment_add","patch":[{"op":"add","path":"/metadata/comments/140","value":{"created_at":"2026-08-09T02:03:23.996Z","author":"harness:codex","text":"2026-08-09 release attempt evidence: PR #944 merged as 26370b95a. Auto Release workflow_dispatch run 31289144441 used push=true with telemetry_mode=required and failed closed before tag or publication after passing exact 100/100/100/100 coverage, secrets, packed npx smoke, 88-command temporary dogfood, and candidate packaging. Exact failure: telemetry_query_command_missing because GitHub-hosted release runners intentionally have no private PM_TELEMETRY_QUERY_COMMAND adapter, the already documented pm-ei6x66 boundary. Remote v2026.8.9 tag, GitHub release, and npm 2026.8.9 are absent; npm remains 2026.8.8. Recovery will use the production workflow's telemetry_mode=off contract, while Sentry remains mandatory via the configured SENTRY_PERSONAL_ADMIN_TOKEN and live telemetry delivery is verified separately from an owner-local adapter."}},{"op":"replace","path":"/metadata/updated_at","value":"2026-08-09T02:03:23.996Z"}],"before_hash":"614022fcd0d2146228a709af4bae4e6ad3d076ad1654b194894c5c09b62a1137","after_hash":"069da3ebd4c57467f66c9b657491b894f20ff9105993c2ad4d071e245dae826a"}
{"ts":"2026-08-09T02:30:19.681Z","author":"harness:codex","author_source":"detected","agent_harness":"codex","agent_instance":"b328d74ff33d5397acdbcabe","agent_provenance":{"model":null,"effort":null,"role":null,"topic":{"value":"pm-7zs0","source":"argv"}},"op":"comment_add","patch":[{"op":"add","path":"/metadata/comments/141","value":{"created_at":"2026-08-09T02:30:19.681Z","author":"harness:codex","text":"2026-08-09 release-health closeout: production-contract Auto Release run 31289529224 succeeded and waited for downstream Release run 31289931100. Exactly one v2026.8.9 tag exists; GitHub release is non-draft/non-prerelease; npm latest 2026.8.9 carries SLSA provenance. Independent verify-published-release passed npm integrity, direct and package-selected npx and bunx dispatch, pm-mcp initialization under both executors, all pm/pm-cli/pm-mcp bin mappings, and four missing-bin negative controls. Live Sentry 14-day reliability gate passed at critical=0/high=0 and the Sentry release pm-cli@2026.8.9 is finalized against release commit c44920a62 with zero new groups. Owner-local telemetry health returned status ok with HTTP 200 probe; an inline flush drained 3/3 queued redacted events to zero at 02:29:53Z. The recurring reminder remains open and unclaimed by design."}},{"op":"replace","path":"/metadata/updated_at","value":"2026-08-09T02:30:19.681Z"}],"before_hash":"069da3ebd4c57467f66c9b657491b894f20ff9105993c2ad4d071e245dae826a","after_hash":"704ec481b84f48ee58b583370a90b3b5be7d1907d4c682fe7810f76da8f1069a"}
6 changes: 4 additions & 2 deletions .agents/pm/reminders/pm-7zs0.toon
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ status: open
priority: 2
tags[3]: "area:release",living-map,reliability
created_at: "2026-06-07T10:24:45.889Z"
updated_at: "2026-08-08T22:04:38.418Z"
updated_at: "2026-08-09T02:30:19.681Z"
reminders[1]{at,text}:
"2026-07-31T06:00:00.000Z","Verify the 2026-07-31 daily auto-release: npm latest advanced or a documented skip reason,git tag exists,npx and bunx both run the published artifact,exactly one cut for the day. Then re-arm this reminder for the next day,because reminders do not re-arm on fire."
author: maintainer-agent
Expand Down Expand Up @@ -58,7 +58,7 @@ dependencies[9]:
author: "harness:claude-code"
source_kind: "cli:update:dep"
author_source: detected
comments[140]{created_at,author,text}:
comments[142]{created_at,author,text}:
"2026-06-10T14:44:30.277Z",maintainer-agent,"2026-06-10 daily auto-release (scheduled run 27258655654, 06:50Z) FAILED at sentry-telemetry-gate: PM-CLI-1J 'CommandError: {' — a CommandError whose message was the raw guided-error JSON envelope (code tracker_not_initialized) thrown by an ephemeral temp-dir script (readPmItemsForUpsert, source no longer on disk; 2 events 2026-06-09T21:34Z). Gate classifier fix already landed in PR #197 (fba75fb0, merged 11:34Z, adds 'tracker_not_initialized' to KNOWN_EXPECTED_HANDLED_CLI_ISSUE_PATTERNS) but AFTER the scheduled run. Recovery: resolved PM-CLI-1J in Sentry + re-dispatched auto-release.yml with push=true (run 27284359777). Will verify v2026.6.10 npm publish before closing."
"2026-06-16T11:26:49.976Z",codex-sdk-cli-consolidation-20260616,"Auto-release gate reproduced locally with SENTRY_PERSONAL_ADMIN_TOKEN; failing high issue was PM-CLI-1Q (handled CommandError: all items failed to apply). Added count-agnostic handled pattern 'item(s) failed to apply' and blocking_short_ids/blocking_titles output for diagnostics. Gate now passes in strict mode with max-high=0."
"2026-06-16T11:46:33.866Z",codex-sdk-cli-consolidation-20260616,"Release-health verification: sentry-telemetry gate now passes in strict mode (max-critical=0,max-high=0) after expected handled-CommandError classification update; output now includes blocking_short_ids/blocking_titles for actionable diagnostics."
Expand Down Expand Up @@ -199,6 +199,8 @@ comments[140]{created_at,author,text}:
"2026-08-07T17:13:56.914Z","harness:claude-code","Evening re-verification 2026-08-07, after the morning pass already recorded the three-run picture for this UTC day. State unchanged and still exactly one release for the day: npm dist-tag latest 2026.8.7, tag v2026.8.7 present and unique, package.json 2026.8.7, and the [Unreleased] changelog section empty. The 04:36Z scheduled run failed on sentry-telemetry-gate, the 10:12Z dispatch cut the tag, the 10:24Z dispatch skipped on release_already_cut_today.\n\nOne addition the morning entry does not carry: the trigger asymmetry that makes the scheduled path the least-verified one. On workflow_dispatch, push defaults to false and dry_run to false; on schedule, INPUT_PUSH is hardcoded true. A dispatch run at the default therefore exercises every gate but not the commit-tag-push path, and a dispatch run with push=true exercises a path whose same-day guard then blocks it. Neither dispatch shape reproduces the scheduled shape exactly, and the scheduled shape is the only one the daily guarantee depends on. The two most recent scheduled failures were both repaired and then released by dispatch, so no scheduled run has completed successfully at HEAD since the repairs landed. Rate evidence recorded on pm-e70zh5; the same-day guard's trigger-blindness remains on pm-uenmu9."
"2026-08-08T14:06:54.631Z","harness:codex","2026-08-08 release-health proof: PRs #935 and #938 shipped as the sole v2026.8.8 cut. Auto Release 31259981172 and downstream Release 31260405095 succeeded; npm latest=2026.8.8 and independent npm/npx/bunx/pm-mcp/GitHub verification passed. The initial issue-recovery run 31258567364 failed on a date-specific packaged test assertion and is tracked/fixed by pm-7ipajv. Closing GH #934 triggered guarded run 31261020199, which completed in 50s using the recorded retry/same-day guard and did not create another tag. Live Sentry critical/high=0/0; telemetry error rate=0.99%, missing error-code rows=0; local flush drained cleanly."
"2026-08-08T22:04:38.418Z","harness:claude-code","Release health 2026-08-08: 2026.8.8 is live on npm as latest and on GitHub Releases, and the published artifact runs under both npx and bunx at that version. The scheduled run at 03:52Z failed the reliability gate on two unresolved high issues (PM-CLI-2S host-capacity ENOSPC, owned by pm-3lhth4; PM-CLI-2Q a correct usage refusal whose event predates the contract-tag producer, now filed as pm-h75tjh). Both were resolved by hand and the cut happened through a manual dispatch at 13:37Z. One release for the day; the same-day guard compares parsed date components rather than a prefix glob, and a tracker-only change set skips the pipeline instead of cutting."
"2026-08-09T02:03:23.996Z","harness:codex","2026-08-09 release attempt evidence: PR #944 merged as 26370b95a. Auto Release workflow_dispatch run 31289144441 used push=true with telemetry_mode=required and failed closed before tag or publication after passing exact 100/100/100/100 coverage, secrets, packed npx smoke, 88-command temporary dogfood, and candidate packaging. Exact failure: telemetry_query_command_missing because GitHub-hosted release runners intentionally have no private PM_TELEMETRY_QUERY_COMMAND adapter, the already documented pm-ei6x66 boundary. Remote v2026.8.9 tag, GitHub release, and npm 2026.8.9 are absent; npm remains 2026.8.8. Recovery will use the production workflow's telemetry_mode=off contract, while Sentry remains mandatory via the configured SENTRY_PERSONAL_ADMIN_TOKEN and live telemetry delivery is verified separately from an owner-local adapter."
"2026-08-09T02:30:19.681Z","harness:codex","2026-08-09 release-health closeout: production-contract Auto Release run 31289529224 succeeded and waited for downstream Release run 31289931100. Exactly one v2026.8.9 tag exists; GitHub release is non-draft/non-prerelease; npm latest 2026.8.9 carries SLSA provenance. Independent verify-published-release passed npm integrity, direct and package-selected npx and bunx dispatch, pm-mcp initialization under both executors, all pm/pm-cli/pm-mcp bin mappings, and four missing-bin negative controls. Live Sentry 14-day reliability gate passed at critical=0/high=0 and the Sentry release pm-cli@2026.8.9 is finalized against release commit c44920a62 with zero new groups. Owner-local telemetry health returned status ok with HTTP 200 probe; an inline flush drained 3/3 queued redacted events to zero at 02:29:53Z. The recurring reminder remains open and unclaimed by design."
notes[8]{created_at,author,text}:
"2026-07-02T06:41:55.766Z",claude-code-agent,"2026-07-02: Auto Release run 28569991109 success; tag v2026.7.2 created and npm dist-tags.latest=2026.7.2 verified live via npm view. Release-commit CI/Release/CodeQL/Docs all green. Release health verified."
"2026-07-04T06:16:41.031Z",maintainer-agent,"2026-07-04: Release v2026.7.4 verified — Release workflow 28697208639 succeeded, npm @unbrained/pm-cli@2026.7.4 live, GH release published 06:16Z (not draft). Auto-release healthy."
Expand Down