heavy-duty/stoke
7
1
Fork 1
Code Issues 1 Pull requests Projects Releases 3 Packages Wiki Activity Actions
stoke/.ceremony
History
claude-lead-andresmgsl 125e44afe9
Some checks are pending
ci / test (push) Waiting to run
Details
docs: re-vendor .ceremony/ from ceremony 0.6.3 
#39 moved the two workflow callers to 0.6.3 but left the doctrine mirror at
0.6.1, so BUILDER.md was missing the three clauses that govern signal-then-ready
(ceremony#330, the undraft order, and ceremony#336). Re-vendored all six
manifest files and moved the pin recorded in .ceremony/README.md.
2026-08-30 22:15:44 +00:00
..
AGENTS.md docs: re-vendor .ceremony/ from ceremony 0.6.3 2026-08-30 22:15:44 +00:00
BUILDER.md Vendor ceremony doctrine and scope mapping 2026-08-19 20:56:10 +00:00
LABELS.md Vendor ceremony doctrine and scope mapping 2026-08-19 20:56:10 +00:00
README.md Fix governance roster and mirror claims 2026-08-20 23:23:51 +00:00
RELEASES.md Vendor ceremony doctrine and scope mapping 2026-08-19 20:56:10 +00:00
REVIEWER.md Vendor ceremony doctrine and scope mapping 2026-08-19 20:56:10 +00:00
TRIAGE.md Vendor ceremony doctrine and scope mapping 2026-08-19 20:56:10 +00:00

README.md

.ceremony/ — the vendored doctrine mirror

Never edit these files ad hoc. The six manifest-listed doctrine files are byte-identical copies of heavy-duty/ceremony at 0.6.1, but stoke does not run docs-sync or re-diff the mirror in CI. Change doctrine upstream through its own flow, then re-vendor it here when the pin moves.

The labels doctrine is vendored manually from heavy-duty/ceremony at 0.6.1 because stoke keeps its own tag-driven .forgejo/workflows/release.yml. docs-sync --fix cannot run until or unless a future issue adopts the ceremony release-workflow pin; until then, doctrine updates must re-vendor the pinned manifest manually.