genichin/gitea-agent
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[verified] Separate rework intake from publication counter checks

Browse Source
This commit is contained in:
gitea-spec-agent
2026-10-13 08:27:25 +00:00
parent e1be0dd526
commit 31ac634585
5 changed files with 194 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
harness/agents/impl/skills/gitea-issue-rework/references/readback.md
+7 -2
View File
@@ -69,8 +69,13 @@ automatically detect a mode or choose one to fit observed counters. Both
policy; per-review counters, complete collection pagination, duplicate IDs and
record cardinality remain checked.
`per_review` requires every exact-review comment endpoint. Only the explicit
`per_review_or_pr_count` capability permits endpoint-unavailable 404/405 fallback.
`per_review` requires every exact-review comment endpoint. Only publication
`snapshot`/`verify-live` with an explicit `per_review_or_pr_count` capability
permits endpoint-unavailable 404/405 fallback. Initial `input-gate` instead requires
real inline records and rejects this fallback; its PR-wide counter projections are
recorded as non-blocking `counter_diagnostics`, not used to establish collection
completeness. See [input-gate.md](input-gate.md) for the phase boundary. Publication
counter crosschecks, Source Issue protection and review decision rules are unchanged.
Permission errors, redirects, malformed JSON and conflicting metadata never
trigger fallback. Fallback uses a fresh PR count, the declared review/inline
components and complete review `comments_count` records; disagreement is BLOCK.