CI.md Release policy's v1.2.3 example contradicts the fleet's bare-tag workflow triggers

standards/CI.md §Release policy illustrates a release tag as v1.2.3. The fleet's release workflows trigger on bare tags only:

on:
  push:
    tags: ['[0-9]+.[0-9]+.[0-9]+']

A v-prefixed tag does not match that pattern, so it publishes having silently skipped every gate the workflows enforce.

This is not hypothetical

liberusoftware/module-analytics-core carries a tag v1.0.4. It matched no workflow trigger, so install.yml and compatibility.yml never ran for that release. Filed separately against that repository.

The failure mode is the bad kind: nothing goes red. The tag exists, the release exists, and the absence of a workflow run is only visible if someone goes looking for it.

Ask

Either change §Release policy's example to a bare 1.2.3, or change the fleet's trigger patterns to accept both forms. The two documents currently disagree, and the disagreement is silent rather than loud.

Recorded downstream as ADR 0005.

Found while auditing ecommerce-laravel against the standards.

Start in standards/CI.md at §Release policy and compare its v1.2.3 example with the bare-tag trigger pattern shown in the issue. Check the linked ADR 0005 for the intended convention; done means the standard and fleet workflow expectations no longer contradict and the release-tag example matches the enforced gates.