---
name: gitea-issue-rework
description: Gitea PR 검토 지적을 계약에 맞춰 재작업하고 검증한다.
version: 0.3.0
author: genichin, Hermes Agent
license: MIT
platforms: [linux]
metadata:
  hermes:
    tags: [gitea, implementation, rework, review, pull-request]
    related_skills: [gitea-issue-implementation]
---

# Gitea Issue Rework

기존 PR의 검토 finding을 승인 계약에 맞춰 재작업하고 exact-head handoff를 한다. Main owns interpretation, approval, credentials, Git/Gitea mutation, integration and delivery; helpers neither grant authority nor prove end-to-end completion. Follow [Impl operation architecture](../../ARCHITECTURE.md); detailed preserved workflow and gates are in [workflow reference](references/workflow.md).

## When to use

A REQUEST_CHANGES/actionable finding on an existing implementation PR; do not use for initial delivery. Never infer unresolved decisions or authorize merge, force-push, Issue changes, release, or deployment.

## Ordered lifecycle

1. **Snapshot과 finding 판정.** Current Issue/PR/review identity, contract digest, reviewed/current head, complete collections와 immutable snapshot을 읽는다. Input gate·delegation/source-binding·runtime adoption을 통과하고 blocked/ambiguous면 중단한다.
2. **Admission·계획.** Broker/cache/worktree/evidence admission, test inventory binding, finding/acceptance matrix, exact allowlist와 baseline을 고정한다. 기존 state를 복구 목적으로 reset하지 않는다.
3. **Test-first 재작업.** 유효 finding만 승인 계약에 따라 고치고 evidence gap은 주장 범위에 맞는 증거로 보완한다. Existing behavior/security gates 약화 금지.
4. **검증·검토·commit.** Focused/full/runtime/browser tests, exact-source evidence, diff/inventory checks와 independent review 실행. Drift 확인 후 exact stage·commit·strict verification.
5. **별도 delivery operations.** Push, PR-body update, canonical PR-top-level comment create/reuse는 각각 승인·preflight·단일 mutation·fresh readback·operation-specific verification을 가진다. Main-owned integration paths only; helpers are not sandbox/authority or end-to-end certificates.
6. **종료·handoff.** 불확실한 acknowledgement는 read-only reconcile; 자동 재시도 금지. Resource/lease 정리, verified receipt 및 후속 reviewer 필요를 보고한다.

## Shared mandatory gates

- Apply test inventory source-binding before check-tests; inventory PASS does not prove test existence, collection, execution, or semantic preservation.
- Before accepting delegated evidence run `harness/lib/delegation_evidence.py` under its canonical contract and independently verify actual artifacts. At each consumer call `require_adoption`; declare `mode=none` or exact `mode=delegated`, never rely on missing declarations or stale PASS receipts. This is not a sandbox.
- Preserve canonical input gates, complete pagination, identity/source binding, cache-mode restrictions, broker leases, worktree admission, exact-source evidence and cleanup. Read the canonical repository-cache and Gitea access operations each run.
- Operation helpers are stage integrations, not authority grants, trusted-adapter substitutes, or completion certificates. The main-owned trusted adapter performs preflight, one mutation and authoritative readback; see the operation integration contract before invoking it.

## References

- [Full workflow, preserved prose and detailed gates](references/workflow.md)
- [Main impl architecture](../../ARCHITECTURE.md)

## Operation integration

Before delivery, read [operation API contract](../../OPERATIONS.md). Use the coordinator-backed entrypoints; a legacy stage receipt is not end-to-end authority.

## Required workflow contract

Required reference: [workflow](references/workflow.md). 행동 전에 `read_file`로 이 참조 전체를 읽어야 한다. 이 요약은 승인·lease·검증·delivery gate를 대체하지 않는다.