Repository navigation
Port work queues, agent continuity and administration to main - #3
Merged
Merged
Conversation
dkropachev
force-pushed
the
sync/local-development
branch
from
October 26, 2026 05:26
b91a6dd to
71c5da1
Compare
Export current implementation, UI, tests and specifications on top of published main while retaining hosted CI and release delivery. Keep private pilot history and evidence local. Record draft-port limits: fresh specification reconciliation and full branch validation remain open.
The imported contracts still carried receipts from an older public base and stale scenario, ownership and host-acceptance descriptions. Reconcile the full port against published main while keeping installed-host acceptance gaps open. Wait for final-text classification before restart assertions, and allow isolated loopback fixture ports so parallel checkouts can verify independently.
Feature pushes and PRs selected different receipt bases for the same source. Limit push and manual verification to main, rejecting unsupported refs before verification or artifact creation. Retain exact PR/main comparisons and main-push release proof. Compare cached observation timestamps by instant so JSON timezone normalization does not cause UTC-only test failures. Refresh the contributor contract and affected reconciliation records for the approved policy.
Apply source closure to retained sessions during targeted PR refresh, and keep prepared nonreview intent stable when review defaults change. Preserve saved priority labels when system defaults are saved afterward. Reject overflowing archive entries before extraction and account for cached response sizes without decoding unrelated bodies. Retain historical dismissal IDs, bound asynchronous test waits, and align operator authority guidance.
Cancel each session's provider before taking its state lock and retry accepted source closure independently of remote freshness. Check the active GitHub principal during asynchronous review preflight while preserving immediate Start and offline follow-up behavior. Read attention and reference candidates without decoding unrelated retained snapshots. Preserve unresolved acceptance identities and strengthen failure and stale-inference assertions. Keep automatic skill-lock adoption unchanged under the PR's explicit scope exclusion; document that initial imports may replace local edits.
Materialize unanswered fallback questions after an interrupted checkpoint. Allow a disconnected session to resume with its submitted reply while retaining stale-turn rejection before claiming an active question answer. Keep native plugin resources under plugin ownership for nested archive layouts. Disable skills omitted by successful discovery even when their cached files remain, preserving managed skills and frozen run snapshots. Frame complete legacy journal messages before decoding, avoiding repeated prefix validation during progress backfill and restoring long human messages to Conversation. Keep malformed fragments in technical details. Refresh saved plugin status through memoizing hosts, clear recovered read errors independently from mutation uncertainty and retain supported custom check intervals. Preserve unread state until the displayed observation is fresh. Correct network-budget prose and restore the independent probe default assertion. Preserve the PR-wide exclusion of ambiguous standalone-skill baseline adoption repair and the accepted risk to edits preceding that baseline.
Treat opaque completion chunks as possible same-run conversation changes before applying question-settlement decisions. Keep their contents outside bounded helper evidence and preserve pending questions on stale inference. Return active-turn concurrency tokens only for running or waiting work. Keep historical turn identity separately so tracking can provide a usable same-session follow-up after interruption without weakening active guards. Make the delayed Start regression wait for returned-run state to reach the UI before checking the selected item and draft. Keep fixture snapshot reads behind that response so they cannot satisfy the processing barrier early.
Keep positive question evidence, shared durable recovery attempts and originating answer claims when restoring sessions under the port's cancellation and saved-message lifecycle. Use the constrained recovery path for its interrupted turn or final answer claim. Let newer owner work continue beside older unresolved diagnostics. Apply final-claim and sibling-retirement checks in the common attention transaction while retaining encrypted claims and uncertain non-replay. Show clarification progress and takeover without false attention. Stop progress when unconfirmed recovery exhausts its budget and retain explicit owner messaging. Align the maintained contracts and assertion mappings. Keep raw setup protocol evidence alongside exact task-call checks. Adapt retained-session fixtures to real Git worktrees and verify startup and takeover boundaries through causal regression and mutation checks.
Retain accepted ordinary starts before recovery normalizes saved state. Read the owning completed turn's saved final response and run the existing question checks, preserving completed work and final answer claims. Keep automatic review eligibility on owning-run metadata and expose the existing saved-detail Retry during cooldown. Reuse the validated provider inventory and align administration guidance with direct-target preparation. Verify the restart, takeover, metadata and cooldown boundaries with causal fixture tests while preserving retained authority and unread drafts.
Keep main's issue reporting and verified releases alongside the development queues, retained sessions and separate administration view. Resolve the provider boundary so fresh identity reads and pagination/cache checks remain effective. Share the managed request gate and persisted budget across the daemon and publication process. Cancel waiting publications before dispatch and retain request accounting and cooldowns across independent connections. Keep Reported issues keyboard reachable and within narrow viewports. Regenerate layered specifications and verification records against main.
dkropachev
force-pushed
the
sync/local-development
branch
from
October 26, 2026 21:33
8d8978b to
84223ac
Compare
dkropachev
marked this pull request as ready for review
October 26, 2026 21:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Published main trails local development, and the local pilot history cannot fast-forward onto the public repository. The current source needs a reviewable branch rooted in published history.
Fix
Port the current implementation, UI, plugin skills, fixtures and layered specifications onto the published main branch. The port adds Working, Issues, My PRs, Review PRs and Messages queues; direct item conversations and retained continuations; durable attention replies and recovery; dependency and plugin administration; bounded GitHub reads and review eligibility; and API call observations.
Retain the published verification suites, release delivery, generic operator guides and placeholder connection endpoints. The source export carries no private pilot history or operational evidence. The acceptance ledger keeps installed-host, callback, soak, login and manual accessibility gaps explicit.
This PR will verify feature branches through pull requests to main and limit push and manual verification to main. Manual feature-branch verification will be rejected; branches without a PR will receive no automatic verification or package artifacts. Exact comparison checks and successful main-push CI remain required for releases.
Standalone-skill registration and automatic lock import will keep their current behavior in this PR. The ambiguous-baseline adoption repair is excluded, including later review cycles and resumed work. First-time or previously imported skills can still have local edits replaced; this exclusion schedules no follow-up fix or issue.
Decisions