Repository navigation
LA: keep Runtime egress authority out of provider Init #143
Description
Part of #84.
Selected saved fix from #84: 8ac5ad8f. Runtime keeps the connection authority marker in private operator configuration and projects the native provider's strict Init schema.
Base and PR target: develop, approved by Anders under the weekly task rules; current fetched and merged base de1db928063425856498785476809fe939663738.
Done means: the provider Init projection omits the Runtime marker while preserving saved authority and credential ownership; focused source checks and exact installed provider Init pass; the isolated Home connection activates clearly; required security and human reviews approve the candidate and its task PR is merged.
Reuse the prior direct installed-provider Init probe as historical input. Home activation remains an acceptance gate; retain this task open until proof and reviewed merge pass.
Preserve existing Homes, keys and data. A fixture requires its own lifecycle receipt and stopped processes.
Activity
andersalm commentedon Sep 30, 2026
Draft PR #144 publishes clean cherry-pick
cfdd1dcetoorigin/fix/0.7.1-model-init-projection(0 behind / 0 ahead), targetfeat/0.7.1-models@ea670e27.All four basic gates and 11 hosted hint/projection tests pass, including marker removal and preservation of saved connection authority.
Independent security review passes exact diff SHA-256
30e6176467f393afb5587944bd88ccf3ac1e08f3581e8d58712b721a5056f130: Runtime retains authorization and credentials, and the native strict schema stays enforced.The prior direct Init result is historical input; exact installed Init and isolated Home activation remain open. Required human review is Irzhy when ready.
Next: prepare the saved Home authority assertion test from #84 as its own PR while CI runs.
andersalm commentedon Sep 30, 2026
PR #144 at cfdd1dc has all eight required CI checks passing. Independent security review passed; the draft remains open for exact installed provider Init and Home activation proof.
andersalm commentedon Sep 30, 2026
Published normal
develop@938a5926mergeeac88f5a50fa664d798bed3d64cfacd946231db8, tree4a066be8ab425d40ba0e95405bac218b2ed87e5e, toorigin/fix/0.7.1-model-init-projectionfor PR #144.The task diff remains byte-identical to accepted independent security review SHA-256
30e6176467f393afb5587944bd88ccf3ac1e08f3581e8d58712b721a5056f130. Incoming base changes are version/lock/docs alignment.All four basic gates pass; the checkout is clean and task-remote divergence is 0/0. Current-candidate CI follows this push.
PR #144 stays draft for exact installed strict Init and isolated Home connection activation. Irzhy is the required human reviewer when ready; #150 is adding CI installed journeys.
Anders approved
developas the task target. Existing Homes, keys and data are preserved. Next: complete saved PR #146 and #147 integration gates.andersalm commentedon Oct 1, 2026
Published normal current-base merge
ef292436d293745b70da73566df14fe0c4aa7c1a, treefc208c2c2d1cb25062dfbbb5fc1b96ab54fe4b42, toorigin/fix/0.7.1-model-init-projectionfor draft PR #144.The approved base is
develop@de1db928063425856498785476809fe939663738. Incoming Home assertion and private Engine request changes merged cleanly with preserved history.The task diff remains exact accepted independent security review SHA-256
30e6176467f393afb5587944bd88ccf3ac1e08f3581e8d58712b721a5056f130; all four basic gates pass.The task branch is clean with remote divergence 0/0. New-candidate CI follows this push; completed prior-candidate run
36786322235succeeded and supplied zero downloadable artifacts.The verified model-provider from run
36783916734, original source26de9c52, has SHA-2568a76e990a241f0fbd1a627266f6e0241c698e3b77f53bf1c0e0e8fc85ce86db7; native model-provider, model-contract, toolchain, features and lock inputs are byte-equivalent to this candidate. Its original provenance stays in the receipt.An exact candidate Runtime artifact remains required for installed strict Init projection and isolated Home connection activation. The existing #141 Runtime has different source inputs.
This bounded pass used light checks while the readiness fix owns the Mac build slot. Existing Homes, credentials and proof data stay preserved.
PR #144 stays draft; Irzhy review follows exact installed acceptance.
andersalm commentedon Oct 1, 2026
Source-only shared-proof check for draft PR #144 at
ef292436: currentdevelop@de1db928selects the MacProviderBridge::spawn_confined_modelpath.That profile uses
allow defaultwith Runtime-selected socket exceptions to denied outbound networking; file reads, engine execution and engine socket files remain allowed by default.The separate #141 delta adds child file confinement, receipt-qualified engine/dylib reads, admitted-file namespaces, journal write ownership and engine socket file allowances. It does not supply a missing engine executable or reply adapter on develop.
Thus #141 is a separate file-isolation acceptance gate, rather than a source prerequisite for a Mac native local-engine reply under develop plus the #154 readiness correction.
This is a source conclusion: exact installed reply, package readiness and cleanup still need the isolated candidate receipt and qualified provider artifacts. The retained #141 reply/descriptor evidence belongs to its own source and stays unchanged.
An exact #143 Runtime artifact remains the prerequisite for its strict ProviderInit and Home connection activation proof.
andersalm commentedon Oct 1, 2026
The exact Runtime artifact for current draft PR #144 will now build from clean
ef292436d293745b70da73566df14fe0c4aa7c1a/ treefc208c2c2d1cb25062dfbbb5fc1b96ab54fe4b42.The #154 build has finished and its binary has verified custody in its own fresh fixture. This task now owns the single heavy local build slot; its native provider remains source/hash-qualified from #97.
This produces the missing candidate-bound installed input while #154's separate isolated product journey runs. Source changes, accepted basic gates and the unchanged independent review remain intact.
Installed strict Init, isolated Home connection activation and required Irzhy review remain open. Existing Homes, keys and data stay preserved.
andersalm commentedon Oct 1, 2026
Current PR #144 Runtime built from clean
ef292436d293745b70da73566df14fe0c4aa7c1a/ treefc208c2c2d1cb25062dfbbb5fc1b96ab54fe4b42in 1m54s.The built Runtime SHA-256 is
6d89048beb30e9e5ef0d9c4bdb838480dd547a3c0680ef2f5044f49d53a07625; the private receipt binds source, tree, command and final artifact. The heavy build has finished.The existing model-provider package remains separately source/hash-qualified. This artifact now supplies the missing exact-candidate input for isolated strict Init and Home connection activation.
Installed acceptance and required Irzhy review remain open; this build result alone does not prove the user journey. PR #144 stays draft and the task branch remains synchronized.
andersalm commentedon Oct 1, 2026
Runtime and the native provider are installed in a fresh isolated fixture for PR #144, candidate
ef292436d293745b70da73566df14fe0c4aa7c1a, treefc208c2c2d1cb25062dfbbb5fc1b96ab54fe4b42.Built/copied/installed Runtime SHA256
6d89048beb30e9e5ef0d9c4bdb838480dd547a3c0680ef2f5044f49d53a07625and qualified native model-provider SHA2568a76e990a241f0fbd1a627266f6e0241c698e3b77f53bf1c0e0e8fc85ce86db7match their receipts; installed-provider verification passes.Served Home authentication, System and Inbox files match the exact candidate. Original native package provenance and source-equivalence qualification remain separate from the Runtime build.
The run stopped at signed Home bootstrap, before hosted configuration Save. The first fixture permission error was corrected; the recovered passkey reaches a readable lock screen, while the helper checks unlock visibility before waiting for Home's authentication state.
Next: make the existing bootstrap wait for signed-ready or the visible lock-face/card, then use its fixture-owned passkey and actual System Check key → Inbox consent → Save controls. Strict hosted Init and connection activation remain open.
Final cleanup passes with zero owned processes and reusable gateway/fixture ports. The retained fixture is 343 MB; free disk is 12.78%. Existing Homes and #141/#154 evidence stay preserved.
The task source remains clean, origin divergence is 0/0, and accepted source checks/security review remain unchanged. PR #144 stays draft for installed acceptance, exact current CI and required Irzhy review; human UX is a separate gate.
andersalm commentedon Oct 1, 2026
The corrected existing fixture adapter waits for Home's async lock-face before its control branch. The retained disposable passkey now passes authentication begin and complete with HTTP 200, and signed Home opens System Models.
At exact
ef292436d293745b70da73566df14fe0c4aa7c1a, actual Check key reached a separate fixture input gap: connection consent requires an HTTPS origin, while the reused generic validation fixture used loopback HTTP.Runtime, provider and served-file hashes stay unchanged. The next step is the existing owner-scoped HTTPS loopback fixture with disposable trust, then actual Inbox consent and Save. Strict hosted Init and connection activation remain open in draft PR #144.
Existing Homes and all retained auth/data remain preserved; the ended phase's owned children stopped.
andersalm commentedon Oct 1, 2026
The isolated signed Home passed System Check key, actual Inbox approval, Save and Use in Assistant at candidate
ef292436d293745b70da73566df14fe0c4aa7c1a, treefc208c2c2d1cb25062dfbbb5fc1b96ab54fe4b42for PR #144.The retained staged connection recovered through Continue setup. System shows the model saved with hosted connection approved, and Assistant advertises that exact offer through its own launch authority. Readable automated media remain private; human UX is a separate gate.
Actual Save returned HTTP 200 after Runtime's awaited native
op:initrefresh; the strict installed provider accepted the hosted offer. Saved Runtime authority marker and private credential reference remain intact, with the fixture credential preserved in a 0600 secret file and inline credentials omitted from configuration.Built/copied/installed Runtime SHA256
6d89048beb30e9e5ef0d9c4bdb838480dd547a3c0680ef2f5044f49d53a07625; qualified provider SHA2568a76e990a241f0fbd1a627266f6e0241c698e3b77f53bf1c0e0e8fc85ce86db7. Source, manifest, capsules, original native provenance and installed hashes remain receipt-bound; served Home/System/Inbox parity passes.The fixture adapter now waits for async lock-face rendering. Connection consent used an owner-scoped HTTPS fixture and a separate server certificate under disposable fixture trust; existing product source and retained auth/data stay unchanged.
Final cleanup passes with zero owned children and reusable ports. The fixture remains below 1 GiB and free disk is 12.68%; existing Homes and #141/#154 evidence stay preserved.
The branch is clean with origin divergence 0/0. The unchanged four basic gates and independent security review remain accepted. PR #144 stays draft pending the current-candidate check receipt and required Irzhy review/UX acceptance; installed Init and Home activation gates now pass.
andersalm commentedon Oct 1, 2026
PR #144 is ready for review at exact
ef292436d293745b70da73566df14fe0c4aa7c1a, treefc208c2c2d1cb25062dfbbb5fc1b96ab54fe4b42; its body now records the final behavior and accepted installed proof.The issue base now names current approved and merged
develop@de1db928063425856498785476809fe939663738. The task branch is clean with origin divergence 0/0.Built and installed Runtime SHA256
6d89048beb30e9e5ef0d9c4bdb838480dd547a3c0680ef2f5044f49d53a07625match; the source build receipt SHA256 is7dbba17643c79417ee9787afaf52f2926791c29f543fb8e4883b119eaf9b2a05, and installed receipt SHA256 is837779b98443fa80febe72bad826c48235d3a73b3b09cb0282b4049cec0b54f1.Current CI run 36796945194 passed all eight required jobs, including Linux x86/ARM and Mac source Homes; release publication was skipped. This completed result is reused without another CI read or test run.
The exact current task diff SHA256
30e6176467f393afb5587944bd88ccf3ac1e08f3581e8d58712b721a5056f130matches the accepted independent security review. Four basic gates and focused source checks remain accepted.Installed strict native Init and actual signed Home connection recovery/approval/Save/Assistant handoff pass. Runtime retains saved private authority and credential ownership; readable automated media remain separate from human UX acceptance.
All owned processes stopped and both fixture ports are reusable. The private lifecycle ledger now records QA / Review and evidence retention; existing Homes and #141/#154 proof stay preserved.
I requested required human reviewer
irzhywauonce after removing draft status. #143 remains open for that approval, human UX acceptance and reviewed merge.andersalm commentedon Oct 1, 2026
PR #144 remains at
ef292436d293745b70da73566df14fe0c4aa7c1a; task/remote divergence is 0/0.Independent source review round 2 PASS: the unchanged task diff SHA-256
30e6176467f393afb5587944bd88ccf3ac1e08f3581e8d58712b721a5056f130keeps saved authority/credentials with Runtime and retains strict Init refusal checks.Compatibility with
develop@c9205a74passes, merge treed799c38532b1a01c3bb01a5551277bb634fad4cf; its task delta has the same hash and narrow diff checks pass. Develop/task divergence is 15 behind / 3 ahead.Accepted installed proof and the first security review remain qualified; this pass is source review and reuses those checks.
Next: Irzhy's approval and required human UX acceptance before merge. Broader provider isolation remains with #173.
andersalm commentedon Oct 2, 2026
PR #144 merged into develop from
ef292436d293745b70da73566df14fe0c4aa7c1a; the normal merge follows #155 and #142.CI 36796945194 passed all eight checks; 11 projection/hint tests and the basic gates passed. The operator’s adversarial review is PASS.
The exact isolated installed Home completed Continue setup → Check key → Inbox approval → Save → Use in Assistant, with native Init refresh and preserved private authority/credential ownership. Owned-process cleanup passed.
This meets the Done means under Anders’s 2 October rule. The strict-config deserialization test follow-up stays with the installed Init fixture in open #150; branch history and private proof remain preserved.