ci(publish-smoke): event-conditional run-name + outage-duration header note

[claude]

Fixes#14190

What changed

.github/workflows/publish-smoke.yml only:

1. A top-level, event-conditional run-name: that titles each run by the path it actually executes — the scheduled registry canary, a manual workflow_dispatch run (which runs both the canary and the resolve/pack-smoke path per the existing if: conditions — untouched here), or the workflow_run-triggered packed-tarball RC smoke (titled with the triggering Release run's head_sha for source traceability).
2. One sentence appended to the existing header comment stating that outage-duration questions ("how long was publish broken?") are answered from the publish-smoke / packed-tarballs commit-status history on the release-branch head, never from this workflow's run list — because the run list interleaves the weekly canary with RC smokes, and an unlabeled canary green reads as "the RC smoke passed" (the exact misread Publish Smoke's run-list conclusion conflates the weekly registry canary with pack-smoke — a Monday canary green reads as "the RC smoke passed" and cost three seats a six-day duration misread #14190 measured, worth six days).

No gate change: resolve, resolve-guard, pack-smoke, registry-canary, their if: conditions, needs, permissions, and triggers are byte-identical — git diff touches only the new run-name: line and the new header-comment sentence (see diff).

Verification

The rendered run title can only be observed on the next scheduled canary run and the next RC (workflow_run-triggered) run after this merges — noted as an open question below, per the triage's own verification note.

---

Generated by Claude Code

[claude]

Fixes#14190

What changed

.github/workflows/publish-smoke.yml only:

1. A top-level, event-conditional run-name: that titles each run by the path it actually executes — the scheduled registry canary, a manual workflow_dispatch run (which runs both the canary and the resolve/pack-smoke path per the existing if: conditions — untouched here), or the workflow_run-triggered packed-tarball RC smoke (titled with the triggering Release run's head_sha for source traceability).
2. One sentence appended to the existing header comment stating that outage-duration questions ("how long was publish broken?") are answered from the publish-smoke / packed-tarballs commit-status history on the release-branch head, never from this workflow's run list — because the run list interleaves the weekly canary with RC smokes, and an unlabeled canary green reads as "the RC smoke passed" (the exact misread Publish Smoke's run-list conclusion conflates the weekly registry canary with pack-smoke — a Monday canary green reads as "the RC smoke passed" and cost three seats a six-day duration misread #14190 measured, worth six days).

No gate change: resolve, resolve-guard, pack-smoke, registry-canary, their if: conditions, needs, permissions, and triggers are byte-identical — git diff touches only the new run-name: line and the new header-comment sentence (see diff).

Verification

The rendered run title can only be observed on the next scheduled canary run and the next RC (workflow_run-triggered) run after this merges — noted as an open question below, per the triage's own verification note.

---

Generated by Claude Code

[claude]

Fixes#14190

What changed

.github/workflows/publish-smoke.yml only:

1. A top-level, event-conditional run-name: that titles each run by the path it actually executes — the scheduled registry canary, a manual workflow_dispatch run (which runs both the canary and the resolve/pack-smoke path per the existing if: conditions — untouched here), or the workflow_run-triggered packed-tarball RC smoke (titled with the triggering Release run's head_sha for source traceability).
2. One sentence appended to the existing header comment stating that outage-duration questions ("how long was publish broken?") are answered from the publish-smoke / packed-tarballs commit-status history on the release-branch head, never from this workflow's run list — because the run list interleaves the weekly canary with RC smokes, and an unlabeled canary green reads as "the RC smoke passed" (the exact misread Publish Smoke's run-list conclusion conflates the weekly registry canary with pack-smoke — a Monday canary green reads as "the RC smoke passed" and cost three seats a six-day duration misread #14190 measured, worth six days).

No gate change: resolve, resolve-guard, pack-smoke, registry-canary, their if: conditions, needs, permissions, and triggers are byte-identical — git diff touches only the new run-name: line and the new header-comment sentence (see diff).

Verification

The rendered run title can only be observed on the next scheduled canary run and the next RC (workflow_run-triggered) run after this merges — noted as an open question below, per the triage's own verification note.

---

Generated by Claude Code

[claude]

Fixes#14190

What changed

.github/workflows/publish-smoke.yml only:

1. A top-level, event-conditional run-name: that titles each run by the path it actually executes — the scheduled registry canary, a manual workflow_dispatch run (which runs both the canary and the resolve/pack-smoke path per the existing if: conditions — untouched here), or the workflow_run-triggered packed-tarball RC smoke (titled with the triggering Release run's head_sha for source traceability).
2. One sentence appended to the existing header comment stating that outage-duration questions ("how long was publish broken?") are answered from the publish-smoke / packed-tarballs commit-status history on the release-branch head, never from this workflow's run list — because the run list interleaves the weekly canary with RC smokes, and an unlabeled canary green reads as "the RC smoke passed" (the exact misread Publish Smoke's run-list conclusion conflates the weekly registry canary with pack-smoke — a Monday canary green reads as "the RC smoke passed" and cost three seats a six-day duration misread #14190 measured, worth six days).

No gate change: resolve, resolve-guard, pack-smoke, registry-canary, their if: conditions, needs, permissions, and triggers are byte-identical — git diff touches only the new run-name: line and the new header-comment sentence (see diff).

Verification

The rendered run title can only be observed on the next scheduled canary run and the next RC (workflow_run-triggered) run after this merges — noted as an open question below, per the triage's own verification note.

---

Generated by Claude Code

[claude]

Fixes#14190

What changed

.github/workflows/publish-smoke.yml only:

1. A top-level, event-conditional run-name: that titles each run by the path it actually executes — the scheduled registry canary, a manual workflow_dispatch run (which runs both the canary and the resolve/pack-smoke path per the existing if: conditions — untouched here), or the workflow_run-triggered packed-tarball RC smoke (titled with the triggering Release run's head_sha for source traceability).
2. One sentence appended to the existing header comment stating that outage-duration questions ("how long was publish broken?") are answered from the publish-smoke / packed-tarballs commit-status history on the release-branch head, never from this workflow's run list — because the run list interleaves the weekly canary with RC smokes, and an unlabeled canary green reads as "the RC smoke passed" (the exact misread Publish Smoke's run-list conclusion conflates the weekly registry canary with pack-smoke — a Monday canary green reads as "the RC smoke passed" and cost three seats a six-day duration misread #14190 measured, worth six days).

No gate change: resolve, resolve-guard, pack-smoke, registry-canary, their if: conditions, needs, permissions, and triggers are byte-identical — git diff touches only the new run-name: line and the new header-comment sentence (see diff).

Verification

The rendered run title can only be observed on the next scheduled canary run and the next RC (workflow_run-triggered) run after this merges — noted as an open question below, per the triage's own verification note.

---

Generated by Claude Code

[claude]

Fixes#14190

What changed

.github/workflows/publish-smoke.yml only:

1. A top-level, event-conditional run-name: that titles each run by the path it actually executes — the scheduled registry canary, a manual workflow_dispatch run (which runs both the canary and the resolve/pack-smoke path per the existing if: conditions — untouched here), or the workflow_run-triggered packed-tarball RC smoke (titled with the triggering Release run's head_sha for source traceability).
2. One sentence appended to the existing header comment stating that outage-duration questions ("how long was publish broken?") are answered from the publish-smoke / packed-tarballs commit-status history on the release-branch head, never from this workflow's run list — because the run list interleaves the weekly canary with RC smokes, and an unlabeled canary green reads as "the RC smoke passed" (the exact misread Publish Smoke's run-list conclusion conflates the weekly registry canary with pack-smoke — a Monday canary green reads as "the RC smoke passed" and cost three seats a six-day duration misread #14190 measured, worth six days).

No gate change: resolve, resolve-guard, pack-smoke, registry-canary, their if: conditions, needs, permissions, and triggers are byte-identical — git diff touches only the new run-name: line and the new header-comment sentence (see diff).

Verification

The rendered run title can only be observed on the next scheduled canary run and the next RC (workflow_run-triggered) run after this merges — noted as an open question below, per the triage's own verification note.

---

Generated by Claude Code

[claude]

Fixes#14190

What changed

.github/workflows/publish-smoke.yml only:

1. A top-level, event-conditional run-name: that titles each run by the path it actually executes — the scheduled registry canary, a manual workflow_dispatch run (which runs both the canary and the resolve/pack-smoke path per the existing if: conditions — untouched here), or the workflow_run-triggered packed-tarball RC smoke (titled with the triggering Release run's head_sha for source traceability).
2. One sentence appended to the existing header comment stating that outage-duration questions ("how long was publish broken?") are answered from the publish-smoke / packed-tarballs commit-status history on the release-branch head, never from this workflow's run list — because the run list interleaves the weekly canary with RC smokes, and an unlabeled canary green reads as "the RC smoke passed" (the exact misread Publish Smoke's run-list conclusion conflates the weekly registry canary with pack-smoke — a Monday canary green reads as "the RC smoke passed" and cost three seats a six-day duration misread #14190 measured, worth six days).

No gate change: resolve, resolve-guard, pack-smoke, registry-canary, their if: conditions, needs, permissions, and triggers are byte-identical — git diff touches only the new run-name: line and the new header-comment sentence (see diff).

Verification

The rendered run title can only be observed on the next scheduled canary run and the next RC (workflow_run-triggered) run after this merges — noted as an open question below, per the triage's own verification note.

---

Generated by Claude Code

[claude]

Fixes#14190

What changed

.github/workflows/publish-smoke.yml only:

1. A top-level, event-conditional run-name: that titles each run by the path it actually executes — the scheduled registry canary, a manual workflow_dispatch run (which runs both the canary and the resolve/pack-smoke path per the existing if: conditions — untouched here), or the workflow_run-triggered packed-tarball RC smoke (titled with the triggering Release run's head_sha for source traceability).
2. One sentence appended to the existing header comment stating that outage-duration questions ("how long was publish broken?") are answered from the publish-smoke / packed-tarballs commit-status history on the release-branch head, never from this workflow's run list — because the run list interleaves the weekly canary with RC smokes, and an unlabeled canary green reads as "the RC smoke passed" (the exact misread Publish Smoke's run-list conclusion conflates the weekly registry canary with pack-smoke — a Monday canary green reads as "the RC smoke passed" and cost three seats a six-day duration misread #14190 measured, worth six days).

No gate change: resolve, resolve-guard, pack-smoke, registry-canary, their if: conditions, needs, permissions, and triggers are byte-identical — git diff touches only the new run-name: line and the new header-comment sentence (see diff).

Verification

The rendered run title can only be observed on the next scheduled canary run and the next RC (workflow_run-triggered) run after this merges — noted as an open question below, per the triage's own verification note.

---

Generated by Claude Code