Maintenance Walkthrough - 2026-04-05

Maintenance Walkthrough - 2026-04-05

• Closed issues #455 and #456 with maintainer comments explaining what a follow-up submission must include before reopening:
  • concrete repo diff or implementation PR
  • source-only contributor branch
  • Quality Bar checklist and maintainer validations from .github/MAINTENANCE.md
• Reviewed open issues #455 and #456 during the maintainer sweep; neither had a matching accepted PR and both remain open pending a source-quality contributor submission.
• Triaged PR #454 as superseded by #457 because #457 rebuilds the Windows validation/test fixes on top of current main and includes the follow-up batch activation fix requested in review.
• Verified PR #457 locally on the contributor head with:
  • npm run validate
  • npm run validate:references
  • npm run check:warning-budget
  • npm run check:readme-credits -- --base origin/main --head HEAD
  • npm run test
  • npm run app:test:coverage
  • npm run app:build
• Cleaned PR #457 back to the repository's source-only PR contract by dropping maintainer-owned generated registry artifacts before merge review.
• Normalized the PR metadata so the required Quality Bar Checklist is present before re-triggering the fork-based GitHub Actions checks.

Maintenance Walkthrough - 2026-03-30

• Merged PR #418 on GitHub with squash after approving the pending fork workflow run and waiting for pr-policy, source-validation, and artifact-preview to finish green.
• Repaired PR #423's stale metadata state by updating the PR body to include the required Quality Bar Checklist, then closed and reopened it to force fresh pull_request runs before squash merging it on GitHub.
• Synced local main after the PR merge batch so release preparation starts from the canonical remote state.
• Resolved issue #421 by ensuring the README.md Community Contributed Skills section includes SoulPass on main.
• Resolved issue #419 by tightening the github-issue-creator frontmatter description and "When to Use" guidance for better discoverability.
• Prepared the v9.3.0 release notes in CHANGELOG.md and recorded the maintainer actions here before running the release flow.

Maintenance Walkthrough - 2026-03-29

• Re-triaged the full 2026-03-15 security finding set against current main and wrote a fresh current-head report in docs/maintainers/security-findings-triage-2026-03-29-refresh.md.
• Added a matching machine-readable export at docs/maintainers/security-findings-triage-2026-03-29-refresh.csv so the refreshed statuses are available in both markdown and CSV form.
• Kept the old 2026-03-15 markdown/CSV as historical baseline input, preserved the smaller 2026-03-29 addendum as a transition note, and pointed both docs at the new refresh as the current source of truth.
• The refreshed triage currently lands at:
  • 0 findings still present and exploitable
  • 0 findings still present but low practical risk
  • 26 obsolete/not repr