6 Commits

Include renames

Author	SHA1	Message	Date
Tirsvad	ec0f6e2cf8	Resolve pending commit links in BC-001, PP-001 and MIL-001 version history ... Task: MIL-001#1	2026-10-10 07:58:02 +08:00
Tirsvad	0c06789a27	Skip metadata sync successfully when no GitHub mirror exists ... Not every Gitea repository has a GitHub push mirror. Zero GitHub mirrors now ends the run successfully without reading the GitHub secret; several mirrors still fail. Tests, guides, README, BC-001, PP-001 and MIL-001 are updated to match. Task: MIL-001#1 Task: MIL-001#5	2026-10-10 07:57:58 +08:00
TirsvadandClaude Sonnet 5.5	2228c49f29	Resolve pending commit link in MIL-001 version history ... Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-10-03 20:46:02 +08:00
TirsvadandClaude Sonnet 5.5	cbb9688ed4	Stabilise the metadata sync workflow and add offline validation ... Restructure the script embedded in the scoped sync workflow into testable functions, fix the invalid `exit 0` (now a successful run with a visible warning when Gitea returns an invalid push mirror list) and report errors as `ERROR: <message>` with exit code 1. Zero, several or malformed GitHub mirrors still fail. Add pytest-based offline tests (workflow YAML, embedded Python, credential and mirror parsing, sync flow against a fake API) that run in a virtual environment, and a validation workflow that runs them on pull requests and pushes to main. Remove the manual tests/test_.ps1 probe and the duplicate src/ copy of the workflow. Update the README and record the decisions for tasks 1 and 3 in MIL-001. Task: MIL-001#1 Task: MIL-001#2 Task: MIL-001#3 Task: MIL-001#4 Task: MIL-001#5 Task: MIL-001#6 Refs #1 Refs #2 Refs #3 Refs #4 Refs #5 Refs #6 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-10-03 20:45:57 +08:00
TirsvadandClaude Sonnet 5.5	72d2671978	Resolve pending commit links in document version histories ... Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-10-03 20:28:49 +08:00
TirsvadandClaude Sonnet 5.5	4de5438a88	Add project plan, milestones and SQA framework; document actual capabilities ... 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>	2026-10-03 20:28:44 +08:00