Issue #986 was closed automatically when PR #996 merged (squash 73e84b8f), but its acceptance criterion AC6 — that hyperpolymath/standards itself calls the ci-pipeline.yml reusable workflow it publishes — was NOT delivered in that PR and now has no tracking issue. The owner previously ruled this should be a separate follow-up PR rather than being bundled into #986. This issue restores the tracking.
Note the general principle: a repo that publishes a reusable pipeline but does not consume it has no protection against silently regressing that pipeline for every downstream consumer.
Cross-reference: #986, #996.
Acceptance criteria
🤖 Generated with Claude Code
https://claude.ai/code/session_01Ji1bq3TypfycfUPAR7hSxR
Issue #986 was closed automatically when PR #996 merged (squash
73e84b8f), but its acceptance criterion AC6 — thathyperpolymath/standardsitself calls theci-pipeline.ymlreusable workflow it publishes — was NOT delivered in that PR and now has no tracking issue. The owner previously ruled this should be a separate follow-up PR rather than being bundled into #986. This issue restores the tracking.Note the general principle: a repo that publishes a reusable pipeline but does not consume it has no protection against silently regressing that pipeline for every downstream consumer.
Cross-reference: #986, #996.
Acceptance criteria
hyperpolymath/standardshas auses:step referencing this repo's ownci-pipeline.yml.main.🤖 Generated with Claude Code
https://claude.ai/code/session_01Ji1bq3TypfycfUPAR7hSxR