Add milestone MIL-006 with five tasks: a scoped publish-wiki workflow with
an opt-in rule, piloted in one other repository. Schedule it in PP-001.
The milestone is Proposed; no code starts before it is accepted.
Add review record RC-015, remove JSON from the credential failures of UC
candidate 2 and the answered MIL-001 items from Open Issues, accept PP-001
and update TM-001.
ADR-0002: an artifact approved by S01 counts as approved for the other
named reviewers, with the stand-in recorded. ADR-0003: the wiki is published
with a separate TOKEN_FOR_GITEA_WIKI, dot-named titles work. Add review
records RC-013 and RC-014 and update TM-001.
English pages are generated and have no suffix; translations are named
<Page>.da and <Page>.ms, written by hand in wiki/, reviewed and checked for
staleness through a source hash. Add the ADR type to the registry.
Add milestone MIL-005 with seven tasks, schedule it in PP-001, add the wiki
to the Business Case scope and record the wiki languages in the registry.
The milestone is Proposed; no wiki work starts before it is accepted.
Adopt the SQA/QC framework as a submodule and plan the project before any
further code: Business Case, Stakeholder Analysis (S01-S05), Project Plan with
use case candidates and prioritisation, and milestones MIL-001..MIL-004
(24 tasks, synced to Gitea as milestones 18-21 and issues #1-#24).
README now separates implemented from planned capabilities, has an English
sequence diagram and points at the scoped workflow. The workflow file moves
out of the repository root and out of .gitea/workflows/; the scoped copy is
unchanged in behaviour here and still contains the known `exit 0` syntax
error, which MIL-001 fixes.
Refs #1
Refs #2
Refs #3
Refs #6
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Tirsvad
