Repository navigation
Integrate durable media delivery and saved-storage maintenance (candidate graph) - #2029
Brian Krabach (bkrabach) wants to merge 44 commits into
Conversation
Checkpoint host API, explicit policies, per-file ledger and real CI retention adapter. Historical image/canonical bindings remain explicitly held pending their owning integration. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
Validate exact native ownership and indexed slices before replacement, preserve completed rebind receipts, hold unverifiable original image policies and exercise the real CI/Foundation diagnostic binding. Retain partial-stage and candidate-graph qualification limits. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
Keep combined selections explicit; a source with no qualified inline images goes through the existing expiry owner without staging a no-op conversion or weakening replay fences. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
Quarantine only the changed capture while unrelated diagnostics persist, classify exact Optimize receipt reads as passive Work recovery, propagate expiry metadata through coalescing/browser projection, and rename the operation-journal helper to distinguish it from app state publication. Actual client expiry rendering is a named canonical-client handoff. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
|
Candidate integration update at dc77a3f plus test-only 0ef1cf1:
Draft is still not merge-ready. Producer graph qualification, compound conversion/expiry, old-origin policy, final client57 acceptance/mirror/build and isolated/installed checks remain pending; no release/live effects. |
Reuse CI verified_optimize continuation without clearing its permanent replay fence. Checkpoint the completed image stage and preserve both maps; reconcile lost expiry acknowledgement without repeating prune, keep final diagnostic ACK inside writer/index fences, and report separate stage accounting with unknown aggregate contributions. Preserve quarantined references/outbox under ordinary age and count retirement. Exercise real owner stages, a lost post-replacement receipt and bounded 16 MiB raw diagnostic maintenance. Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
|
Retained integration checkpoint: exact pushed head3bee560f9dcb596b46fe06582a1c3d0d78510862/tree7811f939f46529396d43732d788ac705a2e703d8. This remains DRAFT, dependency-blocked, NOT complete or merge-ready.
Blocking external inputs: positive qualified post-hook graph/cooperative nested-route disposition (safe bridge remains always incomplete), original historical-provenance policy, named lifecycle owner, final parent Astra/Fable/upstream acceptance, accepted dependency graph/pins, canonical client57/676 acceptance then whole-copy/source-record/build/pairing, and assigned isolated test capacity. Runtime producers stay gated off; that is not forward-feature delivery. Old unknown-origin cohort remains held0eligible. No DTU, inference, live cleanup/migration/restart/adoption, merge, version or publication occurred. Finite evidence/branches/PRs are retained by manager152. |
|
Narrow host mapping-boundary repair pushed at exact 03d4743 (tree22e2e6d22919b9524dfbcbbdca4d279e4bab298f). CI maps nonblank physical events, while the current host rebind requires contiguous LF-terminated spans. Fresh host admission now holds blank-span/unterminated layouts BEFORE replacement or raw expiry, using bounded chunks during the existing source hash pass. This does not rewrite gaps, invent events, clear retained holds or replay uncertain operations. Original source/stat/cursor/reference/outbox guards remain. Cause-matched old3bee function overlay:9 FAIL leading/inter/trailing blanks after actual CI commit, retained. Final affected tests111 PASS/0skip/8warnings18.02s with exact task-owned CIe6de12c343a533187b836f4a99042c415eed2f18 + Foundation87d257e4057865688e9d0294ba170fe4ad1d1cec Git-archive imports; no installed graph/pin claim. Real CI stage/apply/combined and raw-expiry fixtures assert precommit refusal, source+sidecar/records/cursor/delivery bytes unchanged. Contiguous positives and lost-ACK reconciliation retained.16MiB single-event Python peak1,147,420B. Initial fixture IndexError and two overstrict VT/FF exception expectations retained/repaired honestly; CI may hold VT/FF before host callback. Independent exact changed-risk review clear, not separate test rerun or group qualification. Raw final log e36d20a3df83c73a2e6686931cf98662729281f1156d3525c85438f35edb65bc; JUnit378c0b7d2c8eb4fe45f55eadf956340abcb81a06eb188c5cffc7ff73170b315c. Full task remains open/dependency-blocked: production old-image original provenance/cardinality missing0eligibleheld, no multi-group binding/accepted graph, positive bridge/cooperative contract, parking lifecycle, client acceptance/synchronization/build and isolated qualification still pending. No DTU/live operations, merge or release. |
|
Current source checkpoint: 31c53bb, tree Parent explicitly accepted the truthful cohort boundary: refs-first future images and genuinely eligible diagnostic-expiry Optimize operations qualify separately; historical inline images missing original origin/group/TTL receipts remain held. No new raw captures or fabricated receipt registry was added to manufacture an old-image conversion pass. No reclaimed bytes or historical migration claimed. Positive Worker/child/transition and built-client browser qualification remain in progress. Prior remote missing-Foundation-module CI failures remain retained pending accepted root and worker dependency selection; no skips or protections were altered. |
|
Independent shared-policy integration is pushed at 0afe9c1, tree Actual focused source pairing with fixed Foundation |
Status
Draft: in progress, not ready for merge or release. Current head
a947e96b0f389bd842c173daecb24f8230e51247, treef7029ba74bff37fbbcf916d62cc66f9cc52d0355.Integrated source
ba4127997052df7b34045b58a374ca1e6d17c1abmerged as845768167, preserving accepted Windows/auth/ACP/managed-Docker/pricing work. All28 new-main nonclient/generated entries exact, all22 prior committed-reader entries unchanged. ExecutionEvents retains both pricing metadata and awaited media/options. Main release metadata is inherited, not a media release reservation.Focused evidence — separate immutable source inputs, not an aggregate
The actual media-worker owner reports a separate source-only fixture milestone09c98f5ce:two turns on one worker/provider/writer, explicit retirement then fresh-worker resume with private PNG and no replay. Manager read rawc2625337 and verified21 manifest hashes/7 host Git joins. It is NOT integrated here, installed parity is explicitly false, and three supplemental naming calls were refused attribution, not passed.
Remaining acceptance
Complete actual runtime root/finite/selected/nested/resumed media and prospective persistent-writer callers, cancellation/retirement and mode transitions; final exact host packet and accepted dependency graph in BOTH root and separately packaged worker; supported provider private-wire/privacy plus actual pixels; one installed guest with wheel/loaded-byte joins, real rendered Optimize/browser journey; remaining independent review and sole Release Manager publication.
Previous remote CI missing unreleased Foundation modules remains failed, not waived or green from source overlays. Current candidate upstream source is not an accepted merged graph. No Boolean/names-only/digest-only enablement, inferred append suffix, hidden canonical fallback or second writer.
Unknown historical origin/cardinality/order/original TTL stays HELD, separate from future refs-first delivery and eligible diagnostic expiry. No fabricated raw captures/receipt registry or net reclaimed-filesystem-bytes claim. Planned/unlinked/held/recovery values remain distinct.
Owned Unified guest0/cap1, program cap3 with separate Foundation/CI allocations. No duplicate guest, Core/new protocol, user live migration/cleanup/restart/adoption, Mac campaign, merge or media release. Current published releases remain independent; sole RM owns publication.