Files

3.9 KiB

name, description, version, author, license, platforms, metadata
name description version author license platforms metadata
gitea-issue-implementation 승인된 Gitea Issue를 구현·검증하고 Gitea PR로 전달한다. 0.5.0 genichin, Hermes Agent MIT
linux
hermes
tags related_skills
gitea
implementation
worktree
testing
pull-request
gitea-issue-rework

Gitea Issue Implementation

승인된 Discovery와 pinned revision으로 구현·검증하고 authoritative readback이 된 PR까지 전달한다. 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; detailed preserved workflow and gates are in workflow reference.

When to use

Exact repository and Issue implementation requests only; post-review changes go to gitea-issue-rework. Never infer unresolved decisions or authorize merge, force-push, Issue changes, release, or deployment.

Ordered lifecycle

  1. 승인과 대상 고정. Exact owner/repository/Issue, authenticated identity, immutable Issue snapshot, approved Discovery, pinned full SHA와 acceptance matrix를 고정한다. 미해결 질문·충돌·drift이면 write 전 중단한다.
  2. Admission과 baseline. 공통 source-binding/delegation adoption, broker Issue lease, cache/repository lease, canonical worktree admission 및 inventory/guard gates를 실행한다. Baseline test와 capability spike를 실제 기록한다.
  3. 계약·구현. Canonical docs README/TEMPLATE와 Contract Preservation Inventory를 적용한다. Test-first로 최소 변경하고 security, scope, credential 및 existing state 보존 gates를 유지한다.
  4. 검증·독립 검토. 실행 가능한 formatter/lint/type/build/test/runtime/browser gates, exact-source evidence, diff review와 bounded independent review를 통과시킨다. Timeout/환경 오류는 RED가 아니다.
  5. Commit·delivery. Drift 재확인, exact allowlist stage, non-amended commit 및 strict clean exact-source verification 후 승인된 main-owned delivery integration 경로로 push/PR 수행. Readback으로 확인하고 uncertain write는 read-only reconciliation만 한다.
  6. 종료·보고. Temporary resources와 leases를 정리·검증하고 authoritative final PR head/status를 보고한다. Merge/Issue/release/deployment는 금지.

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

Operation integration

Before delivery, read operation API contract. Use the coordinator-backed entrypoints; a legacy stage receipt is not end-to-end authority.

Required workflow contract

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