-
Gitea user account used by Claude Code with Gitea MCP to manage repositories: read/write issues and PRs, comment on changes, and perform merge/review actions with appropriate permissions.
- Joined on
2026-06-20
Fixed by #129, squash-merged to main as 598a7c3.
Description rewritten to ADR-0020 shape — trigger + one capability + boundary, with the catalogue opener and the composition/implementatio…
Fixed by #129, squash-merged to main as 598a7c3.
LOGIC.md and UI.md moved to references/logic.md and references/ui.md (git tracked both as renames, R099). The skill root is now…
Fixed by #129, squash-merged to main as 598a7c3.
validate-provenance.sh now treats an explicit source_keys: [] as a declaration that the file is house-authored with no external source…
Fixed by #129, squash-merged to main as 598a7c3.
Verified against the merged tree on the exact clause from this issue's report:
Not creating or editing `.pre-commit-config.yaml` ->…
Fixed by #129, squash-merged to main as 598a7c3.
The boundary-clause check (and the trigger-quality checks that presuppose model invocation) now skip when frontmatter carries `disable-model-in…
Fixed by #129, squash-merged to main as 598a7c3.
Resolved via fix option 2 — a multi-target arrow clause is rejected with a SUGGESTION telling the author to split, rather than extending…
Second full review + fixes (10 commits, 971e148..0427422)
Nine parallel reviewers over disjoint scopes, then eight implementation agents plus a cleanup pass. 25 of 29 findings are fixed in…
Review + fixes (7 commits, 5b80f30..971e148)
Full review across seven parallel reviewers, then fixed what it found. Verification of the retrofit itself first, since that is the bulk of the…
Research doc: slug and path conventions do not match what validate-provenance expects
Two more items for this issue, found while adding the regression tests for 27a7669 (commit 5b80f30).
The same blind spot exists one function over
484357a / 27a7669 taught `parse_contri…
All three findings fixed on refactor/adr0020-skill-retrofit (not yet pushed — the PR body will carry the close)
1. Description: 386 → 224 characters
Rewritten to trigger + one…
Still open — but a material change on refactor/adr0020-skill-retrofit strengthens the case
The defect this issue describes is unfixed: validate-provenance.sh still cannot tell a true…
Still open, still correct — and there is a second independent cause this issue does not record
Nothing on refactor/adr0020-skill-retrofit fixes this. assets/vale/.vale.ini still…
Fixed on refactor/adr0020-skill-retrofit (not yet pushed — the PR body will carry the close)
Implemented exactly as the suggested fix specifies. The branches now differ:
if…
Fixed on refactor/adr0020-skill-retrofit (not yet pushed — the PR body will carry the close)
All four steps of the stated scope are done.
LOGIC.md→references/logic.md,UI.md→…
Fixed on refactor/adr0020-skill-retrofit (not yet pushed — the PR body will carry the close)
Implemented as the first of the two suggested shapes: source_keys: [] is now a declaration,…
Fixed on refactor/adr0020-skill-retrofit (not yet pushed — the PR body will carry the close), including the severity escalation in comment 2
The regex
[^.;] became a named `CLAUSE_BOD…