TirsvadandClaude Sonnet 5.5
4de5438a88
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>
8 lines
403 B
Bash
8 lines
403 B
Bash
# Copy to .env and fill in real values. .env is gitignored - never commit it.
|
|
|
|
# Gitea personal access token (Settings -> Applications -> Generate New Token),
|
|
# scoped to issues only if your Gitea version supports scoped tokens.
|
|
# Used by framework/scripts/sync-project.sh --apply against a Gitea remote.
|
|
# NOT a deploy key - deploy keys authenticate git-over-SSH only, not the API.
|
|
GITEA_TOKEN=
|