Files
ARCADIA-Studio/harness/history/2026-09-11-state-before-gitea-migration/STATE.md
T

23 KiB
Raw Blame History

Progress Ledger — first release

Updated 2026-09-11, Codex-9e8r6t /root, Windows host. Release remains unaccepted. Windows/product work continues; Linux is paused by the user. The restart handoff preserves the earlier pause; current results and capacity constraints below supersede its active-status wording.

Objective and current source

Deliver the complete OA/SA first release in PROJECT_GOAL.md. The latest authoritative attachment is 815ff7b9-73c4-41a2-a809-635ecf8389d6/goal-objective.md, read in full and preserved in that file. It requires constraints/calculations, quantities/units and reusable libraries, plus uncluttered human/AI text-only modeling at small and large scale. Long homogeneous lists and poor behavior editing remain explicit concerns.

Local branch: codex/release1-9e8r6t, substantive source checkpoint df6f59562643b7771ecf0c972f8655f3e3f1c4da, committed, pushed and read back. It follows the user's instruction sync 07eb3cd. The preceding committed and pushed code/package checkpoint is 27df4a3945ebc97cd7cbde61f6aeea7a91c680d3. It includes named behavior creation, source CLI, the nine CLI packaging changes and reviewed evidence. Source CLI semantic commit 01b76a1, packaging assembly a0a48e8 and release integration 27df4a3 are distinct. Contextual prerequisite creation, its reports/oracle and 40 raw evidence files are integrated in df6f595; native acceptance continues. All 238 frozen build inputs and 44 exact index artifacts passed before commit. Gitea issue 1 records the handoff in comment 242. Remote AGENTS.md at blob 4b8465c8993107062ad2974c15a958d449530e92 adds the maintenance instructions announced in comment 229: concise current entrypoints, durable history and coordinated preservation rather than indiscriminate deletion.

Current acceptance checkpoint — postboot work

CLI publication evidence d95b1ab and complete OA native evidence c4bad4b are also pushed and read back. The reboot checkpoint preserves reviewed layout/owner caption WIP, native evidence and interrupted compiler records; it is not a new accepted build. This update follows published reboot checkpoint ca53f574e57381a523e946d5277b4081cff74355; the newer results follow below. After successive user reboots, the latest observed boot is13:59:33.500 UTC.

The postboot focused3 gate reached a real terminal before that reboot:25 passed, one new long-parent fixture assertion failed; no production visibility assertion failed. A reviewed test-only stronger fixture is frozen for focused4, preserving the same215-pixel host and all visibility guarantees. Automatic approval review blocked both exact proposed incremental-cache removal attempts before execution, with only blocked by policy; no deletion ran. Nondeleting NTFS compression recovered capacity instead. The incremental-cache pass was partially applied then intentionally stopped; the generated-binary pass completed exit0 across 282 files with every SHA256 unchanged. C had11,777,519,616 bytes free afterward. Supported Ubuntu26.04 installation finished exit0 at14:36:46 UTC (session32405), with10.51GB host space remaining. First actual root shell reports Ubuntu26.04 LTS, x86_64 Linux6.18.33.2-microsoft-standard-WSL2 and a mounted root filesystem. A systemd root-user-session warning remains recorded. The user316 mirrored/DNS settings were applied and runtime mirrored mode verified, but the guest had only loopback, no route and failed DNS/HTTPS. Read-only host IPv6 evidence is a cause hypothesis only; no global registry/adapter/VPN/firewall change was made. User328 now supersedes that trial with VirtioProxy and explicitly makes AmneziaWG immutable, including inspection. Its exact VirtioProxy-only config is saved; both the initial startup and one persistent root-shell retry after compilation ended with CreateVm/0x800705b4 before guest commands. A distinct WslService-only restart then failed at Windows service access; it remains Running. No elevation workaround, extra launch or other service/network change followed. This is a startup timeout, not a measured VirtioProxy network failure. Root rechecked the Gitea issue through comment348 after renewed user steering: owner328 remains the latest posted solution and is already applied. Verified official Rust archives and all60 exact Ubuntu packages are prepared via Windows HTTPS; Ubuntu signature verification and installation remain mandatory. Windows focused4 passed26/26 after11m05 compile and9.54s test execution, retaining every geometry assertion. Strict all-target Clippy and workspace format also passed. Matching GUI compilation also passed; session87425 is terminal and no compiler lease remains live. Immutable GUI SHA256 is 5657BAB5C841939B66F901EFE6C0FFB2D7CBBE8CC5F111A0CA3DE8073D3846CE. All238 actual source inputs were rehashed unchanged. After the26 affected tests, the immutable complete desktop executable passed all679 tests at15:47:53 UTC, zero failed/ignored/filtered, exit0, one test thread and ordinary Windows stack. The user subsequently directed that Linux builds and checking be skipped until they notify us that WSL networking is resolved. Linux setup, launches, diagnostics, builds and checks are paused; preserve current configuration and inputs. This direction is recorded in Gitea comment356 and supersedes service-access next steps. See WSL readiness.

Fresh GUI5657 v2 Lifeline baseline opened through the native file picker. At 1100x700 client size with both panels, child Name, Activity, OA root and pinned Back/Use controls were visible; a maximize/restore retained both raw names. The completed recovery record passed exact accepted-baseline, raw parent/child, kind/root and reserved-ID checks before a controlled isolated process stop. Recovery restored an unsaved local copy with an exactly equal accepted baseline and authored behavior/identities. Child Escape retained the parent; a new blank child, temporary Use and parent Cancel left nothing to undo. Save As to a fresh destination passed the unchanged core oracle with exactly two source files. The isolated process closed normally. A fresh direct Lifeline trial subsequently passed actual Create-before-Save, one Undo/Save and one Redo/Save against the complete independent model/source/original-ID contract. Fresh Machine owner visibility at minimum size, actual Create and open, one Undo/Save, one Redo/Save and real-picker reopen/SA/Save also pass the unchanged complete contract. All new source and consumer identities persist; Undo retains only the two proven generated files. The final six-file reopen equals Redo exactly, and all isolated native processes closed normally. See the v2 native report.

Peer956 comment338 reserves our bounded syntax-only language outline seam; their codec/lifecycle scope remains separate. The query experiment is private, uncompiled and not integrated. The current design is text navigation; a discovered Unicode path-collision mismatch is being corrected in a separate proposal. Independent outline review additionally requires rejecting noncanonical UUID spellings as authored navigation anchors and recommends folding paths once. Root verified the parser mismatch; the author is preparing a separate v2 patch.

  • CLI BAD169F8…E3559: author 12/12, strict all-target Clippy/format/build pass; independent 183 assertions across 21 fresh processes pass. All four committed experiment files retain their measured bytes. JSON describes complete changed files, not a saved whole-candidate plan. See the two source-CLI reports.
  • Contextual source first frozen artifact 6E677F58…8CC0: focused 22/22 and full desktop 675/675 pass, 448.33 seconds execution. The later inactive-source origin bypass and guide wording are fixed and independently reviewed. Final source across 13 desktop files passed 23 focused tests, 3 guide tests, strict all-target Clippy, matching GUI build and formatting. GUI SHA256 starts 52DE82E4; its test inventory is 676. There is no full 676-suite pass. Root verified the frozen inputs/executable and launched PID 7212 in the isolated .local/native-qa/contextual-source-20260911-v1 stage. Lifeline Save-adoption and Chain direct Create each pass complete model/source and one Undo/Redo. Machine direct Create/Save and Undo/Save pass; its Redo remains pending. A fresh-profile postboot Open/SA view/Save now passes complete six-file model, source and original identities. That GUI closed normally. See native results.
  • Native scenario B3: both OA use-return paths pass wide and minimum sizes; both SA paths pass minimum focused canvas. Pending disabled Open preserves the draft; explicit Cancel/Save matches exact baseline. B2 OA Action, nested State, explicitly bound Reuse and Fragment all pass independent complete Project and two-source Create/Save, one Undo/Save and one Redo/Save predictions, retaining original exact identities. Final OA reopen/Save also passes. SA B2 remains pending locally; B3's earlier size/layer scopes are unchanged. See local scenario native evidence.
  • Root published GUI/server release 1, v0.2.0-preview.authoring.20260911, at 12:40:51 UTC, using source 2ec72d4, D4D9 GUI and EFEE server. ZIP 664F30B6… has 559 files and passed strict notices, independent complete archive/source correspondence, clean GUI launch/example/Save/help/close and server create/get/restart persistence. All three release assets passed full downloaded readback. Reports/raw evidence are committed in 6a61061; see GUI/server publication. This is a prerelease, not full OA/SA acceptance.
  • Root published CLI release 2, cli-v0.2.0-preview.authoring.20260911, at 12:50:39 UTC. Tag and release readback match 27df4a3, draft false and prerelease true. ZIP 2B051F8C… has 114 files, 27 notice packages and exact BAD169F8/F456 executable/runtime. Independent clean CLI 156 assertions across 10 invocations pass; all three uploaded assets passed downloaded hash readback. Publication report preserves the exact records and distinguishes local CRLF notes from the public LF body.

Completed work and scoped evidence

  • Palette inline naming and focused Escape: 7d1df4f, independently published as codex/palette-authoring-20260910. Candidate 2 focused tests, GUI build and strict desktop Clippy passed. Its native F2 rename/Save/Undo/Redo matched exact three-file expectations; Entity creation matched the complete independent model/source oracle. Candidate 3 completed ordinary Activity, existing placement, allocation, direct Interaction and F2: complete basic model/four sources PASS. Explicit SA actor/destination transition passed complete model/six sources; Undo four-source baseline, Redo six-source result and reopen all passed. Six physical files are byte-identical across reopen/reuse-preview Cancel/Save. Immutable checkpoints/logs: .local/native-qa/palette-20260910-v3/.
  • Recovery naming autofocus: 31b7dc3, 13 focused checkpoint tests passed after integrated compilation. The later SA behavior draft's native recovery, autofocus and Escape evidence is recorded in the creation report below.
  • Other-host behavior/topology/scenario/history: original 01bb52a integrated as 057eddd; constructor cache fix b6b76ef integrated as a70de55; explicit history seed fix 4ecad78 cherry-picked as 81668f9.
  • Corrected immutable desktop artifact completed 631/631 passed, 408.18 seconds, exit 0; all three prior 618-artifact failures are fixed. Exact artifact/logs in .local/scenario-workspace-20260910/tests-81668f9/. It covers 3978bbe workspace, Back/OpenUse guards and both history fixes, but not later Sensor/creation work.
  • A real same-size owner/document Sensor regression led to d114a27; affected scenario 53/53 passed. Historical native candidate 3 predates that correction. Mounted workspace tests cover 500×570 and wide geometry; later local native B2/B3 results have the separate scopes recorded above.
  • Named local creation passed final 21/21 and guide 3/3 after ancestry-label correction. The matching immutable desktop suite passed 653/653, 362.83 seconds, zero failures/ignored; exact artifact 864B0F…E86 and logs under .local/behavior-creation-20260911/tests-final. Independent integration review found no additional correctness blocker. Strict Clippy with all targets and -D warnings, plus workspace formatting, pass after one behavior-equivalent history_fields let-chain correction; affected history 63/63 and matching GUI rebuild pass. This frozen creation GUI is gui-verified SHA D4D9C2BD…B20C31. At actual 1100×700 client size, named OA Process, explicit ParticipantInteraction Scenario with capability context and SA owner-linked State machine plus requested first view passed complete independent Project/SourceBundle checks at 7/8/9 files. Each single Undo/Redo preserved exact expected semantics, sources and role identities. Reopen/Save retained all nine physical source files byte-for-byte. Wide/minimum draft cancellations retained the initial six files exactly. Detailed report: native creation.
  • Independent creation oracle v2 corrects a harness assumption: Save retains known detached source files after Undo. Full Project and reachable source equality remain mandatory; the complete physical inventory must equal the explicit pre-Undo checkpoint overlaid with expected reachable bytes. Unknown, changed or missing retained files fail. No product defect was hidden by this correction; see oracle review.
  • Fresh source-7 constructor probes passed 54 explicit/omitted comparisons and 12 required-field refusals across OA/SA, with complete typed models, canonical reparse and exact authored no-op/name-edit retention. Constructor and Scenario default wording now describes current behavior; strict HTML regeneration passed. Other constructor families are explicitly outside this evidence. See default review.
  • Source schema checks passed: 72 fixtures, 204 schemas, 14 families, 90 scalar leaves. API/language reST rendered with strict docutils without warnings.
  • Packaging committed b98f135: portable Linux adapter, shared package checks, Docker input validation and exact upstream notices. Independent review found and fixed five concrete defects. Python 11/11 and PowerShell contracts pass. Historical Windows-input ZIP has 557 files; real Linux notices close over 339 packages/681 files. Linux archive adapter used inert ELF fixtures, not actual current application binaries. Exact Fira/Cantarell notice Git bytes were independently verified. Later exact GUI/server and CLI packages have their own regenerated notices and published artifact evidence above.
  • Independent native Capella creation study completed, saved and closed cleanly; report release-capella-creation-study-20260910.md is complete. Viewpoint-first naming and distinct local create/existing selection inform the implementation.
  • Textual usability audit completed three static tasks and example counts. The existing grammar already permits omitted initial IDs/defaults; key gaps are cross-file reference context, safe alias refactoring and reviewed patches. Source-7 EBNF/schema documentation and viewpoint omission guidance are corrected; generated language HTML passed strict docutils. Both concise snippets passed 26 real REST requests: identity-only stabilization, exact no-op/name edit, stale/invalid nonmutation and restart persistence. All 120 current core/server files match the preserved source-7 binary's documented snapshot. This closes the bounded recipe gap, not large-model or native text-editor acceptance. The verified recipe is now examples/text-first and in the language reference.

Detailed evidence: integrated gates, palette native, scenario workspace, creation design, packaging implementation, independent packaging review.

Active ownership and execution

Root owns integration, native input, commits, publication and Wiki updates. GUI5657 native trials and the complete679 desktop tests are terminal; no owned Studio, compiler or test process remains. All Linux actions are user-paused.

  • release_audit: full-suite/recovery archives frozen; now audits updated Windows package inputs and per-binary source provenance without building.
  • behavior_audit: Lifeline evidence frozen; prepares separately reviewed v2 bounded outline/query proposals. No production application or compiler lease.
  • linux_readiness: Linux remains paused. Completed independent outline review; now preserves only the completed Windows Machine evidence.
  • Codex-956atf: owns chooser/workspace/focus, shared canvas shell and isolated schema8/local-definition core. Reported focus5/5, analysis28/28 and numeric26/26 plus core Clippy; codec/lifecycle work remains separate. None of that later peer source is integrated locally. Our bounded language outline seam is reserved by comment338; source8/codec ownership remains theirs.
  • Codex-ytr83r: owns external B4 Scene/lifetime integration and Linux packaging. Linux work is paused; peer host results cannot substitute for local execution.

User issue2/comment250 calls for consistent, domain-constrained interactive diagrams, not necessarily arbitrary placement. Codex-956atf owns the shared canvas-shell implementation in an isolated worktree (comment261). Existing technical Canvas widgets and source cards do not close this requirement. Local Ubuntu26.04 is installed; the last two startup attempts timed out before guest execution. Preserve that history and verified inputs while waiting for the user's explicit notice that WSL networking is resolved.

Verified bundles for eb5161b and 4ecad78 are retained in .local/integration-20260910. Local refs codex/behavior-snapshot-eb5161b and codex/history-seed-20260910 preserve exact commits. B4 lifetime projection and its guide delta are not integrated yet; coordinate shared scene wiring. Review found insertion versus lifetime bounds, activation after branch-local Delete and unassigned-lane map differences that must be addressed before acceptance.

Unresolved requirements and gates

  1. Finish native basic supplementary move/camera/focus/minimum matrix and current scenario/process/state tasks. Main basic/transition/history/reopen passed at wide size. Check raw drafts, recovery, exact source and real task completion.
  2. Publish the verified contextual missing-source/source-form milestone with truthful Windows package inputs. Named and contextual creation/history/reopen pass; operand-editing and qualified Action allocation remain separate work.
  3. Constraints/calculations and quantity compatibility are currently descriptive metadata; same-project includes are not maintained cross-project libraries. Peer schema 8/local-definition implementation is now ratified and staged in its isolated worktree (Gitea comment 231); local integration and all required representations/acceptance remain pending. See library review brief. Other-host proposals expose cosmetic package revision/type compatibility, subjectless analysis closure and text-only instance normalization decisions; full reports and paired criticism are now available from verified c6d296a. Its 218-assertion maintenance experiment supports explicit baseline values with one-level Case overrides; complete freeze and effective-case evaluation are required. Refined baseline/library contracts remain active externally.
  4. Build on the published standalone CLI and compare language improvements using both local usability and complete other-host proposals. Current grammar+tooling, domain syntax, namespaces and portable identity modules remain distinct candidates. Concise examples/CLI alone do not prove uncluttered modular engineering authoring or safe large-model changes.
  5. Run coherent current desktop/core/server, specification, examples, REST and optimized packaging gates after integration. Prior passes remain scoped.
  6. Obtain current Linux runtime acceptance through the external owner's supported guest route. Local WSL2 import failed with HCS_E_HYPERV_NOT_INSTALLED and no distro registered; this host still has no usable Linux runtime. Preserve recorded route failures and do not repeat a rejected workaround.
  7. Fresh independent cross-disciplinary release review remains required after actual workflow and semantic acceptance, with all material findings resolved.

Handoff and publication

Use Gitea issue #1 and current Wiki to coordinate as Codex-9e8r6t. Read before resuming; preserve the other host's work. User issue 1 comment 178 authorizes programmatic reuse of existing MCP credentials for Git/REST without printing or committing them. Authenticated non-force push and remote readback now pass; current branch is available directly. Historical bundle transfers remain reproducible. Integration 3978bbe was published and independently fetched/hash-verified as a Git bundle on codex/integration-transfer-20260910; Wiki Integration3978bbe and issue #97 own exact transfer instructions. Other host has integrated it and an equivalent Sensor fix. Creation 4bb4aaf was likewise published on codex/integration-transfer-20260911, file harness/transfers/creation-4bb4aaf.bundle.b64: decoded 105022 bytes, SHA256 0DEFAE91A56430076C432758F923BC0675911DA9FA7588C9961FF15F47EAEBF6, prerequisite 3978bbe. Anonymous Git readback, strict base64 length/hash check and git bundle verify passed; issue #128 gives selective integration instructions. Corrected oracle/native/default evidence is published as 2ec72d4 on the same branch, file harness/transfers/evidence-2ec72d4.bundle.b64: decoded 185563 bytes, SHA256 F74E14EE394BCC026E24987C8526AA7E769DDE748FE38117532824EC19AE159F, prerequisite 4bb4aaf. Anonymous readback/hash and bundle verification pass (#150). Preserve the other hosts' B4/reference chooser/design work and avoid duplicates.

Other-host c6d296a transfer is verified and imported as local codex/behavior-snapshot-c6d296a: 334830 bytes, SHA256 526A80E2D32ED0E57A7B2372B5F02D4652E8751DFEBA81953C4F045225D6AACB, prerequisite 1797516, from codex/behavior-transfer-20260910 file harness/transfers/behavior-c6d296a.bundle.b64. Selected analysis/library/text reports, criticism, experiments and independent scenario oracle are restored; 51 evidence files compare byte-for-byte with Git blobs. No source/ledger merge. Issue comments 136/143 and Wiki Authoring20260911 record the handoff.

The old ledgers, including all historical platform and native evidence, were archived byte-for-byte before this consolidation in history/2026-09-10-ledgers-before-second-consolidation, with hashes.json. Their historical-current wording does not supersede this file.