feat: coordinate ordinary Forgejo programs in pull and push modes (#106) #112

Closed
kilo wants to merge 0 commits from issue-106-forgejo-ordinary-execution into develop
Member

Refs #106. Forgejo-first ordinary Program execution; the current canonical issue body contains active acceptance criteria and constraints.

Current HEAD efbe76abe4c27ee0c81e9b373d3f0715a30d32bc; base/merge-base b1c9ffca16f06596e5c3afdca3b9893cf7422d8d. The entire accumulated diff is the review subject.

The candidate contains trusted-local shared pull and managed-push SDK handlers, Forgejo discovery and synchronization, bounded review and verification, durable recovery and versioned SQLite compatibility. Existing source-boundary and offline/live limitations apply. Exact public source pins and license references are in docs/architecture/reuse.md.

Review history and validation receipts remain preserved in issue comments and the excluded delivery ledger. Current approval and integrated acceptance are not claimed.

Refs #106. Forgejo-first ordinary Program execution; the current canonical issue body contains active acceptance criteria and constraints. Current HEAD `efbe76abe4c27ee0c81e9b373d3f0715a30d32bc`; base/merge-base `b1c9ffca16f06596e5c3afdca3b9893cf7422d8d`. The entire accumulated diff is the review subject. The candidate contains trusted-local shared pull and managed-push SDK handlers, Forgejo discovery and synchronization, bounded review and verification, durable recovery and versioned SQLite compatibility. Existing source-boundary and offline/live limitations apply. Exact public source pins and license references are in `docs/architecture/reuse.md`. Review history and validation receipts remain preserved in issue comments and the excluded delivery ledger. Current approval and integrated acceptance are not claimed.
feat: coordinate ordinary Forgejo programs in pull and push modes (#106)
Some checks failed
ci / check (pull_request) Failing after 6m37s
6e92db71ea
fix: recover exact ordinary review and compose DAG inputs (#106)
Some checks failed
ci / check (pull_request) Failing after 6m58s
4a3fd22b9a
fix: retain original ordinary evidence and Forgejo comment receipts (#106)
Some checks failed
ci / check (pull_request) Failing after 6m47s
c6418cc1a6
fix: recover original settled command evidence after interruption (#106)
Some checks failed
ci / check (pull_request) Failing after 6m50s
8f03e98687
fix: revoke completed publication and honor work authority (#106)
Some checks failed
ci / check (pull_request) Failing after 15m1s
c6bb7028d1
fix: refuse unresolved baseline and bound CI execution (#106)
All checks were successful
ci / check (pull_request) Successful in 36m30s
60ecc0b474
fix: preserve scope and publication topic recovery (#106)
All checks were successful
ci / check (pull_request) Successful in 38m58s
34bb0e48e2
fix: carry substantive review findings into remediation (#106)
All checks were successful
ci / check (pull_request) Successful in 41m7s
efbe76abe4
Author
Member

STOP_REVISE — Not Approved, Do Not Merge

The tenth and final independent whole-PR review (ses_e6d557ff7ffeDNxUYbDuinFq22) returned COMMENT with two P2 findings for HEAD efbe76abe4c27ee0c81e9b373d3f0715a30d32bc and base b1c9ffca16f06596e5c3afdca3b9893cf7422d8d. Independent make check and package-check passed, as did exact-head CI #3403, but no independent approval exists.

  1. A historical PREPARED claim can trigger unfinished workspace materialization after expiry or budget revocation, before the current-authority check.
  2. Cumulative base-relative patches still falsely conflict for a diamond in which one branch advances an ancestor-modified line and the other merely inherits it.

See the full disposition and source-access distinction in issue #106 comment20092. The review budget is permanently 10/10 consumed; no review11, reset, self-approval or merge. Preserve this open unmerged PR, its branch, all commits, review history and negative evidence. Any revised delivery needs an explicit owner decision; an open PR is not restart authority.

## STOP_REVISE — Not Approved, Do Not Merge The tenth and final independent whole-PR review (`ses_e6d557ff7ffeDNxUYbDuinFq22`) returned **COMMENT with two P2 findings** for HEAD `efbe76abe4c27ee0c81e9b373d3f0715a30d32bc` and base `b1c9ffca16f06596e5c3afdca3b9893cf7422d8d`. Independent `make check` and package-check passed, as did exact-head CI #3403, but no independent approval exists. 1. A historical PREPARED claim can trigger unfinished workspace materialization after expiry or budget revocation, before the current-authority check. 2. Cumulative base-relative patches still falsely conflict for a diamond in which one branch advances an ancestor-modified line and the other merely inherits it. See the full disposition and source-access distinction in [issue #106 comment20092](https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/106#issuecomment-20092). The review budget is permanently **10/10 consumed**; no review11, reset, self-approval or merge. Preserve this open unmerged PR, its branch, all commits, review history and negative evidence. Any revised delivery needs an explicit owner decision; an open PR is not restart authority.
Author
Member

Superseded Unmerged: Explicit Owner-Authorized Recovery

Direct owner decision 2026-10-31T20:33:18Z authorizes ONE distinct, bounded recovery for #106, identity kernel106-final-authority-dag-20261031T203318Z, restricted to the two substantive review10 defects and directly necessary regressions. This is not review11, a reset or permission to weaken full-issue acceptance.

This PR remains the permanent STOP_REVISE 10/10 receipt at exact HEAD efbe76abe4c27ee0c81e9b373d3f0715a30d32bc, base b1c9ffca16f06596e5c3afdca3b9893cf7422d8d, with all original commits, branch and native review results preserved. It will be closed UNMERGED AS SUPERSEDED; the unapproved head will never be merged or reviewed an eleventh time.

A normal recovery branch will retain this exact ancestry and add actual authority-before-materialization and provenance-correct diamond composition fixes, validated red/green and through all local gates before a fresh complete independent review. The new explicitly authorized recovery has a separate maximum 4/4 review budget; its branch/PR number alone is not authority. Replacement PR will be linked after creation. #106 remains open pending separately verified acceptance. No worktree, clone, parallel writer, architecture change, live effect, release or deployment.

## Superseded Unmerged: Explicit Owner-Authorized Recovery Direct owner decision 2026-10-31T20:33:18Z authorizes ONE distinct, bounded recovery for #106, identity `kernel106-final-authority-dag-20261031T203318Z`, restricted to the two substantive review10 defects and directly necessary regressions. This is not review11, a reset or permission to weaken full-issue acceptance. This PR remains the permanent **STOP_REVISE 10/10** receipt at exact HEAD `efbe76abe4c27ee0c81e9b373d3f0715a30d32bc`, base `b1c9ffca16f06596e5c3afdca3b9893cf7422d8d`, with all original commits, branch and native review results preserved. It will be closed **UNMERGED AS SUPERSEDED**; the unapproved head will never be merged or reviewed an eleventh time. A normal recovery branch will retain this exact ancestry and add actual authority-before-materialization and provenance-correct diamond composition fixes, validated red/green and through all local gates before a fresh complete independent review. The new explicitly authorized recovery has a separate maximum **4/4** review budget; its branch/PR number alone is not authority. Replacement PR will be linked after creation. #106 remains open pending separately verified acceptance. No worktree, clone, parallel writer, architecture change, live effect, release or deployment.
kilo closed this pull request 2026-10-31 20:34:36 +00:00
Author
Member

Owner-authorized materially revised replacement is PR #113, HEAD d3d22d19f9588d2556eb7db3fe3252d386f3590e, base b1c9ffca16f06596e5c3afdca3b9893cf7422d8d. It retains original HEAD efbe76ab... as an ancestor and adds one normal commit addressing the two named defects. Original PR112 remains CLOSED/UNMERGED/STOP_REVISE, permanently 10/10; its branch, commits and review evidence remain intact. Replacement recovery is separately owner-authorized and limited to 4 fresh complete reviews, not original review11. No approval or merge claimed.

Owner-authorized materially revised replacement is [PR #113](https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/113), HEAD `d3d22d19f9588d2556eb7db3fe3252d386f3590e`, base `b1c9ffca16f06596e5c3afdca3b9893cf7422d8d`. It retains original HEAD `efbe76ab...` as an ancestor and adds one normal commit addressing the two named defects. Original PR112 remains **CLOSED/UNMERGED/STOP_REVISE, permanently 10/10**; its branch, commits and review evidence remain intact. Replacement recovery is separately owner-authorized and limited to 4 fresh complete reviews, not original review11. No approval or merge claimed.
All checks were successful
ci / check (pull_request) Successful in 41m7s

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Creatidy/creatidy-kernel!112
No description provided.