chore(snapshots): refresh anomaly parser release

[ArchonVII]

Summary

Refresh the canonical githubWorkflows snapshot manifest to released github-workflows@v1 commit f34893a3b67e5c17e59ca1413e92077833fdc571, which includes the anomaly metadata parser compatibility repair from ArchonVII/github-workflows#111. The 18 caller snapshots remain byte-identical; only the provider pin, capture time, generated ecosystem map, and release note change.

Verification

• Verified all provider snapshots against their recorded commits after the scoped refresh.

  command: npm run snapshots:verify -- --only githubWorkflows
  location: local
  result: Exit 0; githubWorkflows 18 files, repoTemplate 131 files, and orgDefaults 1 file matched their pins.
  timestamp: 2026-07-09T23:11:00-05:00
  

• Verified the generated ecosystem map is current.

  command: node scripts/update-ecosystem-overview.mjs --check
  location: local
  result: Exit 0; generated block reported up to date.
  timestamp: 2026-07-09T23:11:01-05:00
  

• Proved root self-apply remains idempotent after the provider pin update.

  command: npm run agent:self-apply -- --check (executed twice consecutively)
  location: local
  result: Exit 0 on both runs; all six tasks reported already-done with no writes.
  timestamp: 2026-07-09T23:11:03-05:00
  

• Executed the complete integrator test suite.

  command: npm test
  location: local
  result: Exit 0; 674 tests, 672 passed, 0 failed, 2 platform skips.
  timestamp: 2026-07-09T23:12:20-05:00
  

Verification Notes

Before regeneration, node scripts/update-ecosystem-overview.mjs --check failed with ecosystem-overview.md generated block is STALE. The scoped refresh first verified the existing e6ef54c snapshot (18 files) and then captured f34893a; no caller snapshot content changed. npm install was used because this dependency-free repository intentionally has no package lock.

Docs / Changelog

Updated the generated provider pin in docs/ecosystem-overview.md and added .changelog/unreleased/346-refresh-anomaly-parser-snapshot.md. The retired per-PR repo-update-log ledger was not revived.

Plan/status artifacts: not applicable because none were created or used by this lane.

Linked Issue

Closes #346

Risks

• Risk level: low; snapshot contents are byte-identical and only the released provider pin advances.
• Rollback: revert commit d7efbc0 and restore the previous e6ef54c manifest pin if release provenance is incorrect.
• Follow-ups: none; consumers use @v1 directly and their caller permission blocks were propagated in the parent issue.