Skip to content

Make GitHub review publication durable - #504

Closed
morgaesis wants to merge 67 commits into
mainfrom
codex/publication-controller-integration
Closed

Make GitHub review publication durable#504
morgaesis wants to merge 67 commits into
mainfrom
codex/publication-controller-integration

Conversation

@morgaesis

Copy link
Copy Markdown
Contributor

GitHub review publication needs to converge after retries, stale deliveries, and worker lease loss without repeating or losing forge mutations. This introduces a durable controller that stages immutable plans, executes one operation at a time, and derives receipts and gate outcomes from durable evidence; images whose CLI lacks the exact plan capability retain the controller dark while the existing publication path remains active.

The same release preserves protected deep links through authentication, keeps sessions stable across transient membership failures, reconciles finding state after thread activity, exposes repository access and dismissal authority accurately, grounds time-sensitive reviews in current UTC, and renders comparison operators in inline code without HTML entities.

@morgaesis

Copy link
Copy Markdown
ContributorAuthor

@postil review

2 similar comments
@morgaesis

Copy link
Copy Markdown
ContributorAuthor

@postil review

@morgaesis

Copy link
Copy Markdown
ContributorAuthor

@postil review

@morgaesis

Copy link
Copy Markdown
ContributorAuthor

The live approval-authorization slice is merged through PR #550, with actor verification kept read-only against application access state. The remaining branch combines stale schema, queue, and publication semantics that conflict with current main, so I am closing the aggregate rather than merging it.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@morgaesis