Scaled-Tech-Consulting/Gitea-Tools
4
0
Fork 0
Code Issues 110 Pull Requests 12 Actions Packages Projects Releases Wiki Activity

Enforce self-propagating canonical handoffs through final controller closure #626

New Issue
Closed
opened 2026-07-10 11:20:01 -05:00 by jcwalker3 · 4 comments
jcwalker3 commented 2026-07-10 11:20:01 -05:00
Owner
Copy Link
Copy Source

Problem

Current author, reviewer, and merger reports may include a ready-to-paste next prompt, but the workflow does not reliably enforce that each actor:

  1. reads and verifies the live canonical state;
  2. performs only its assigned role;
  3. updates the durable issue and PR state after acting;
  4. posts a complete prompt for the next actor;
  5. continues the handoff chain until the authorized controller verifies completion and records final closure.

The gap was demonstrated by the merger handoff produced after review of PR #625 / Issue #601. The prompt included basic merge instructions but did not require:

  • verification that the inherited approval still applied to the live head;
  • complete post-merge verification;
  • canonical issue-state and thread-ledger updates;
  • controller-boundary handling;
  • durable handling of workflow failures;
  • generation and posting of the next complete handoff;
  • continuation until final controller acceptance and closure.

This means the workflow still depends on a human copying reports into another chat and expanding the next prompt manually.

Desired behavior

Every workflow actor should consume one canonical handoff, perform one authorized workflow role, update Gitea as the durable system of record, and emit the next complete canonical handoff.

The chain should end only when:

  • the authorized controller verifies the outcome;
  • all acceptance criteria are satisfied;
  • required cleanup and reconciliation are complete;
  • canonical final state is posted;
  • the issue is closed through the sanctioned workflow.

Relationship to prior work

This issue does not re-spec the foundational templates already tracked (and largely closed) under:

  • #494 — canonical state handoff ledger
  • #495 — canonical next-action comments
  • #496 — fail-closed canonical comment validation
  • #500 — controller issue-acceptance gate
  • #501 — reject contradictory reviewer handoffs
  • #505 — Canonical Thread Handoff (CTH) protocol
  • #507 — controller handoff + thread state ledger

Those issues define schemas, docs, and partial validators. This issue owns the systemic enforcement gap: self-propagating handoffs across all roles, live-state recovery, mandatory Gitea posting, final-report schema integration that makes the next handoff non-optional, merger → merged-awaiting-controller transition, controller accept/reject continuation, and workflow-failure escalation until durable final closure.

PR #625 / Issue #601 is a concrete example of the gap, not the sole scope.

Scope

The durable solution should cover the author, reviewer, merger, controller, operator, and reconciliation paths where applicable.

It should define and enforce:

1. Canonical handoff contract

Each handoff must include at least:

  • repository;
  • issue number;
  • PR number, when applicable;
  • current workflow state;
  • current head and relevant base or merge SHA;
  • acting role and identity;
  • completed actions;
  • validation evidence;
  • mutation ledger;
  • active blockers;
  • next actor;
  • exact next action;
  • prohibited actions;
  • complete next-session prompt;
  • durable workflow-failure issue references;
  • last-updated timestamp.

2. Live-state recovery

The receiving actor must verify the live Gitea and Git state rather than treating the inherited handoff as authoritative.

The workflow must detect:

  • changed PR head;
  • stale approval;
  • closed or reopened issue;
  • merged PR;
  • stale or foreign lease;
  • missing or dirty worktree;
  • namespace mismatch;
  • stale runtime;
  • changed base;
  • conflicting canonical comments.

3. Role-limited continuation

The receiving actor must perform only the role assigned by the current state.

Examples:

  • author fixes requested changes;
  • reviewer independently reviews the current head;
  • merger verifies approval parity and merges;
  • controller verifies acceptance and closes or requests more work;
  • operator resolves infrastructure blockers;
  • reconciler performs sanctioned cleanup.

4. Mandatory durable state update

A successful actor session must not end with only a chat report.

It must post or update the canonical Gitea state and thread ledger before completion.

5. Mandatory next handoff

Unless the issue is durably complete, every actor must post a complete ready-to-run prompt for the next actor.

The prompt must be stored in Gitea, not only returned in chat output.

6. Controller completion boundary

A merged PR must not automatically be treated as fully accepted unless the configured workflow authorizes that behavior.

The workflow must represent states such as:

  • needs-author
  • needs-review
  • approved-awaiting-merge
  • merged-awaiting-controller
  • blocked
  • complete

The controller must be able to:

  • accept and close;
  • request additional tests;
  • request clearer proof;
  • request feature corrections;
  • reopen or return the issue to an earlier actor;
  • leave the next canonical handoff.

7. Workflow-failure escalation

Any tooling or workflow failure discovered while processing a work item must be captured in durable issue work.

The current work item should contain:

  • failure classification;
  • linked issue;
  • temporary impact;
  • next valid actor;
  • recovery prompt.

The actor should not silently fold an unrelated workflow defect into the active feature issue.

8. Validation before posting

Canonical handoff comments should be schema-validated before Gitea accepts them.

Missing or ambiguous fields should fail closed with actionable feedback.

9. Final-report integration

Author, reviewer, merger, controller, operator, and reconciler final-report schemas should generate or require the canonical next handoff consistently.

The next prompt should not be an optional prose section.

Acceptance criteria

  • A canonical schema exists for cross-role handoffs.

  • Applicable workflow final-report schemas require that handoff.

  • A validator rejects incomplete handoffs.

  • Successful actor workflows post the handoff into Gitea.

  • The receiving actor can recover the task using only:

    • the issue or PR thread;
    • workflow documentation;
    • live repository state.

  • No outside chat history is required.

  • Head changes invalidate stale review or merge handoffs.

  • Merge success transitions to the configured controller state.

  • Controller acceptance or rejection generates the appropriate final or next state.

  • Workflow failures produce a separate durable issue reference.

  • Completed workflows terminate without generating an unnecessary next prompt.

  • Tests cover at least:

    • author to reviewer;
    • reviewer to merger;
    • merger to controller;
    • controller back to author;
    • stale-head rejection;
    • blocked infrastructure path;
    • final successful closure;
    • incomplete handoff rejection;
    • duplicate workflow-failure issue handling.

Non-goals

  • Do not hard-code Issue #601 or PR #625 behavior.
  • Do not place project-specific acceptance criteria into generic workflow prompts.
  • Do not require humans to paste reports through ChatGPT between roles.
  • Do not solve unrelated lease, worktree, or namespace defects inside this issue unless needed for handoff enforcement.
  • Do not bypass existing capability, role, or controller gates.
  • Do not re-open the foundational schema/docs work already closed under #494–#507 unless a regression or missing enforcement wire-up is discovered.

Evidence / example

Use PR #625 / Issue #601 as a concrete example of the gap:

  • author produced a detailed reviewer handoff;
  • reviewer successfully approved the current head;
  • reviewer’s next merger prompt was operationally too narrow;
  • the missing requirements had to be added manually outside Gitea.

Describe this as an example, not as the sole scope.

## Problem Current author, reviewer, and merger reports may include a ready-to-paste next prompt, but the workflow does not reliably enforce that each actor: 1. reads and verifies the live canonical state; 2. performs only its assigned role; 3. updates the durable issue and PR state after acting; 4. posts a complete prompt for the next actor; 5. continues the handoff chain until the authorized controller verifies completion and records final closure. The gap was demonstrated by the merger handoff produced after review of PR #625 / Issue #601. The prompt included basic merge instructions but did not require: * verification that the inherited approval still applied to the live head; * complete post-merge verification; * canonical issue-state and thread-ledger updates; * controller-boundary handling; * durable handling of workflow failures; * generation and posting of the next complete handoff; * continuation until final controller acceptance and closure. This means the workflow still depends on a human copying reports into another chat and expanding the next prompt manually. ## Desired behavior Every workflow actor should consume one canonical handoff, perform one authorized workflow role, update Gitea as the durable system of record, and emit the next complete canonical handoff. The chain should end only when: * the authorized controller verifies the outcome; * all acceptance criteria are satisfied; * required cleanup and reconciliation are complete; * canonical final state is posted; * the issue is closed through the sanctioned workflow. ## Relationship to prior work This issue does **not** re-spec the foundational templates already tracked (and largely closed) under: * #494 — canonical state handoff ledger * #495 — canonical next-action comments * #496 — fail-closed canonical comment validation * #500 — controller issue-acceptance gate * #501 — reject contradictory reviewer handoffs * #505 — Canonical Thread Handoff (CTH) protocol * #507 — controller handoff + thread state ledger Those issues define schemas, docs, and partial validators. **This issue owns the systemic enforcement gap:** self-propagating handoffs across all roles, live-state recovery, mandatory Gitea posting, final-report schema integration that makes the next handoff non-optional, merger → `merged-awaiting-controller` transition, controller accept/reject continuation, and workflow-failure escalation until durable final closure. PR #625 / Issue #601 is a concrete example of the gap, not the sole scope. ## Scope The durable solution should cover the author, reviewer, merger, controller, operator, and reconciliation paths where applicable. It should define and enforce: ### 1. Canonical handoff contract Each handoff must include at least: * repository; * issue number; * PR number, when applicable; * current workflow state; * current head and relevant base or merge SHA; * acting role and identity; * completed actions; * validation evidence; * mutation ledger; * active blockers; * next actor; * exact next action; * prohibited actions; * complete next-session prompt; * durable workflow-failure issue references; * last-updated timestamp. ### 2. Live-state recovery The receiving actor must verify the live Gitea and Git state rather than treating the inherited handoff as authoritative. The workflow must detect: * changed PR head; * stale approval; * closed or reopened issue; * merged PR; * stale or foreign lease; * missing or dirty worktree; * namespace mismatch; * stale runtime; * changed base; * conflicting canonical comments. ### 3. Role-limited continuation The receiving actor must perform only the role assigned by the current state. Examples: * author fixes requested changes; * reviewer independently reviews the current head; * merger verifies approval parity and merges; * controller verifies acceptance and closes or requests more work; * operator resolves infrastructure blockers; * reconciler performs sanctioned cleanup. ### 4. Mandatory durable state update A successful actor session must not end with only a chat report. It must post or update the canonical Gitea state and thread ledger before completion. ### 5. Mandatory next handoff Unless the issue is durably complete, every actor must post a complete ready-to-run prompt for the next actor. The prompt must be stored in Gitea, not only returned in chat output. ### 6. Controller completion boundary A merged PR must not automatically be treated as fully accepted unless the configured workflow authorizes that behavior. The workflow must represent states such as: * `needs-author` * `needs-review` * `approved-awaiting-merge` * `merged-awaiting-controller` * `blocked` * `complete` The controller must be able to: * accept and close; * request additional tests; * request clearer proof; * request feature corrections; * reopen or return the issue to an earlier actor; * leave the next canonical handoff. ### 7. Workflow-failure escalation Any tooling or workflow failure discovered while processing a work item must be captured in durable issue work. The current work item should contain: * failure classification; * linked issue; * temporary impact; * next valid actor; * recovery prompt. The actor should not silently fold an unrelated workflow defect into the active feature issue. ### 8. Validation before posting Canonical handoff comments should be schema-validated before Gitea accepts them. Missing or ambiguous fields should fail closed with actionable feedback. ### 9. Final-report integration Author, reviewer, merger, controller, operator, and reconciler final-report schemas should generate or require the canonical next handoff consistently. The next prompt should not be an optional prose section. ## Acceptance criteria * A canonical schema exists for cross-role handoffs. * Applicable workflow final-report schemas require that handoff. * A validator rejects incomplete handoffs. * Successful actor workflows post the handoff into Gitea. * The receiving actor can recover the task using only: * the issue or PR thread; * workflow documentation; * live repository state. * No outside chat history is required. * Head changes invalidate stale review or merge handoffs. * Merge success transitions to the configured controller state. * Controller acceptance or rejection generates the appropriate final or next state. * Workflow failures produce a separate durable issue reference. * Completed workflows terminate without generating an unnecessary next prompt. * Tests cover at least: * author to reviewer; * reviewer to merger; * merger to controller; * controller back to author; * stale-head rejection; * blocked infrastructure path; * final successful closure; * incomplete handoff rejection; * duplicate workflow-failure issue handling. ## Non-goals * Do not hard-code Issue #601 or PR #625 behavior. * Do not place project-specific acceptance criteria into generic workflow prompts. * Do not require humans to paste reports through ChatGPT between roles. * Do not solve unrelated lease, worktree, or namespace defects inside this issue unless needed for handoff enforcement. * Do not bypass existing capability, role, or controller gates. * Do not re-open the foundational schema/docs work already closed under #494–#507 unless a regression or missing enforcement wire-up is discovered. ## Evidence / example Use PR #625 / Issue #601 as a concrete example of the gap: * author produced a detailed reviewer handoff; * reviewer successfully approved the current head; * reviewer’s next merger prompt was operationally too narrow; * the missing requirements had to be added manually outside Gitea. Describe this as an example, not as the sole scope.
jcwalker3 added the type:guardrailstatus:readyworkflow-hardening labels 2026-07-10 11:20:02 -05:00
jcwalker3 added status:in-progressworkflow-hardening and removed status:readyworkflow-hardening labels 2026-07-20 22:50:09 -05:00
jcwalker3 commented 2026-07-20 22:50:09 -05:00
Author
Owner
Copy Link
Copy Source

Issue claim heartbeat

<!-- gitea-issue-claim-heartbeat:v1 --> **Issue claim heartbeat** - kind: claim - issue: #626 - branch: feat/issue-626-self-propagating-handoffs - phase: claimed - profile: prgs-author - pr: none - blocker: none - next_action: create worktree and begin implementation
jcwalker3 added status:pr-open and removed status:in-progress labels 2026-07-21 02:35:25 -05:00
jcwalker3 commented 2026-07-21 02:39:00 -05:00
Author
Owner
Copy Link
Copy Source

[THREAD STATE LEDGER]

What is true now

  • Issue #626 is open; PR #779 carries its implementation against base master.
  • PR #779 head is ddc9b97d401a3102f4088abc27cbe1be1795f3a0, parented on 1d11cbab0fdc529859bdace2bd01e20da22ff449.
  • Server-side decision state: no review verdict of any kind exists on PR #779. Merge result: merge not performed.
  • Local verdict/state: author implementation is finished and its validation evidence is recorded below; the author holds no review or merge authority.
  • Blocker classification: no blocker.

What changed

  • Server-side mutation ledger:
    • durable issue lock for #626 recovered through canonical dead-session recovery (recovery_mode: unpublished_claim, prior pid 2100 dead, ancestry proven against recorded base 1d11cbab);
    • remote branch feat/issue-626-self-propagating-handoffs created at commit ddc9b97d401a3102f4088abc27cbe1be1795f3a0 through native MCP gitea_commit_files;
    • PR #779 opened against master;
    • issue label set moved to status:pr-open by the PR-creation transition;
    • this comment.
  • Local-only: no working-tree edits were made this fire. The implementation commit b2977a35 already existed in branches/issue-626-self-propagating-handoffs; the published tree 4df467f5746be4f6c86a9d229250b7eefd5354d0 is byte-identical to it.

What is blocked

  • Nothing. Blocker classification: no blocker.
  • Progress now depends only on an independent reviewer acting on PR #779.

Who/what acts next

  • Next actor: reviewer (an identity other than jcwalker3, in the reviewer namespace).
  • Required action: perform an independent native review of PR #779 pinned to head ddc9b97d401a3102f4088abc27cbe1be1795f3a0 and post a verdict.
  • Do not do: do not let the author review or merge this work; do not re-implement anything already carried by ddc9b97d; do not rewrite, force-push, or rebase the branch; do not treat the twelve pre-existing master test failures listed below as regressions from this branch.

Canonical Issue State

STATE: pr-open-awaiting-independent-review
WHO_IS_NEXT: reviewer
NEXT_ACTION: Perform an independent native reviewer-namespace review of PR #779 pinned to head ddc9b97d40 and post a verdict.
NEXT_PROMPT: Act as the independent reviewer for Scaled-Tech-Consulting/Gitea-Tools on remote prgs. Review PR #779, which closes issue #626 and adds the self-propagating canonical handoff protocol. Bind a reviewer namespace and profile whose identity is not jcwalker3, verify runtime parity and control-checkout cleanliness, then pin the live PR head, which was ddc9b97d40 against base master at 1d11cbab0f when this handoff was written, and re-derive that head from live state before deciding. Examine the new module self_propagating_handoff.py, its wiring into final_report_validator.py as rule shared.self_propagating_handoff across nine task kinds, the schema document skills/llm-project-workflow/schemas/self-propagating-handoff.md, and the five final-report schema updates. Check each acceptance criterion of issue #626, including the nine enforcement areas, the fourteen live-state detection kinds, the four controller closure proofs, the workflow-failure escalation fields with duplicate handling, and terminal closure that emits no further prompt. Re-run pytest tests/test_self_propagating_handoff.py and the full suite from a reviewer worktree under branches/, and compare any failures against a clean checkout at base 1d11cbab before attributing them to this branch. Post a native verdict through the reviewer namespace, then leave the next canonical handoff on issue #626. Everything you need is in this issue thread, PR #779, the workflow documentation, and live repository state.
WHAT_HAPPENED: An earlier author session of this loop implemented issue #626 and committed it locally as b2977a35, then exited before publishing. This fire proved ownership through canonical dead-session recovery rather than re-implementing, re-ran the validation evidence, published the branch through native MCP, and opened PR #779.
WHY: Issue #626 owns the systemic enforcement gap left by #494 through #507: nothing forced the handoff chain itself. The change adds the canonical cross-role handoff contract, a fail-closed validator, live-state recovery, role-limited continuation, mandatory durable posting into Gitea, the post-merge controller boundary, controller accept and reject continuation, and workflow-failure escalation into separate durable issues.
ISSUE: 626
HEAD_SHA: ddc9b97d40
REVIEW_STATUS: No verdict exists on PR #779; the PR awaits its first independent review.
MERGE_READY: Not evaluated by this session. Merge authority belongs to the merger role and is out of author scope.
RELATED_PRS: #779
BLOCKERS: none
VALIDATION: pytest tests/test_self_propagating_handoff.py returned 53 passed. The full suite on this branch returned 4009 passed, 12 failed, 6 skipped, 493 subtests passed in 672s. All twelve failures reproduce identically on a clean checkout at the exact base SHA 1d11cbab0f in worktree branches/baseline-master-issue-626, so they are pre-existing on master and are not caused by this branch: six in tests/test_commit_payloads.py, two in tests/test_issue_702_review_findings_f1_f6.py, and one each in tests/test_mcp_server.py TestPreflightVerification, tests/test_post_merge_moot_lease.py TestAcquireToolRefusesMergedPR, tests/test_reconciler_supersession_close.py TestReconcilerSupersessionMcpTool, and tests/test_webui_ci_gate.py TestCiRunnerScript. git diff --check over the branch range reported no whitespace defects.
LAST_UPDATED_BY: jcwalker3 / prgs-author (LLM_LOCK_ID claude-author-loop-prod-v1, LLM_EXECUTION_ID claude-author-loop-prod-v1-20260721T071305Z-pid94743-0bfff856)

[THREAD STATE LEDGER] ### What is true now - Issue #626 is open; PR #779 carries its implementation against base `master`. - PR #779 head is `ddc9b97d401a3102f4088abc27cbe1be1795f3a0`, parented on `1d11cbab0fdc529859bdace2bd01e20da22ff449`. - Server-side decision state: no review verdict of any kind exists on PR #779. Merge result: merge not performed. - Local verdict/state: author implementation is finished and its validation evidence is recorded below; the author holds no review or merge authority. - Blocker classification: no blocker. ### What changed - Server-side mutation ledger: - durable issue lock for #626 recovered through canonical dead-session recovery (`recovery_mode: unpublished_claim`, prior pid 2100 dead, ancestry proven against recorded base `1d11cbab`); - remote branch `feat/issue-626-self-propagating-handoffs` created at commit `ddc9b97d401a3102f4088abc27cbe1be1795f3a0` through native MCP `gitea_commit_files`; - PR #779 opened against `master`; - issue label set moved to `status:pr-open` by the PR-creation transition; - this comment. - Local-only: no working-tree edits were made this fire. The implementation commit `b2977a35` already existed in `branches/issue-626-self-propagating-handoffs`; the published tree `4df467f5746be4f6c86a9d229250b7eefd5354d0` is byte-identical to it. ### What is blocked - Nothing. Blocker classification: no blocker. - Progress now depends only on an independent reviewer acting on PR #779. ### Who/what acts next - Next actor: reviewer (an identity other than `jcwalker3`, in the reviewer namespace). - Required action: perform an independent native review of PR #779 pinned to head `ddc9b97d401a3102f4088abc27cbe1be1795f3a0` and post a verdict. - Do not do: do not let the author review or merge this work; do not re-implement anything already carried by `ddc9b97d`; do not rewrite, force-push, or rebase the branch; do not treat the twelve pre-existing master test failures listed below as regressions from this branch. ## Canonical Issue State STATE: pr-open-awaiting-independent-review WHO_IS_NEXT: reviewer NEXT_ACTION: Perform an independent native reviewer-namespace review of PR #779 pinned to head ddc9b97d401a3102f4088abc27cbe1be1795f3a0 and post a verdict. NEXT_PROMPT: Act as the independent reviewer for Scaled-Tech-Consulting/Gitea-Tools on remote prgs. Review PR #779, which closes issue #626 and adds the self-propagating canonical handoff protocol. Bind a reviewer namespace and profile whose identity is not jcwalker3, verify runtime parity and control-checkout cleanliness, then pin the live PR head, which was ddc9b97d401a3102f4088abc27cbe1be1795f3a0 against base master at 1d11cbab0fdc529859bdace2bd01e20da22ff449 when this handoff was written, and re-derive that head from live state before deciding. Examine the new module self_propagating_handoff.py, its wiring into final_report_validator.py as rule shared.self_propagating_handoff across nine task kinds, the schema document skills/llm-project-workflow/schemas/self-propagating-handoff.md, and the five final-report schema updates. Check each acceptance criterion of issue #626, including the nine enforcement areas, the fourteen live-state detection kinds, the four controller closure proofs, the workflow-failure escalation fields with duplicate handling, and terminal closure that emits no further prompt. Re-run pytest tests/test_self_propagating_handoff.py and the full suite from a reviewer worktree under branches/, and compare any failures against a clean checkout at base 1d11cbab before attributing them to this branch. Post a native verdict through the reviewer namespace, then leave the next canonical handoff on issue #626. Everything you need is in this issue thread, PR #779, the workflow documentation, and live repository state. WHAT_HAPPENED: An earlier author session of this loop implemented issue #626 and committed it locally as b2977a35, then exited before publishing. This fire proved ownership through canonical dead-session recovery rather than re-implementing, re-ran the validation evidence, published the branch through native MCP, and opened PR #779. WHY: Issue #626 owns the systemic enforcement gap left by #494 through #507: nothing forced the handoff chain itself. The change adds the canonical cross-role handoff contract, a fail-closed validator, live-state recovery, role-limited continuation, mandatory durable posting into Gitea, the post-merge controller boundary, controller accept and reject continuation, and workflow-failure escalation into separate durable issues. ISSUE: 626 HEAD_SHA: ddc9b97d401a3102f4088abc27cbe1be1795f3a0 REVIEW_STATUS: No verdict exists on PR #779; the PR awaits its first independent review. MERGE_READY: Not evaluated by this session. Merge authority belongs to the merger role and is out of author scope. RELATED_PRS: #779 BLOCKERS: none VALIDATION: pytest tests/test_self_propagating_handoff.py returned 53 passed. The full suite on this branch returned 4009 passed, 12 failed, 6 skipped, 493 subtests passed in 672s. All twelve failures reproduce identically on a clean checkout at the exact base SHA 1d11cbab0fdc529859bdace2bd01e20da22ff449 in worktree branches/baseline-master-issue-626, so they are pre-existing on master and are not caused by this branch: six in tests/test_commit_payloads.py, two in tests/test_issue_702_review_findings_f1_f6.py, and one each in tests/test_mcp_server.py TestPreflightVerification, tests/test_post_merge_moot_lease.py TestAcquireToolRefusesMergedPR, tests/test_reconciler_supersession_close.py TestReconcilerSupersessionMcpTool, and tests/test_webui_ci_gate.py TestCiRunnerScript. git diff --check over the branch range reported no whitespace defects. LAST_UPDATED_BY: jcwalker3 / prgs-author (LLM_LOCK_ID claude-author-loop-prod-v1, LLM_EXECUTION_ID claude-author-loop-prod-v1-20260721T071305Z-pid94743-0bfff856)
sysadmin commented 2026-07-21 12:54:54 -05:00
Owner
Copy Link
Copy Source

Canonical Handoff

REPOSITORY: Scaled-Tech-Consulting/Gitea-Tools
ISSUE: 626
PR: 779
WORKFLOW_STATE: merged-awaiting-controller
HEAD_SHA: ddc9b97d401a3102f4088abc27cbe1be1795f3a0
BASE_BRANCH: master
BASE_OR_MERGE_SHA: df3167488c5451f802549b40463ad59cbaad6109
ACTING_ROLE: merger
ACTING_IDENTITY: sysadmin (prgs-merger)
COMPLETED_ACTIONS: verified OS user jasonwalker non-root, verified namespace health, verified master parity, verified live head is ddc9b97d401a3102f4088abc27cbe1be1795f3a0 and approval 491 is current-head-valid, acquired merger lease 52026-ab9774c6eb54, merged PR #779 via gitea_merge_pr
VALIDATION_EVIDENCE: gitea_assess_pr_sync_status recommended_next_action is merge_now, gitea_merge_pr returned success: true and performed: true, local git fetch confirmed merge commit df3167488c5451f802549b40463ad59cbaad6109
MUTATION_LEDGER: merger lease 52026-ab9774c6eb54 acquired; PR #779 merged on remote prgs; decision lock for prgs-reviewer cleared
BLOCKERS: none
NEXT_ACTOR: controller
NEXT_ACTION: Verify acceptance criteria, verify cleanup, verify final state and close Issue #626 through sanctioned controller workflow
PROHIBITED_ACTIONS: merger-session controller closure; bypassing controller verification; re-merging or mutating the closed PR
NEXT_PROMPT: Act as controller for Scaled-Tech-Consulting/Gitea-Tools on remote prgs. Inspect Issue #626 and PR #779, which has been merged as df3167488c5451f802549b40463ad59cbaad6109. Bind a controller namespace, verify parity and namespace health, confirm live PR is merged and Issue #626 is awaiting final verification. Verify all acceptance criteria are satisfied, verify that cleanup has run, and perform the final controller closure of Issue #626 through the sanctioned workflow.
WORKFLOW_FAILURE_ISSUES: none
LAST_UPDATED: 2026-07-21T17:55:00Z

Canonical Issue State

STATE: merged-awaiting-controller
WHO_IS_NEXT: controller
NEXT_ACTION: Verify acceptance criteria, verify cleanup, verify final state and close Issue #626 through sanctioned controller workflow
NEXT_PROMPT:

Act as controller for Scaled-Tech-Consulting/Gitea-Tools on remote prgs. Inspect Issue #626 and PR #779, which has been merged as df3167488c5451f802549b40463ad59cbaad6109. Bind a controller namespace, verify parity and namespace health, confirm live PR is merged and Issue #626 is awaiting final verification. Verify all acceptance criteria are satisfied, verify that cleanup has run, and perform the final controller closure of Issue #626 through the sanctioned workflow.

WHAT_HAPPENED: PR #779 merged under merger profile prgs-merger at head ddc9b97d40 with merge commit df3167488c.
WHY: Approved review 491 was verified valid and non-stale at current head; namespace health and parity verified; lease acquired.
RELATED_PRS: #779
BLOCKERS: none
VALIDATION: PR successfully merged; local git fetch verified commit df3167488c is present and is master branch head.
LAST_UPDATED_BY: sysadmin / prgs-merger (LLM_LOCK_ID gemini-merger-loop)

<!-- sph:v1 --> ## Canonical Handoff ```text REPOSITORY: Scaled-Tech-Consulting/Gitea-Tools ISSUE: 626 PR: 779 WORKFLOW_STATE: merged-awaiting-controller HEAD_SHA: ddc9b97d401a3102f4088abc27cbe1be1795f3a0 BASE_BRANCH: master BASE_OR_MERGE_SHA: df3167488c5451f802549b40463ad59cbaad6109 ACTING_ROLE: merger ACTING_IDENTITY: sysadmin (prgs-merger) COMPLETED_ACTIONS: verified OS user jasonwalker non-root, verified namespace health, verified master parity, verified live head is ddc9b97d401a3102f4088abc27cbe1be1795f3a0 and approval 491 is current-head-valid, acquired merger lease 52026-ab9774c6eb54, merged PR #779 via gitea_merge_pr VALIDATION_EVIDENCE: gitea_assess_pr_sync_status recommended_next_action is merge_now, gitea_merge_pr returned success: true and performed: true, local git fetch confirmed merge commit df3167488c5451f802549b40463ad59cbaad6109 MUTATION_LEDGER: merger lease 52026-ab9774c6eb54 acquired; PR #779 merged on remote prgs; decision lock for prgs-reviewer cleared BLOCKERS: none NEXT_ACTOR: controller NEXT_ACTION: Verify acceptance criteria, verify cleanup, verify final state and close Issue #626 through sanctioned controller workflow PROHIBITED_ACTIONS: merger-session controller closure; bypassing controller verification; re-merging or mutating the closed PR NEXT_PROMPT: Act as controller for Scaled-Tech-Consulting/Gitea-Tools on remote prgs. Inspect Issue #626 and PR #779, which has been merged as df3167488c5451f802549b40463ad59cbaad6109. Bind a controller namespace, verify parity and namespace health, confirm live PR is merged and Issue #626 is awaiting final verification. Verify all acceptance criteria are satisfied, verify that cleanup has run, and perform the final controller closure of Issue #626 through the sanctioned workflow. WORKFLOW_FAILURE_ISSUES: none LAST_UPDATED: 2026-07-21T17:55:00Z ``` ## Canonical Issue State STATE: merged-awaiting-controller WHO_IS_NEXT: controller NEXT_ACTION: Verify acceptance criteria, verify cleanup, verify final state and close Issue #626 through sanctioned controller workflow NEXT_PROMPT: ```text Act as controller for Scaled-Tech-Consulting/Gitea-Tools on remote prgs. Inspect Issue #626 and PR #779, which has been merged as df3167488c5451f802549b40463ad59cbaad6109. Bind a controller namespace, verify parity and namespace health, confirm live PR is merged and Issue #626 is awaiting final verification. Verify all acceptance criteria are satisfied, verify that cleanup has run, and perform the final controller closure of Issue #626 through the sanctioned workflow. ``` WHAT_HAPPENED: PR #779 merged under merger profile prgs-merger at head ddc9b97d401a3102f4088abc27cbe1be1795f3a0 with merge commit df3167488c5451f802549b40463ad59cbaad6109. WHY: Approved review 491 was verified valid and non-stale at current head; namespace health and parity verified; lease acquired. RELATED_PRS: #779 BLOCKERS: none VALIDATION: PR successfully merged; local git fetch verified commit df3167488c5451f802549b40463ad59cbaad6109 is present and is master branch head. LAST_UPDATED_BY: sysadmin / prgs-merger (LLM_LOCK_ID gemini-merger-loop)
sysadmin commented 2026-07-21 13:26:01 -05:00
Owner
Copy Link
Copy Source

Canonical Handoff

REPOSITORY: Scaled-Tech-Consulting/Gitea-Tools
ISSUE: 626
PR: 779
WORKFLOW_STATE: complete
HEAD_SHA: ddc9b97d401a3102f4088abc27cbe1be1795f3a0
BASE_BRANCH: master
BASE_OR_MERGE_SHA: df3167488c5451f802549b40463ad59cbaad6109
ACTING_ROLE: controller
ACTING_IDENTITY: sysadmin (prgs-reconciler)
COMPLETED_ACTIONS: verified OS user jasonwalker uid 502 non-root, verified Gitea identity sysadmin under profile prgs-reconciler with identity_match true, verified live namespace health for gitea-reconciler with probe_source client_namespace, verified server/master parity at df3167488c5451f802549b40463ad59cbaad6109, read Issue #626 and PR #779 and review 491 and merger handoff comment 13589, verified PR #779 is closed and merged at head ddc9b97d401a3102f4088abc27cbe1be1795f3a0 with merge commit df3167488c5451f802549b40463ad59cbaad6109, verified every acceptance criterion against the merged repository state, performed authorized post-merge cleanup, recorded this final controller state
VALIDATION_EVIDENCE: merge commit df3167488c5451f802549b40463ad59cbaad6109 has parents 1d11cbab0fdc529859bdace2bd01e20da22ff449 and ddc9b97d401a3102f4088abc27cbe1be1795f3a0 and tree 4df467f5746be4f6c86a9d229250b7eefd5354d0 identical to the reviewed head tree; local master HEAD equals the merge commit with a clean control checkout; self_propagating_handoff.py and tests/test_self_propagating_handoff.py and skills/llm-project-workflow/schemas/self-propagating-handoff.md are present in the merged tree; rule shared.self_propagating_handoff is registered for all nine task kinds review_pr, merge_pr, reconcile_already_landed, author_issue, work_issue, issue_filing, inventory, issue_selection, controller_close; the module exposes assess_self_propagating_handoff, assess_thread_recoverability, assess_handoff_live_state with fourteen detection kinds, assess_role_continuation, assess_durable_state_update, assess_merge_completion_transition, assess_controller_decision with four closure proof fields, assess_workflow_failure_escalation with five required fields, assess_final_report_self_propagating_handoff; five final-report schemas plus SKILL.md carry the handoff requirement; pytest tests/test_self_propagating_handoff.py at the merged tree returned 53 passed
MUTATION_LEDGER: remote branch feat/issue-626-self-propagating-handoffs deleted through gitea_cleanup_merged_pr_branch with post-delete readback verified_absent true; this controller closure comment posted to Issue #626
BLOCKERS: none
NEXT_ACTOR: none
NEXT_ACTION: none
PROHIBITED_ACTIONS: reopening Issue #626 without new evidence; re-merging or mutating the closed PR #779; emitting a further actor prompt from this terminated chain; folding unrelated workflow defects into this issue
NEXT_PROMPT: none
WORKFLOW_FAILURE_ISSUES: none
LAST_UPDATED: 2026-07-21T18:30:00Z

[THREAD STATE LEDGER]

What is true now

  • Issue #626 is closed. PR #779 is closed with merge commit df3167488c5451f802549b40463ad59cbaad6109.
  • PR #779 head is ddc9b97d401a3102f4088abc27cbe1be1795f3a0; the merge commit's tree 4df467f5746be4f6c86a9d229250b7eefd5354d0 is byte-identical to that head's tree, so nothing drifted between review and landing.
  • Server-side decision state: review 491 by sysadmin / prgs-reviewer is an APPROVED review posted to Gitea at head ddc9b97d401a3102f4088abc27cbe1be1795f3a0, with dismissed: false, stale: false, quarantined: false, approval_at_current_head: true. Merge result: merge performed at 2026-07-21T12:53:50-05:00 by profile prgs-merger.
  • Local verdict/state: the controller re-derived every acceptance criterion from the merged repository state at local master df3167488c5451f802549b40463ad59cbaad6109 (clean control checkout, runtime in parity) and re-ran the focused suite at the merged tree with the result 53 passed.
  • Blocker classification: no blocker.

What changed

  • Server-side mutation ledger:
    • remote branch feat/issue-626-self-propagating-handoffs deleted through native gitea_cleanup_merged_pr_branch, post-delete readback verified_absent: true, branch_present: false;
    • this controller closure comment.
      Local-only changes: four worktrees belonging to this work item were removed after a captured pre-removal snapshot proved each one clean — branches/review-pr-779-ddc9b97 (detached ddc9b97), branches/review-418 (detached ddc9b97), branches/baseline-master-issue-626 (detached 1d11cbab) and branches/issue-626-self-propagating-handoffs; the local branch feat/issue-626-self-propagating-handoffs at b2977a35bffefbe6a58a977d3fe16aac27833a18 was deleted only after proving its tree equals the landed tree 4df467f5746be4f6c86a9d229250b7eefd5354d0. Cleanup integrity reconciled 4 initial / 4 removed / 0 preserved-missing / 0 orphaned, with integrity_passed: true. Every other worktree was left untouched.

What is blocked

  • Nothing for this work item. Blocker classification: no blocker.
  • Reported, not changed: Issue #626 still carries the label status:pr-open. The prgs-reconciler profile holds no issue-label permission, so the stale label is reported here instead of being edited through an unauthorized path.

Who/what acts next

  • Next actor: user. The workflow chain for Issue #626 terminates at this controller acceptance; no automated actor inherits it.
  • Required action: no further workflow action is authorized on Issue #626; any new work must be filed as its own issue.
  • Do not do: do not reopen Issue #626 without new evidence; do not re-merge or otherwise mutate the closed PR #779; do not generate a further actor prompt from this terminated chain; do not treat the pre-existing master test failures recorded on this thread as regressions from this work.

Canonical Issue State

STATE: accepted
WHO_IS_NEXT: user
NEXT_ACTION:
The workflow chain for Issue #626 is terminated at controller acceptance; no further workflow action is authorized on this issue.
NEXT_PROMPT:

No next-actor prompt is issued. Issue #626 is accepted and closed, PR #779 landed as df3167488c5451f802549b40463ad59cbaad6109, its source branch is deleted, and the local worktrees for this work item are removed. Any additional work must be filed as a new issue with its own canonical handoff chain.

WHAT_HAPPENED: The controller verified the merge, the acceptance criteria, the durable evidence chain and the required cleanup for Issue #626, then recorded final acceptance. Issue #626 was closed by the sanctioned merge of PR #779, whose body declares Closes #626.
WHY: Every acceptance criterion of Issue #626 is satisfied in the merged tree, the reviewed head landed without drift, the required handoffs are durable on this thread, and the sanctioned post-merge cleanup completed with proof.
ISSUE: 626
HEAD_SHA: ddc9b97d40
RELATED_PRS: #779
BLOCKERS: none
VALIDATION: merge parents 1d11cbab0fdc529859bdace2bd01e20da22ff449 and ddc9b97d401a3102f4088abc27cbe1be1795f3a0; merge tree 4df467f5746be4f6c86a9d229250b7eefd5354d0 equals the reviewed head tree; pytest tests/test_self_propagating_handoff.py at the merged tree returned 53 passed; rule shared.self_propagating_handoff registered for nine task kinds; schema document and five final-report schemas present in the merged tree.
NATIVE_REVIEW_PROOF: transport=native_mcp; namespace=gitea-reviewer; profile=prgs-reviewer; identity=sysadmin; tool=gitea_submit_pr_review; review_id=491; head=ddc9b97d401a3102f4088abc27cbe1be1795f3a0
LAST_UPDATED_BY: sysadmin / prgs-reconciler (controller closure) / 2026-07-21

Controller Issue Acceptance

STATE: accepted
WHO_IS_NEXT: user
NEXT_ACTION:
Record no further workflow action for Issue #626; the chain terminates at this controller acceptance.
NEXT_PROMPT:

No next-actor prompt is issued for Issue #626. The chain terminates at controller acceptance; file any additional work as a new issue with its own canonical handoff chain.

ISSUE: #626
MERGED_PR: #779
MERGE_COMMIT: df3167488c
ACCEPTANCE_CRITERIA_CHECKED:

  • A canonical schema exists for cross-role handoffs — skills/llm-project-workflow/schemas/self-propagating-handoff.md in the merged tree.
  • Applicable workflow final-report schemas require that handoff — create-issue, pr-queue-cleanup, reconcile-landed, review-merge and work-issue final-report schemas plus skills/llm-project-workflow/SKILL.md.
  • A validator rejects incomplete handoffs — assess_self_propagating_handoff fails closed on missing or placeholder fields; wired as rule shared.self_propagating_handoff for review_pr, merge_pr, reconcile_already_landed, author_issue, work_issue, issue_filing, inventory, issue_selection and controller_close.
  • Successful actor workflows post the handoff into Gitea — assess_durable_state_update rejects a chat-only report; comments 13568, 13589 and this comment are the durable chain on this thread.
  • The receiving actor can recover from the thread, workflow documentation and live state alone — assess_thread_recoverability rejects prompts that lean on outside chat history; this controller session recovered the task from this thread with no outside chat context.
  • Head changes invalidate stale review or merge handoffs — assess_handoff_live_state covers all fourteen detection kinds including changed_pr_head and stale_approval.
  • Merge success transitions to the configured controller state — assess_merge_completion_transition moves a merged PR to merged-awaiting-controller, which is exactly the state comment 13589 recorded.
  • Controller acceptance or rejection generates the appropriate final or next state — assess_controller_decision honors accept only with all four closure proofs and routes request_tests, request_proof, request_corrections, reopen and return_to_actor.
  • Workflow failures produce a separate durable issue reference — assess_workflow_failure_escalation requires classification, linked_issue, temporary_impact, next_valid_actor and recovery_prompt per distinct defect and reuses an existing issue for a known signature.
  • Completed workflows terminate without generating an unnecessary next prompt — terminal complete must carry no NEXT_ACTION and no NEXT_PROMPT, as the canonical handoff at the top of this comment demonstrates.
  • Tests cover author to reviewer, reviewer to merger, merger to controller, controller back to author, stale-head rejection, blocked infrastructure path, final successful closure, incomplete handoff rejection and duplicate workflow-failure issue handling — tests/test_self_propagating_handoff.py, 53 passed at the merged tree.
    VALIDATION_REVIEWED: Reviewer 491 evidence (focused 53 passed; full suite 4010 passed / 11 failed / 6 skipped, with the eleven failures reproduced identically on a clean checkout at base 1d11cbab0fdc529859bdace2bd01e20da22ff449, so they are pre-existing on master and are not caused by this work) plus the controller's own re-run of pytest tests/test_self_propagating_handoff.py at the merged tree, which returned 53 passed.
    CONTROLLER_DECISION: accepted
    WHY: All acceptance criteria are satisfied in the merged tree, the landed tree is identical to the independently reviewed head, the durable handoff chain is present on this thread, and the sanctioned post-merge cleanup completed with proof.
    MISSING_WORK: none
    FOLLOW_UP_ISSUES: none
    BLOCKERS: none
    CLEANUP_PERFORMED: remote branch feat/issue-626-self-propagating-handoffs deleted and verified absent; four #626/#779 worktrees removed; local branch deleted after tree-parity proof; no active workflow lease remained on Issue #626 or PR #779.
    LAST_UPDATED_BY: sysadmin / prgs-reconciler (controller closure) / 2026-07-21
<!-- sph:v1 --> ## Canonical Handoff ```text REPOSITORY: Scaled-Tech-Consulting/Gitea-Tools ISSUE: 626 PR: 779 WORKFLOW_STATE: complete HEAD_SHA: ddc9b97d401a3102f4088abc27cbe1be1795f3a0 BASE_BRANCH: master BASE_OR_MERGE_SHA: df3167488c5451f802549b40463ad59cbaad6109 ACTING_ROLE: controller ACTING_IDENTITY: sysadmin (prgs-reconciler) COMPLETED_ACTIONS: verified OS user jasonwalker uid 502 non-root, verified Gitea identity sysadmin under profile prgs-reconciler with identity_match true, verified live namespace health for gitea-reconciler with probe_source client_namespace, verified server/master parity at df3167488c5451f802549b40463ad59cbaad6109, read Issue #626 and PR #779 and review 491 and merger handoff comment 13589, verified PR #779 is closed and merged at head ddc9b97d401a3102f4088abc27cbe1be1795f3a0 with merge commit df3167488c5451f802549b40463ad59cbaad6109, verified every acceptance criterion against the merged repository state, performed authorized post-merge cleanup, recorded this final controller state VALIDATION_EVIDENCE: merge commit df3167488c5451f802549b40463ad59cbaad6109 has parents 1d11cbab0fdc529859bdace2bd01e20da22ff449 and ddc9b97d401a3102f4088abc27cbe1be1795f3a0 and tree 4df467f5746be4f6c86a9d229250b7eefd5354d0 identical to the reviewed head tree; local master HEAD equals the merge commit with a clean control checkout; self_propagating_handoff.py and tests/test_self_propagating_handoff.py and skills/llm-project-workflow/schemas/self-propagating-handoff.md are present in the merged tree; rule shared.self_propagating_handoff is registered for all nine task kinds review_pr, merge_pr, reconcile_already_landed, author_issue, work_issue, issue_filing, inventory, issue_selection, controller_close; the module exposes assess_self_propagating_handoff, assess_thread_recoverability, assess_handoff_live_state with fourteen detection kinds, assess_role_continuation, assess_durable_state_update, assess_merge_completion_transition, assess_controller_decision with four closure proof fields, assess_workflow_failure_escalation with five required fields, assess_final_report_self_propagating_handoff; five final-report schemas plus SKILL.md carry the handoff requirement; pytest tests/test_self_propagating_handoff.py at the merged tree returned 53 passed MUTATION_LEDGER: remote branch feat/issue-626-self-propagating-handoffs deleted through gitea_cleanup_merged_pr_branch with post-delete readback verified_absent true; this controller closure comment posted to Issue #626 BLOCKERS: none NEXT_ACTOR: none NEXT_ACTION: none PROHIBITED_ACTIONS: reopening Issue #626 without new evidence; re-merging or mutating the closed PR #779; emitting a further actor prompt from this terminated chain; folding unrelated workflow defects into this issue NEXT_PROMPT: none WORKFLOW_FAILURE_ISSUES: none LAST_UPDATED: 2026-07-21T18:30:00Z ``` [THREAD STATE LEDGER] ### What is true now - Issue #626 is closed. PR #779 is closed with merge commit `df3167488c5451f802549b40463ad59cbaad6109`. - PR #779 head is `ddc9b97d401a3102f4088abc27cbe1be1795f3a0`; the merge commit's tree `4df467f5746be4f6c86a9d229250b7eefd5354d0` is byte-identical to that head's tree, so nothing drifted between review and landing. - Server-side decision state: review 491 by `sysadmin` / `prgs-reviewer` is an APPROVED review posted to Gitea at head `ddc9b97d401a3102f4088abc27cbe1be1795f3a0`, with `dismissed: false`, `stale: false`, `quarantined: false`, `approval_at_current_head: true`. Merge result: merge performed at 2026-07-21T12:53:50-05:00 by profile `prgs-merger`. - Local verdict/state: the controller re-derived every acceptance criterion from the merged repository state at local master `df3167488c5451f802549b40463ad59cbaad6109` (clean control checkout, runtime in parity) and re-ran the focused suite at the merged tree with the result 53 passed. - Blocker classification: no blocker. ### What changed - Server-side mutation ledger: - remote branch `feat/issue-626-self-propagating-handoffs` deleted through native `gitea_cleanup_merged_pr_branch`, post-delete readback `verified_absent: true`, `branch_present: false`; - this controller closure comment. Local-only changes: four worktrees belonging to this work item were removed after a captured pre-removal snapshot proved each one clean — `branches/review-pr-779-ddc9b97` (detached ddc9b97), `branches/review-418` (detached ddc9b97), `branches/baseline-master-issue-626` (detached 1d11cbab) and `branches/issue-626-self-propagating-handoffs`; the local branch `feat/issue-626-self-propagating-handoffs` at `b2977a35bffefbe6a58a977d3fe16aac27833a18` was deleted only after proving its tree equals the landed tree `4df467f5746be4f6c86a9d229250b7eefd5354d0`. Cleanup integrity reconciled 4 initial / 4 removed / 0 preserved-missing / 0 orphaned, with `integrity_passed: true`. Every other worktree was left untouched. ### What is blocked - Nothing for this work item. Blocker classification: no blocker. - Reported, not changed: Issue #626 still carries the label `status:pr-open`. The `prgs-reconciler` profile holds no issue-label permission, so the stale label is reported here instead of being edited through an unauthorized path. ### Who/what acts next - Next actor: user. The workflow chain for Issue #626 terminates at this controller acceptance; no automated actor inherits it. - Required action: no further workflow action is authorized on Issue #626; any new work must be filed as its own issue. - Do not do: do not reopen Issue #626 without new evidence; do not re-merge or otherwise mutate the closed PR #779; do not generate a further actor prompt from this terminated chain; do not treat the pre-existing master test failures recorded on this thread as regressions from this work. ## Canonical Issue State STATE: accepted WHO_IS_NEXT: user NEXT_ACTION: The workflow chain for Issue #626 is terminated at controller acceptance; no further workflow action is authorized on this issue. NEXT_PROMPT: ```text No next-actor prompt is issued. Issue #626 is accepted and closed, PR #779 landed as df3167488c5451f802549b40463ad59cbaad6109, its source branch is deleted, and the local worktrees for this work item are removed. Any additional work must be filed as a new issue with its own canonical handoff chain. ``` WHAT_HAPPENED: The controller verified the merge, the acceptance criteria, the durable evidence chain and the required cleanup for Issue #626, then recorded final acceptance. Issue #626 was closed by the sanctioned merge of PR #779, whose body declares `Closes #626`. WHY: Every acceptance criterion of Issue #626 is satisfied in the merged tree, the reviewed head landed without drift, the required handoffs are durable on this thread, and the sanctioned post-merge cleanup completed with proof. ISSUE: 626 HEAD_SHA: ddc9b97d401a3102f4088abc27cbe1be1795f3a0 RELATED_PRS: #779 BLOCKERS: none VALIDATION: merge parents `1d11cbab0fdc529859bdace2bd01e20da22ff449` and `ddc9b97d401a3102f4088abc27cbe1be1795f3a0`; merge tree `4df467f5746be4f6c86a9d229250b7eefd5354d0` equals the reviewed head tree; `pytest tests/test_self_propagating_handoff.py` at the merged tree returned 53 passed; rule `shared.self_propagating_handoff` registered for nine task kinds; schema document and five final-report schemas present in the merged tree. NATIVE_REVIEW_PROOF: transport=native_mcp; namespace=gitea-reviewer; profile=prgs-reviewer; identity=sysadmin; tool=gitea_submit_pr_review; review_id=491; head=ddc9b97d401a3102f4088abc27cbe1be1795f3a0 LAST_UPDATED_BY: sysadmin / prgs-reconciler (controller closure) / 2026-07-21 ## Controller Issue Acceptance STATE: accepted WHO_IS_NEXT: user NEXT_ACTION: Record no further workflow action for Issue #626; the chain terminates at this controller acceptance. NEXT_PROMPT: ```text No next-actor prompt is issued for Issue #626. The chain terminates at controller acceptance; file any additional work as a new issue with its own canonical handoff chain. ``` ISSUE: #626 MERGED_PR: #779 MERGE_COMMIT: df3167488c5451f802549b40463ad59cbaad6109 ACCEPTANCE_CRITERIA_CHECKED: - [x] A canonical schema exists for cross-role handoffs — `skills/llm-project-workflow/schemas/self-propagating-handoff.md` in the merged tree. - [x] Applicable workflow final-report schemas require that handoff — create-issue, pr-queue-cleanup, reconcile-landed, review-merge and work-issue final-report schemas plus `skills/llm-project-workflow/SKILL.md`. - [x] A validator rejects incomplete handoffs — `assess_self_propagating_handoff` fails closed on missing or placeholder fields; wired as rule `shared.self_propagating_handoff` for review_pr, merge_pr, reconcile_already_landed, author_issue, work_issue, issue_filing, inventory, issue_selection and controller_close. - [x] Successful actor workflows post the handoff into Gitea — `assess_durable_state_update` rejects a chat-only report; comments 13568, 13589 and this comment are the durable chain on this thread. - [x] The receiving actor can recover from the thread, workflow documentation and live state alone — `assess_thread_recoverability` rejects prompts that lean on outside chat history; this controller session recovered the task from this thread with no outside chat context. - [x] Head changes invalidate stale review or merge handoffs — `assess_handoff_live_state` covers all fourteen detection kinds including `changed_pr_head` and `stale_approval`. - [x] Merge success transitions to the configured controller state — `assess_merge_completion_transition` moves a merged PR to `merged-awaiting-controller`, which is exactly the state comment 13589 recorded. - [x] Controller acceptance or rejection generates the appropriate final or next state — `assess_controller_decision` honors accept only with all four closure proofs and routes request_tests, request_proof, request_corrections, reopen and return_to_actor. - [x] Workflow failures produce a separate durable issue reference — `assess_workflow_failure_escalation` requires classification, linked_issue, temporary_impact, next_valid_actor and recovery_prompt per distinct defect and reuses an existing issue for a known signature. - [x] Completed workflows terminate without generating an unnecessary next prompt — terminal `complete` must carry no NEXT_ACTION and no NEXT_PROMPT, as the canonical handoff at the top of this comment demonstrates. - [x] Tests cover author to reviewer, reviewer to merger, merger to controller, controller back to author, stale-head rejection, blocked infrastructure path, final successful closure, incomplete handoff rejection and duplicate workflow-failure issue handling — `tests/test_self_propagating_handoff.py`, 53 passed at the merged tree. VALIDATION_REVIEWED: Reviewer 491 evidence (focused 53 passed; full suite 4010 passed / 11 failed / 6 skipped, with the eleven failures reproduced identically on a clean checkout at base `1d11cbab0fdc529859bdace2bd01e20da22ff449`, so they are pre-existing on master and are not caused by this work) plus the controller's own re-run of `pytest tests/test_self_propagating_handoff.py` at the merged tree, which returned 53 passed. CONTROLLER_DECISION: accepted WHY: All acceptance criteria are satisfied in the merged tree, the landed tree is identical to the independently reviewed head, the durable handoff chain is present on this thread, and the sanctioned post-merge cleanup completed with proof. MISSING_WORK: none FOLLOW_UP_ISSUES: none BLOCKERS: none CLEANUP_PERFORMED: remote branch `feat/issue-626-self-propagating-handoffs` deleted and verified absent; four #626/#779 worktrees removed; local branch deleted after tree-parity proof; no active workflow lease remained on Issue #626 or PR #779. LAST_UPDATED_BY: sysadmin / prgs-reconciler (controller closure) / 2026-07-21
jcwalker3 removed the status:pr-open label 2026-07-21 13:33:00 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels type:guardrail workflow-hardening
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 jwalker (Regular User Account) superadmin (Admin Account) sysadmin (Regular User Account)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#626