tmk241/ink-releases
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test(release): strengthen repository verification

Browse Source
This commit is contained in:
tmk241
2026-08-17 07:54:05 +02:00
parent 6f3969f071
commit 1ee3b97f3b
5 changed files with 73 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+8 -6
View File
@@ -4,10 +4,9 @@
## Authority
- Read `REQUIREMENTS.md` before durable changes.
- `REQUIREMENTS.md` is authoritative; generated artifacts and private source repositories are evidence.
- Update requirements before changing durable installer, publication, integrity, or platform behavior.
- Keep strict Redgate proof current. `req:` is traceability; accepted local `test` edges are proof.
- `SPEC.md` is the sole current-state authority; generated artifacts and private source repositories are evidence, not parallel canon.
- Read applicable records and update `SPEC.md` before changing durable installer, publication, integrity, or platform behavior.
- Keep strict Redgate proof current. `req:` is traceability; only accepted local `test` edges satisfy coverage. Exceptions expose debt and do not make strict checks pass.
## Boundaries
@@ -27,7 +26,10 @@ Work is tracked in Gitea Issues for `tmk241/ink-releases`. Do not mirror issues
bash -n install.sh
uv run test/installer_e2e.py
bash test/repository_e2e.sh
awk '/^## / { component=$2; next } /^[0-9][0-9][0-9]\t/ { print component "/" $0 }' REQUIREMENTS.md | redgate lint -
redgate list
redgate refs
redgate lint
redgate check
```
Final reports must include `REQUIREMENT IMPACT: IDs` or `REQUIREMENT IMPACT: none`.
Final reports must name updated record IDs or exactly `SPECIFICATION IMPACT: none - <specific reason>`.