First run: Windows 10 / Shell or custom runner #6015

Activity

1. BigDataDZ commented on Oct 14, 2026

   

   BigDataDZ

   on Oct 14, 2026

   Last edited by BigDataDZ

   ContributorAuthor

   More actions

   Current Windows follow-through

   The bounded Unicode interpreter-discovery fix and installed writeback regression in #6430 are merged at 35cf8ce70914e2494b04ec04ac7b8016c2a13dc7 (reviewed head 5841f9efa285066cf4a945c95e0c6fb04504ba63). The digest-consumer dependency #6431 is also merged. These merges do not by themselves establish release adoption or automatic continuation.

   The author's native Windows source qualification passed 16 installer/CLI UTF-8 tests, including Unicode interpreter paths, install/doctor, skill preservation, rollback, real task lease/version, validator rejection and retry, fresh-process completion readback and identical receipt replay. The later local integration onto main ad863559af7a7cd6e10aa62137bbf69dd877fb3f passed the same 16 tests, 37 control-plane/text-I/O tests with two platform skips, and the complete packaged replan-cadence browser scenario after installing its test browser. Detailed CI attribution and integration evidence preserve the historical failed, cancelled and untested hosted checks; no full green CI claim is made here.

   Released 1.4.0: manual PowerShell reopen qualification (2026-10-15)

   At the reporter's selected PowerShell/manual boundary, installed the published loopx==1.4.0 distribution in an isolated environment and verified imports resolve to that installed package rather than the source checkout. Three separate native PowerShell 7 sessions used a disposable synthetic project and explicit registry/runtime routes; usage collection was disabled and no model or automatic driver was launched.

   1. Session one created a claimed Todo, acquired its task lease, wrote an unfinished artifact, persisted the recovery locator, and exited with the Todo still open. Process exit was checked before starting session two.
   2. Session two started from a different directory with a Unicode path. It recovered the same Todo and unchanged lease owner/version from durable state. Completion of the unfinished artifact was rejected and the Todo remained open. After writing the required UTF-8 artifact (Chinese text and emoji), completion succeeded and returned a nonempty receipt.
   3. After session two exited, a third fresh session read the Todo as done with the exact same receipt. Replaying completion returned the original receipt and changed=false.

   Result: the released 1.4.0 manual PowerShell state-recovery/writeback path passes this bounded synthetic journey. This is separate from the merged installer fix, which is not claimed present in that published wheel. It does not establish recovery of the original 1.3.1 project, expired-lease recovery, model/session transcript reattachment, automatic Agent continuation, Desktop or Lark. The original adoption checkboxes remain unchanged. The source install's long-path host limitation and any broader #5208 acceptance are not closed by this result.

   The useful next adoption check is the same manual reopen procedure against the reporter's intended real task, using its actual installed version and authority route. No new capability, release, deployment, benchmark or competing host integration is proposed.