feat: own work claims and reconciled task resources (#59) #110
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-59-work-resource-ownership"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #59, complete active AC1-6. Selected by owner-authorized /loop after accepted #56 integration. #105 remains independently eligible, not a #59 prerequisite. Canonical issue comments19422/19431/19440/19558/19576/19583/19588/19593/19598 preserve selection and all review dispositions.
Exact Subject And Budget
HEAD
75db6fc43ad4917a72df589b21357ea592bda723; base/merge-baseb11aae420517b14bbb4d85c84f9a0d82c14446c6. Ordinary branchissue-59-work-resource-ownership; eight normal owner commits retain the full history, ending75db6fc4. No rewrite/force/squash.#59 complete whole-PR reviews 7/10 consumed, all REQUEST_CHANGES on earlier exact heads, followed by scoped normal remediation. Current approval not claimed. #56 predecessor10/10 and distinct accepted recovery3/4 remain permanently preserved and separate; neither implementation-context recovery nor session resume reset any counter.
Actual Boundaries
Shared installed trusted-local WorkOwnership handlers support cooperative pull and retained managed profiles with host-bound Principal/profile/resources. Atomic exact-spec/claimant/eligibility/capacity handoff combines PrepareAttempt, original budget reservation, Operation, immutable baseline and increasing generation. Exact claim/publication replay returns historical evidence before live capture/profile/clocks, never renewed authority.
All fresh owned/generic preparation, reservation, candidate, acceptance and delivery paths share physical-resource fencing. Logical completion is not resource settlement; typed qualification binds exact original reservation/Attempt/workspace/request/fence. Count-only retry/remediation remains finite consumption. Fresh physical acceptance/publication requires qualified runtime and real effects; intent is validated atomically and delivery rechecks.
One retained-identity predicate covers generic work and every unreleased owned claim. Owned holds survive expiry/revoke/quarantine/settlement/logical completion until explicit durable release. Original A, matching observed R and inode/ancestor conflicts remain fenced; proved-disjoint B progresses. First physical admission records identity atomically; old owned identity is read only from original claim-digest-bound capture. Missing/unusable originals stay unknown, without current-path adoption or backfill. Session/effect and original native-witness requirements remain intact.
Fresh owned subject-bound decisions now capture the actual original-bound LocalOwnedWorkspace twice before the fresh independently durable clock cut. SQL consumes those decision-local byte subjects for acceptance, candidate checking/submission, first publication, runtime/publication rechecks and delivery, reconciliation and release. An existing-file edit after verification cannot commit satisfaction, free logical capacity or enable dependents. Capture is limited to the requested claim. Historical receipts remain capture/clock-free; logical FinishAttempt and qualified generic semantics remain unchanged.
Store rechecks use the smaller original task/project retained-byte ceiling as finite raw-read bound, not an invented historical max_bytes. Configured adapter limits,10,000-entry bound, encoded-retention accounting/dedup/headroom remain separate. A valid17MiB configured producer and explicit18MiB reconciled growth work within finite policy; small app limits and over-policy files still refuse.
Private-parent/token binding, bounded no-follow snapshots, explicit manual reconciliation, exact empty-only nonrecursive cleanup and durable retirement receipts preserve unknown/nonempty data. Schema5 backups/migration and actual old-reader refusal retain original IDs/history/clocks/artifacts. Frozen143/166/source leases remain unchanged.
Final Validation
Final resumed closed-environment make check/package-check/audit all passed on exact final content: 2,275 tests,85 existing native opt-in skips,106 subtests, pytest916.62s; locked/static/format/lint/types/inward-import/secrets/diff gates passed. Package checks prove reproducible builds, isolated actual handlers both modes, current-subject refusal/positive acceptance/publication/delivery, configured capture above16MiB, owned/generic alias holds and independence, original captures and all pinned-reader preservation/refusal. Audit found no known vulnerabilities.
Fresh-subject RED64 reproduced stale acceptance/delivery; configuration RED4 and managed-runtime recheck RED1/3positive exposed and fixed additional shared-entry gaps before this review. Full focused ownership suite536PASS. Edited data/original artifacts remain intact, independent clocks/cancellation survive refusal, and no filesystem callback executes after the final clock cut. The interrupted prior background validation was not counted as a pass; a new complete terminal receipt was obtained before commit.
Previous43fa CI3331/UI251 passed. Current-head CI, fresh complete independent approval/currentness and separate integrated acceptance remain required before owner-authorized merge/closure.
Limits
Trusted same-principal/cooperative namespace/native-group boundary only; not hostile same-UID containment, escaped-descendant isolation, strict physical expiry or provider billing. Unprovable legacy resources stay unknown. Native skips are not live/deployment proof.
No ADR0012 replan, schema/format/dependency/service/profile addition in this remediation, #105drivers/#106engine/#57remote API, new scheduler/agent/gateway, SR/MI/CC mutation, live inference/private payloads/main/release/deploy or gate waiver. PR remains unapproved and unmerged.
Final Independent Approval And Merge Receipt
Fresh GPT-6.1 Sol High whole-PR review 8/10, task
ses_e7dd40a1bffedEmji0f2H33VRp, returned APPROVE / findings[] for exact HEAD75db6fc43ad4917a72df589b21357ea592bda723, baseb11aae420517b14bbb4d85c84f9a0d82c14446c6. The reviewer independently inspected the full 29-file/8,959-line accumulated delta and active #59 AC1-6, verified initial/final canonical/local refs and clean checkout, passedmake check(2,275 tests,106 subtests,85 existing native opt-ins skipped;867.61s) and complete package checks. Parent final check/package/audit also passed; no independent audit claim is made because that command is outside the reviewer allowlist.Fresh premerge issue/eligibility/currentness, exact approved refs, clean checkout, empty findings and exact-head CI3332/UI252 SUCCESS were verified. Supported owner-authorized /loop merge succeeded at2026-10-28T11:22:04Z as
b1c9ffca16f06596e5c3afdca3b9893cf7422d8d. Canonical merged readback and normal fetch prove exact parents[b11aae42,75db6fc4], approved head ancestor of develop and integrated tree identical to the independently tested tree. No force, auto-merge, squash, branch deletion or direct develop push.Immutable #59 history: eight complete review invocations, seven REQUEST_CHANGES followed by APPROVE; 8/10 used, two unused, no counter reset after context/session recovery. All eight normal owner commits and prior negative evidence remain intact. #56 original PR108 remains closed/unmerged10/10; its explicitly authorized recovery PR109 remains separately completed3/4. No original or successor history erased.
This receipt supersedes the description's pre-review state without rewriting that evidence. Issue59 closure follows separate integrated active-criteria verification, then fresh canonical SELECT. Trusted/cooperative/native-group limits remain explicit;85skips are not live, strict-expiry, hostile-isolation or provider-billing proof. No release/deployment or external repository mutation.