Clean up transfer artifacts surgically at consumption, not blanket-delete by ptr727 · Pull Request #216 · ptr727/ProjectTemplate

ptr727 · 2026-06-26T17:51:30Z

Problem

Closes#214. The cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). It was added to stop huge release-asset-* artifacts (KiCadLibrary) filling the storage quota, but it overstepped — it also destroys diagnostic/log artifacts and the build-records actions emit automatically, exactly what you need to debug a failed run.

Fix

Per maintainer guidance: surgical cleanup + retention-days: 1 + normal failed-job surfacing, no naming-pattern terminal backstop (overkill).

Consume-then-delete: each transfer artifact is deleted by exact name/pattern at the job that consumes it — the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing.
Permissions: actions: write granted where deletion happens — at the publish caller for the reusable github-release job, and on publish-pypi directly (was actions: read).
Removed the blanket cleanup-artifacts job from both workflows. retention-days: 1 (already on every transfer upload) is the failure-path backstop; a failed run is reported normally. Diagnostics/build-records survive — the intended outcome.
Pattern: rewrote the AGENTS.md "Artifact retention" rule to the consume-then-delete shape so downstream customizations honor it.

Verification

actionlint (Docker, bundles shellcheck) clean on all three changed workflows; markdownlint clean on AGENTS.md; CRLF preserved.
check-workflow-status (the required-status-check aggregator) does not depend on the removed job, so the merge gate is unaffected.

🤖 Generated with Claude Code

…lete Fixes#214. The terminal cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). Added to control huge release-asset artifacts (KiCadLibrary) filling the storage quota, it overstepped: it also destroyed diagnostic/log artifacts needed to debug a failed run. - Delete each transfer artifact at its point of consumption, by exact name/pattern: the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing. Grant actions:write where deletion happens (the publish caller for the reusable github-release job; publish-pypi directly). - Remove the blanket cleanup-artifacts job from both workflows. retention-days:1 on every upload is the failure-path backstop (a job that dies before its consumer leaves its artifact, reaped within a day); a failed run is reported normally. Diagnostics and build-records are no longer destroyed. - Rewrite the AGENTS.md artifact-retention rule to the consume-then-delete pattern so downstream job customizations honor it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR updates the repository's GitHub Actions artifact-retention approach to avoid blanket-deleting all run artifacts (which can remove diagnostics), and instead deletes only inter-job transfer artifacts at the point they are consumed. It also updates the documented workflow conventions accordingly.

Changes:

Document the new "consume-then-delete" artifact cleanup strategy in AGENTS.md.
Remove the terminal cleanup-artifacts jobs from test-pull-request.yml and publish-release.yml.
Add targeted deletion steps: release-asset-<branch>-* cleanup in build-release-task.yml after attaching to the GitHub release, and pypilibrary-build-<branch> cleanup in publish-release.yml after publishing to PyPI (including permission updates).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
AGENTS.md	Updates the workflow convention to require surgical, consume-time deletion of transfer artifacts and to avoid blanket deletion.
.github/workflows/test-pull-request.yml	Removes the terminal job that deleted all run artifacts.
.github/workflows/publish-release.yml	Grants `actions: write` where needed and deletes the consumed PyPI build artifact after publishing; removes blanket cleanup job.
.github/workflows/build-release-task.yml	Deletes consumed `release-asset-<branch>-*` artifacts after attaching them to the GitHub release.

A listing/delete API hiccup must not red a job whose release/publish already succeeded: tolerate a failed artifact-list (warn + skip) and add continue-on-error, and delete every matching artifact id rather than a single scalar (a rerun can upload duplicates). The retention-days: 1 backstop covers anything missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…rtifact-cleanup-214

Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T17:51:30Z

Problem

Closes#214. The cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). It was added to stop huge release-asset-* artifacts (KiCadLibrary) filling the storage quota, but it overstepped — it also destroys diagnostic/log artifacts and the build-records actions emit automatically, exactly what you need to debug a failed run.

Fix

Per maintainer guidance: surgical cleanup + retention-days: 1 + normal failed-job surfacing, no naming-pattern terminal backstop (overkill).

Consume-then-delete: each transfer artifact is deleted by exact name/pattern at the job that consumes it — the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing.
Permissions: actions: write granted where deletion happens — at the publish caller for the reusable github-release job, and on publish-pypi directly (was actions: read).
Removed the blanket cleanup-artifacts job from both workflows. retention-days: 1 (already on every transfer upload) is the failure-path backstop; a failed run is reported normally. Diagnostics/build-records survive — the intended outcome.
Pattern: rewrote the AGENTS.md "Artifact retention" rule to the consume-then-delete shape so downstream customizations honor it.

Verification

actionlint (Docker, bundles shellcheck) clean on all three changed workflows; markdownlint clean on AGENTS.md; CRLF preserved.
check-workflow-status (the required-status-check aggregator) does not depend on the removed job, so the merge gate is unaffected.

🤖 Generated with Claude Code

…lete Fixes#214. The terminal cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). Added to control huge release-asset artifacts (KiCadLibrary) filling the storage quota, it overstepped: it also destroyed diagnostic/log artifacts needed to debug a failed run. - Delete each transfer artifact at its point of consumption, by exact name/pattern: the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing. Grant actions:write where deletion happens (the publish caller for the reusable github-release job; publish-pypi directly). - Remove the blanket cleanup-artifacts job from both workflows. retention-days:1 on every upload is the failure-path backstop (a job that dies before its consumer leaves its artifact, reaped within a day); a failed run is reported normally. Diagnostics and build-records are no longer destroyed. - Rewrite the AGENTS.md artifact-retention rule to the consume-then-delete pattern so downstream job customizations honor it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR updates the repository's GitHub Actions artifact-retention approach to avoid blanket-deleting all run artifacts (which can remove diagnostics), and instead deletes only inter-job transfer artifacts at the point they are consumed. It also updates the documented workflow conventions accordingly.

Changes:

Document the new "consume-then-delete" artifact cleanup strategy in AGENTS.md.
Remove the terminal cleanup-artifacts jobs from test-pull-request.yml and publish-release.yml.
Add targeted deletion steps: release-asset-<branch>-* cleanup in build-release-task.yml after attaching to the GitHub release, and pypilibrary-build-<branch> cleanup in publish-release.yml after publishing to PyPI (including permission updates).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
AGENTS.md	Updates the workflow convention to require surgical, consume-time deletion of transfer artifacts and to avoid blanket deletion.
.github/workflows/test-pull-request.yml	Removes the terminal job that deleted all run artifacts.
.github/workflows/publish-release.yml	Grants `actions: write` where needed and deletes the consumed PyPI build artifact after publishing; removes blanket cleanup job.
.github/workflows/build-release-task.yml	Deletes consumed `release-asset-<branch>-*` artifacts after attaching them to the GitHub release.

A listing/delete API hiccup must not red a job whose release/publish already succeeded: tolerate a failed artifact-list (warn + skip) and add continue-on-error, and delete every matching artifact id rather than a single scalar (a rerun can upload duplicates). The retention-days: 1 backstop covers anything missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…rtifact-cleanup-214

Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T17:51:30Z

Problem

Closes#214. The cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). It was added to stop huge release-asset-* artifacts (KiCadLibrary) filling the storage quota, but it overstepped — it also destroys diagnostic/log artifacts and the build-records actions emit automatically, exactly what you need to debug a failed run.

Fix

Per maintainer guidance: surgical cleanup + retention-days: 1 + normal failed-job surfacing, no naming-pattern terminal backstop (overkill).

Consume-then-delete: each transfer artifact is deleted by exact name/pattern at the job that consumes it — the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing.
Permissions: actions: write granted where deletion happens — at the publish caller for the reusable github-release job, and on publish-pypi directly (was actions: read).
Removed the blanket cleanup-artifacts job from both workflows. retention-days: 1 (already on every transfer upload) is the failure-path backstop; a failed run is reported normally. Diagnostics/build-records survive — the intended outcome.
Pattern: rewrote the AGENTS.md "Artifact retention" rule to the consume-then-delete shape so downstream customizations honor it.

Verification

actionlint (Docker, bundles shellcheck) clean on all three changed workflows; markdownlint clean on AGENTS.md; CRLF preserved.
check-workflow-status (the required-status-check aggregator) does not depend on the removed job, so the merge gate is unaffected.

🤖 Generated with Claude Code

…lete Fixes#214. The terminal cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). Added to control huge release-asset artifacts (KiCadLibrary) filling the storage quota, it overstepped: it also destroyed diagnostic/log artifacts needed to debug a failed run. - Delete each transfer artifact at its point of consumption, by exact name/pattern: the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing. Grant actions:write where deletion happens (the publish caller for the reusable github-release job; publish-pypi directly). - Remove the blanket cleanup-artifacts job from both workflows. retention-days:1 on every upload is the failure-path backstop (a job that dies before its consumer leaves its artifact, reaped within a day); a failed run is reported normally. Diagnostics and build-records are no longer destroyed. - Rewrite the AGENTS.md artifact-retention rule to the consume-then-delete pattern so downstream job customizations honor it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR updates the repository's GitHub Actions artifact-retention approach to avoid blanket-deleting all run artifacts (which can remove diagnostics), and instead deletes only inter-job transfer artifacts at the point they are consumed. It also updates the documented workflow conventions accordingly.

Changes:

Document the new "consume-then-delete" artifact cleanup strategy in AGENTS.md.
Remove the terminal cleanup-artifacts jobs from test-pull-request.yml and publish-release.yml.
Add targeted deletion steps: release-asset-<branch>-* cleanup in build-release-task.yml after attaching to the GitHub release, and pypilibrary-build-<branch> cleanup in publish-release.yml after publishing to PyPI (including permission updates).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
AGENTS.md	Updates the workflow convention to require surgical, consume-time deletion of transfer artifacts and to avoid blanket deletion.
.github/workflows/test-pull-request.yml	Removes the terminal job that deleted all run artifacts.
.github/workflows/publish-release.yml	Grants `actions: write` where needed and deletes the consumed PyPI build artifact after publishing; removes blanket cleanup job.
.github/workflows/build-release-task.yml	Deletes consumed `release-asset-<branch>-*` artifacts after attaching them to the GitHub release.

A listing/delete API hiccup must not red a job whose release/publish already succeeded: tolerate a failed artifact-list (warn + skip) and add continue-on-error, and delete every matching artifact id rather than a single scalar (a rerun can upload duplicates). The retention-days: 1 backstop covers anything missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…rtifact-cleanup-214

Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T17:51:30Z

Problem

Closes#214. The cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). It was added to stop huge release-asset-* artifacts (KiCadLibrary) filling the storage quota, but it overstepped — it also destroys diagnostic/log artifacts and the build-records actions emit automatically, exactly what you need to debug a failed run.

Fix

Per maintainer guidance: surgical cleanup + retention-days: 1 + normal failed-job surfacing, no naming-pattern terminal backstop (overkill).

Consume-then-delete: each transfer artifact is deleted by exact name/pattern at the job that consumes it — the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing.
Permissions: actions: write granted where deletion happens — at the publish caller for the reusable github-release job, and on publish-pypi directly (was actions: read).
Removed the blanket cleanup-artifacts job from both workflows. retention-days: 1 (already on every transfer upload) is the failure-path backstop; a failed run is reported normally. Diagnostics/build-records survive — the intended outcome.
Pattern: rewrote the AGENTS.md "Artifact retention" rule to the consume-then-delete shape so downstream customizations honor it.

Verification

actionlint (Docker, bundles shellcheck) clean on all three changed workflows; markdownlint clean on AGENTS.md; CRLF preserved.
check-workflow-status (the required-status-check aggregator) does not depend on the removed job, so the merge gate is unaffected.

🤖 Generated with Claude Code

…lete Fixes#214. The terminal cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). Added to control huge release-asset artifacts (KiCadLibrary) filling the storage quota, it overstepped: it also destroyed diagnostic/log artifacts needed to debug a failed run. - Delete each transfer artifact at its point of consumption, by exact name/pattern: the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing. Grant actions:write where deletion happens (the publish caller for the reusable github-release job; publish-pypi directly). - Remove the blanket cleanup-artifacts job from both workflows. retention-days:1 on every upload is the failure-path backstop (a job that dies before its consumer leaves its artifact, reaped within a day); a failed run is reported normally. Diagnostics and build-records are no longer destroyed. - Rewrite the AGENTS.md artifact-retention rule to the consume-then-delete pattern so downstream job customizations honor it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR updates the repository's GitHub Actions artifact-retention approach to avoid blanket-deleting all run artifacts (which can remove diagnostics), and instead deletes only inter-job transfer artifacts at the point they are consumed. It also updates the documented workflow conventions accordingly.

Changes:

Document the new "consume-then-delete" artifact cleanup strategy in AGENTS.md.
Remove the terminal cleanup-artifacts jobs from test-pull-request.yml and publish-release.yml.
Add targeted deletion steps: release-asset-<branch>-* cleanup in build-release-task.yml after attaching to the GitHub release, and pypilibrary-build-<branch> cleanup in publish-release.yml after publishing to PyPI (including permission updates).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
AGENTS.md	Updates the workflow convention to require surgical, consume-time deletion of transfer artifacts and to avoid blanket deletion.
.github/workflows/test-pull-request.yml	Removes the terminal job that deleted all run artifacts.
.github/workflows/publish-release.yml	Grants `actions: write` where needed and deletes the consumed PyPI build artifact after publishing; removes blanket cleanup job.
.github/workflows/build-release-task.yml	Deletes consumed `release-asset-<branch>-*` artifacts after attaching them to the GitHub release.

A listing/delete API hiccup must not red a job whose release/publish already succeeded: tolerate a failed artifact-list (warn + skip) and add continue-on-error, and delete every matching artifact id rather than a single scalar (a rerun can upload duplicates). The retention-days: 1 backstop covers anything missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…rtifact-cleanup-214

Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T17:51:30Z

Problem

Closes#214. The cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). It was added to stop huge release-asset-* artifacts (KiCadLibrary) filling the storage quota, but it overstepped — it also destroys diagnostic/log artifacts and the build-records actions emit automatically, exactly what you need to debug a failed run.

Fix

Per maintainer guidance: surgical cleanup + retention-days: 1 + normal failed-job surfacing, no naming-pattern terminal backstop (overkill).

Consume-then-delete: each transfer artifact is deleted by exact name/pattern at the job that consumes it — the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing.
Permissions: actions: write granted where deletion happens — at the publish caller for the reusable github-release job, and on publish-pypi directly (was actions: read).
Removed the blanket cleanup-artifacts job from both workflows. retention-days: 1 (already on every transfer upload) is the failure-path backstop; a failed run is reported normally. Diagnostics/build-records survive — the intended outcome.
Pattern: rewrote the AGENTS.md "Artifact retention" rule to the consume-then-delete shape so downstream customizations honor it.

Verification

actionlint (Docker, bundles shellcheck) clean on all three changed workflows; markdownlint clean on AGENTS.md; CRLF preserved.
check-workflow-status (the required-status-check aggregator) does not depend on the removed job, so the merge gate is unaffected.

🤖 Generated with Claude Code

…lete Fixes#214. The terminal cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). Added to control huge release-asset artifacts (KiCadLibrary) filling the storage quota, it overstepped: it also destroyed diagnostic/log artifacts needed to debug a failed run. - Delete each transfer artifact at its point of consumption, by exact name/pattern: the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing. Grant actions:write where deletion happens (the publish caller for the reusable github-release job; publish-pypi directly). - Remove the blanket cleanup-artifacts job from both workflows. retention-days:1 on every upload is the failure-path backstop (a job that dies before its consumer leaves its artifact, reaped within a day); a failed run is reported normally. Diagnostics and build-records are no longer destroyed. - Rewrite the AGENTS.md artifact-retention rule to the consume-then-delete pattern so downstream job customizations honor it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR updates the repository's GitHub Actions artifact-retention approach to avoid blanket-deleting all run artifacts (which can remove diagnostics), and instead deletes only inter-job transfer artifacts at the point they are consumed. It also updates the documented workflow conventions accordingly.

Changes:

Document the new "consume-then-delete" artifact cleanup strategy in AGENTS.md.
Remove the terminal cleanup-artifacts jobs from test-pull-request.yml and publish-release.yml.
Add targeted deletion steps: release-asset-<branch>-* cleanup in build-release-task.yml after attaching to the GitHub release, and pypilibrary-build-<branch> cleanup in publish-release.yml after publishing to PyPI (including permission updates).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
AGENTS.md	Updates the workflow convention to require surgical, consume-time deletion of transfer artifacts and to avoid blanket deletion.
.github/workflows/test-pull-request.yml	Removes the terminal job that deleted all run artifacts.
.github/workflows/publish-release.yml	Grants `actions: write` where needed and deletes the consumed PyPI build artifact after publishing; removes blanket cleanup job.
.github/workflows/build-release-task.yml	Deletes consumed `release-asset-<branch>-*` artifacts after attaching them to the GitHub release.

A listing/delete API hiccup must not red a job whose release/publish already succeeded: tolerate a failed artifact-list (warn + skip) and add continue-on-error, and delete every matching artifact id rather than a single scalar (a rerun can upload duplicates). The retention-days: 1 backstop covers anything missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…rtifact-cleanup-214

Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T17:51:30Z

Problem

Closes#214. The cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). It was added to stop huge release-asset-* artifacts (KiCadLibrary) filling the storage quota, but it overstepped — it also destroys diagnostic/log artifacts and the build-records actions emit automatically, exactly what you need to debug a failed run.

Fix

Per maintainer guidance: surgical cleanup + retention-days: 1 + normal failed-job surfacing, no naming-pattern terminal backstop (overkill).

Consume-then-delete: each transfer artifact is deleted by exact name/pattern at the job that consumes it — the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing.
Permissions: actions: write granted where deletion happens — at the publish caller for the reusable github-release job, and on publish-pypi directly (was actions: read).
Removed the blanket cleanup-artifacts job from both workflows. retention-days: 1 (already on every transfer upload) is the failure-path backstop; a failed run is reported normally. Diagnostics/build-records survive — the intended outcome.
Pattern: rewrote the AGENTS.md "Artifact retention" rule to the consume-then-delete shape so downstream customizations honor it.

Verification

actionlint (Docker, bundles shellcheck) clean on all three changed workflows; markdownlint clean on AGENTS.md; CRLF preserved.
check-workflow-status (the required-status-check aggregator) does not depend on the removed job, so the merge gate is unaffected.

🤖 Generated with Claude Code

…lete Fixes#214. The terminal cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). Added to control huge release-asset artifacts (KiCadLibrary) filling the storage quota, it overstepped: it also destroyed diagnostic/log artifacts needed to debug a failed run. - Delete each transfer artifact at its point of consumption, by exact name/pattern: the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing. Grant actions:write where deletion happens (the publish caller for the reusable github-release job; publish-pypi directly). - Remove the blanket cleanup-artifacts job from both workflows. retention-days:1 on every upload is the failure-path backstop (a job that dies before its consumer leaves its artifact, reaped within a day); a failed run is reported normally. Diagnostics and build-records are no longer destroyed. - Rewrite the AGENTS.md artifact-retention rule to the consume-then-delete pattern so downstream job customizations honor it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR updates the repository's GitHub Actions artifact-retention approach to avoid blanket-deleting all run artifacts (which can remove diagnostics), and instead deletes only inter-job transfer artifacts at the point they are consumed. It also updates the documented workflow conventions accordingly.

Changes:

Document the new "consume-then-delete" artifact cleanup strategy in AGENTS.md.
Remove the terminal cleanup-artifacts jobs from test-pull-request.yml and publish-release.yml.
Add targeted deletion steps: release-asset-<branch>-* cleanup in build-release-task.yml after attaching to the GitHub release, and pypilibrary-build-<branch> cleanup in publish-release.yml after publishing to PyPI (including permission updates).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
AGENTS.md	Updates the workflow convention to require surgical, consume-time deletion of transfer artifacts and to avoid blanket deletion.
.github/workflows/test-pull-request.yml	Removes the terminal job that deleted all run artifacts.
.github/workflows/publish-release.yml	Grants `actions: write` where needed and deletes the consumed PyPI build artifact after publishing; removes blanket cleanup job.
.github/workflows/build-release-task.yml	Deletes consumed `release-asset-<branch>-*` artifacts after attaching them to the GitHub release.

A listing/delete API hiccup must not red a job whose release/publish already succeeded: tolerate a failed artifact-list (warn + skip) and add continue-on-error, and delete every matching artifact id rather than a single scalar (a rerun can upload duplicates). The retention-days: 1 backstop covers anything missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…rtifact-cleanup-214

Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T17:51:30Z

Problem

Closes#214. The cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). It was added to stop huge release-asset-* artifacts (KiCadLibrary) filling the storage quota, but it overstepped — it also destroys diagnostic/log artifacts and the build-records actions emit automatically, exactly what you need to debug a failed run.

Fix

Per maintainer guidance: surgical cleanup + retention-days: 1 + normal failed-job surfacing, no naming-pattern terminal backstop (overkill).

Consume-then-delete: each transfer artifact is deleted by exact name/pattern at the job that consumes it — the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing.
Permissions: actions: write granted where deletion happens — at the publish caller for the reusable github-release job, and on publish-pypi directly (was actions: read).
Removed the blanket cleanup-artifacts job from both workflows. retention-days: 1 (already on every transfer upload) is the failure-path backstop; a failed run is reported normally. Diagnostics/build-records survive — the intended outcome.
Pattern: rewrote the AGENTS.md "Artifact retention" rule to the consume-then-delete shape so downstream customizations honor it.

Verification

actionlint (Docker, bundles shellcheck) clean on all three changed workflows; markdownlint clean on AGENTS.md; CRLF preserved.
check-workflow-status (the required-status-check aggregator) does not depend on the removed job, so the merge gate is unaffected.

🤖 Generated with Claude Code

…lete Fixes#214. The terminal cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). Added to control huge release-asset artifacts (KiCadLibrary) filling the storage quota, it overstepped: it also destroyed diagnostic/log artifacts needed to debug a failed run. - Delete each transfer artifact at its point of consumption, by exact name/pattern: the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing. Grant actions:write where deletion happens (the publish caller for the reusable github-release job; publish-pypi directly). - Remove the blanket cleanup-artifacts job from both workflows. retention-days:1 on every upload is the failure-path backstop (a job that dies before its consumer leaves its artifact, reaped within a day); a failed run is reported normally. Diagnostics and build-records are no longer destroyed. - Rewrite the AGENTS.md artifact-retention rule to the consume-then-delete pattern so downstream job customizations honor it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR updates the repository's GitHub Actions artifact-retention approach to avoid blanket-deleting all run artifacts (which can remove diagnostics), and instead deletes only inter-job transfer artifacts at the point they are consumed. It also updates the documented workflow conventions accordingly.

Changes:

Document the new "consume-then-delete" artifact cleanup strategy in AGENTS.md.
Remove the terminal cleanup-artifacts jobs from test-pull-request.yml and publish-release.yml.
Add targeted deletion steps: release-asset-<branch>-* cleanup in build-release-task.yml after attaching to the GitHub release, and pypilibrary-build-<branch> cleanup in publish-release.yml after publishing to PyPI (including permission updates).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
AGENTS.md	Updates the workflow convention to require surgical, consume-time deletion of transfer artifacts and to avoid blanket deletion.
.github/workflows/test-pull-request.yml	Removes the terminal job that deleted all run artifacts.
.github/workflows/publish-release.yml	Grants `actions: write` where needed and deletes the consumed PyPI build artifact after publishing; removes blanket cleanup job.
.github/workflows/build-release-task.yml	Deletes consumed `release-asset-<branch>-*` artifacts after attaching them to the GitHub release.

A listing/delete API hiccup must not red a job whose release/publish already succeeded: tolerate a failed artifact-list (warn + skip) and add continue-on-error, and delete every matching artifact id rather than a single scalar (a rerun can upload duplicates). The retention-days: 1 backstop covers anything missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…rtifact-cleanup-214

Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

ptr727 · 2026-06-26T17:51:30Z

Problem

Closes#214. The cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). It was added to stop huge release-asset-* artifacts (KiCadLibrary) filling the storage quota, but it overstepped — it also destroys diagnostic/log artifacts and the build-records actions emit automatically, exactly what you need to debug a failed run.

Fix

Per maintainer guidance: surgical cleanup + retention-days: 1 + normal failed-job surfacing, no naming-pattern terminal backstop (overkill).

Consume-then-delete: each transfer artifact is deleted by exact name/pattern at the job that consumes it — the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing.
Permissions: actions: write granted where deletion happens — at the publish caller for the reusable github-release job, and on publish-pypi directly (was actions: read).
Removed the blanket cleanup-artifacts job from both workflows. retention-days: 1 (already on every transfer upload) is the failure-path backstop; a failed run is reported normally. Diagnostics/build-records survive — the intended outcome.
Pattern: rewrote the AGENTS.md "Artifact retention" rule to the consume-then-delete shape so downstream customizations honor it.

Verification

actionlint (Docker, bundles shellcheck) clean on all three changed workflows; markdownlint clean on AGENTS.md; CRLF preserved.
check-workflow-status (the required-status-check aggregator) does not depend on the removed job, so the merge gate is unaffected.

🤖 Generated with Claude Code

…lete Fixes#214. The terminal cleanup-artifacts job (duplicated in test-pull-request.yml and publish-release.yml) blanket-deleted every run artifact (.artifacts[].id). Added to control huge release-asset artifacts (KiCadLibrary) filling the storage quota, it overstepped: it also destroyed diagnostic/log artifacts needed to debug a failed run. - Delete each transfer artifact at its point of consumption, by exact name/pattern: the github-release job deletes release-asset-<branch>-* after attaching them to the release; publish-pypi deletes pypilibrary-build-<branch> after publishing. Grant actions:write where deletion happens (the publish caller for the reusable github-release job; publish-pypi directly). - Remove the blanket cleanup-artifacts job from both workflows. retention-days:1 on every upload is the failure-path backstop (a job that dies before its consumer leaves its artifact, reaped within a day); a failed run is reported normally. Diagnostics and build-records are no longer destroyed. - Rewrite the AGENTS.md artifact-retention rule to the consume-then-delete pattern so downstream job customizations honor it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Copilot

Pull request overview

This PR updates the repository's GitHub Actions artifact-retention approach to avoid blanket-deleting all run artifacts (which can remove diagnostics), and instead deletes only inter-job transfer artifacts at the point they are consumed. It also updates the documented workflow conventions accordingly.

Changes:

Document the new "consume-then-delete" artifact cleanup strategy in AGENTS.md.
Remove the terminal cleanup-artifacts jobs from test-pull-request.yml and publish-release.yml.
Add targeted deletion steps: release-asset-<branch>-* cleanup in build-release-task.yml after attaching to the GitHub release, and pypilibrary-build-<branch> cleanup in publish-release.yml after publishing to PyPI (including permission updates).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
AGENTS.md	Updates the workflow convention to require surgical, consume-time deletion of transfer artifacts and to avoid blanket deletion.
.github/workflows/test-pull-request.yml	Removes the terminal job that deleted all run artifacts.
.github/workflows/publish-release.yml	Grants `actions: write` where needed and deletes the consumed PyPI build artifact after publishing; removes blanket cleanup job.
.github/workflows/build-release-task.yml	Deletes consumed `release-asset-<branch>-*` artifacts after attaching them to the GitHub release.

A listing/delete API hiccup must not red a job whose release/publish already succeeded: tolerate a failed artifact-list (warn + skip) and add continue-on-error, and delete every matching artifact id rather than a single scalar (a rerun can upload duplicates). The retention-days: 1 backstop covers anything missed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…rtifact-cleanup-214

Promote the accumulated `develop` work to `main`. Twelve changes since the last promotion: - Add `WORKFLOW.md`: workflow style, architecture, behavioral contract, test methodology (#223) - Use NBGV `IGNORE_GITHUB_REF` instead of the ineffective `GITHUB_REF` override (#222) - Skip validate-release on smoke builds (#220) - Gate asset delete on the release create/refresh condition (#218) - Ship branch rulesets as versioned JSON in the re-sync / drift loop (#212) - Clean up transfer artifacts surgically at consumption, not blanket-delete (#216) - Version each publish leg against its own branch; validate at entry (#215) - Consolidate workspace configurations into a unified ProjectTemplate workspace (#210) - Template convergence barrier: absorb pins, generic release + docker-readme, carry-whole-file (#207) - Key merge-bot concurrency on PR number, not `github.ref` (#206) - Codify orchestrated re-sync personas and full-replacement rule (#205) - Lead action pins; affirm pattern-based artifact handoff (#204) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

CopilotAI review requested due to automatic review settings June 26, 2026 17:51

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:51 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment thread.github/workflows/publish-release.yml Outdated
Comment thread.github/workflows/build-release-task.yml

ptr727and others added 2 commits June 26, 2026 11:07

Merge remote-tracking branch 'origin/develop' into feature/surgical-a…
34e73a0
…rtifact-cleanup-214

ptr727 merged commit 161d8a9 into developJun 26, 2026
8 checks passed

ptr727 deleted the feature/surgical-artifact-cleanup-214 branch June 26, 2026 18:16

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 17:51

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:51 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment thread.github/workflows/publish-release.yml Outdated
Comment thread.github/workflows/build-release-task.yml

ptr727and others added 2 commits June 26, 2026 11:07

Merge remote-tracking branch 'origin/develop' into feature/surgical-a…
34e73a0
…rtifact-cleanup-214

ptr727 merged commit 161d8a9 into developJun 26, 2026
8 checks passed

ptr727 deleted the feature/surgical-artifact-cleanup-214 branch June 26, 2026 18:16

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 17:51

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:51 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment thread.github/workflows/publish-release.yml Outdated
Comment thread.github/workflows/build-release-task.yml

ptr727and others added 2 commits June 26, 2026 11:07

Merge remote-tracking branch 'origin/develop' into feature/surgical-a…
34e73a0
…rtifact-cleanup-214

ptr727 merged commit 161d8a9 into developJun 26, 2026
8 checks passed

ptr727 deleted the feature/surgical-artifact-cleanup-214 branch June 26, 2026 18:16

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 17:51

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:51 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment thread.github/workflows/publish-release.yml Outdated
Comment thread.github/workflows/build-release-task.yml

ptr727and others added 2 commits June 26, 2026 11:07

Merge remote-tracking branch 'origin/develop' into feature/surgical-a…
34e73a0
…rtifact-cleanup-214

ptr727 merged commit 161d8a9 into developJun 26, 2026
8 checks passed

ptr727 deleted the feature/surgical-artifact-cleanup-214 branch June 26, 2026 18:16

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 17:51

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:51 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment thread.github/workflows/publish-release.yml Outdated
Comment thread.github/workflows/build-release-task.yml

ptr727and others added 2 commits June 26, 2026 11:07

Merge remote-tracking branch 'origin/develop' into feature/surgical-a…
34e73a0
…rtifact-cleanup-214

ptr727 merged commit 161d8a9 into developJun 26, 2026
8 checks passed

ptr727 deleted the feature/surgical-artifact-cleanup-214 branch June 26, 2026 18:16

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 17:51

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:51 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment thread.github/workflows/publish-release.yml Outdated
Comment thread.github/workflows/build-release-task.yml

ptr727and others added 2 commits June 26, 2026 11:07

Merge remote-tracking branch 'origin/develop' into feature/surgical-a…
34e73a0
…rtifact-cleanup-214

ptr727 merged commit 161d8a9 into developJun 26, 2026
8 checks passed

ptr727 deleted the feature/surgical-artifact-cleanup-214 branch June 26, 2026 18:16

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 17:51

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:51 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment thread.github/workflows/publish-release.yml Outdated
Comment thread.github/workflows/build-release-task.yml

ptr727and others added 2 commits June 26, 2026 11:07

Merge remote-tracking branch 'origin/develop' into feature/surgical-a…
34e73a0
…rtifact-cleanup-214

ptr727 merged commit 161d8a9 into developJun 26, 2026
8 checks passed

ptr727 deleted the feature/surgical-artifact-cleanup-214 branch June 26, 2026 18:16

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

CopilotAI review requested due to automatic review settings June 26, 2026 17:51

Copilotstarted reviewing on behalf of ptr727 June 26, 2026 17:51 View session

CopilotAI reviewed Jun 26, 2026
View reviewed changes

Comment thread.github/workflows/publish-release.yml Outdated
Comment thread.github/workflows/build-release-task.yml

ptr727and others added 2 commits June 26, 2026 11:07

Merge remote-tracking branch 'origin/develop' into feature/surgical-a…
34e73a0
…rtifact-cleanup-214

ptr727 merged commit 161d8a9 into developJun 26, 2026
8 checks passed

ptr727 deleted the feature/surgical-artifact-cleanup-214 branch June 26, 2026 18:16

ptr727 mentioned this pull request Jul 4, 2026
Release: promote develop to main #225
Merged

Conversation

ptr727 commented Jun 26, 2026

Problem

Fix

Verification

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

ptr727 commented Jun 26, 2026

Problem

Fix

Verification

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

ptr727 commented Jun 26, 2026

Problem

Fix

Verification

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

ptr727 commented Jun 26, 2026

Problem

Fix

Verification

Uh oh!

CopilotAI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!