ARCADIA-Studio/harness/release-teaching-native-20260906.md

Teaching project native acceptance — 2026-09-06

Status: bounded onboarding, reviewed-name/source/history and reopen checks pass; complete tutorial acceptance is still in progress. Root operated the actual Iced application through the authorized Computer Use API. No UI state was synthesized through application internals.

Exact environment

Windows 11, minimum client size 1100×700 (captured window1102×732), process9672, staged .local/native-qa/bin-source6-behavior-context/arcadia-studio.exe. GUI SHA256 F5ECAEC02BBAFBC6F3BDC6ADEB746AFE91F3A495C6D9564A68DEA41E61AC9246; server 1F98F02DBC9FB2D9AFA3C42BB0CB4038BAAE81C85EF17365B5CB486669E749F8; runtime DLL F45604A12E8BCD839FD86F667C1BE1CC7C4F9DA2B3C69FF381AC708F0E1AE7D4. The corrected packaged example has94elements,62relations,5views,68traces and30reachable source files; the whole folder contains37files. This differs from the earlier28-source Linux snapshot.

The whole staged example was copied to .local/native-qa/water-pressure-working, including its README/evidence/generator inputs. All37file hashes matched the staged original. Tests used the copied project.arcadia; packaged teaching sources were preserved.

Observed and checked

• Home displayed complete whole-folder copy guidance and a reachable walkthrough action at minimum size. Home and the end of the guide's Build first model topic both opened the corrected packaged project. Returning to the copied project through recent models worked.
• Source displayed30files, the entry's includes, and syntax highlighting. Appending the invalid raw text {unfinished 雨 then attempting the Home walkthrough action produced the normal Keep changes guard. Cancel retained the exact raw editor buffer and located lint (project.arcadia34:13, invalid token雨). One Undo Text restored the original draft. All37copied files remained byte-identical; the trial made no file save.
• Before the tutorial rename, Model checks showed the one intended warning. Its Open action selected SA @sa_audit_thresholds and its actual description/performer context.
• OA @oa_confirm was renamed to Confirm stable pressure, applied and saved. The complete folder was preserved as .local/native-qa/water-pressure-before-review.
• OA→SA semantic review selected the existing counterpart and Header Name, Take Operational: one decision, zero resets and zero additional impacts. Apply changed SA @sa_confirm to Confirm stable pressure, preserving the deliberately distinct System name. Save all succeeded on its first submission. Relative to the OA-only rename, exactly sa/functions/function_sa_restore_work.arcadia and traceability.arcadia changed. The accepted37files were preserved as .local/native-qa/water-pressure-reviewed-accepted.
• The independent checker harness/native-release1-review-check.rs reproduced the lesson generator, OA rename and actual core semantic NameTake/source update. The actual full Project and all30source files matched without UUID, metadata, ordering or whitespace normalization. Separate OA-only and reviewed checks passed.
• One Undo/Save restored all37files exactly to the OA-only baseline. One Redo/Save restored all37files exactly to the accepted review. The root reran the independent review checker after Redo: PASS full model/all30source, with preserved OA baseline verified. .local/native-qa/water-pressure-redo-hashes.json records37comparisons/zero mismatches. All four saves (OA rename, reviewed result, Undo, Redo) succeeded first submission.
• Home recent-model reopen restored the accepted saved project and the visible OA reviewed name; no dirty indicator. The independent full model check establishes both names and unchanged System identity; further SA visual reopen inspection belongs to the follow-up navigation-fix replay.
• Behavior opened the assessment procedure and the main alarm-response process. At100%, the assessment reference and its1/1source preview were readable and selectable as @oa_assess_step. Fit overview showed the full six-contribution topology at23%. Opening Two paths showed a pending form with Create disabled and reachable Cancel; Cancel restored clean state without creating records. No two-path commit or full reusable-procedure drill-down is claimed from this trial.

Findings and remaining work

Semantic Apply produced correct accepted data but changed the layer/selection after view normalization: SA properties appeared over the previous OA canvas, and the diagram picker read Choose diagram. A fresh snapshot reproduced it. Undo subsequently normalized the SA view; this was a navigation defect, not source corruption. release-semantic-review-navigation-20260906.md owns the focused fix/tests and its later native replay. This binary predates that fix.

The process overview at minimum size is too small for label reading;100% exposes less than one complete column and requires both horizontal and vertical scrolling. Selection works, but these observations do not establish an ergonomic complete process lesson. Reference-label double-click and right-click did not navigate in this trial. Revisit the working-space arrangement and explicit reference navigation while implementing the independently established contextual-chain capability.

Remaining tutorial gates include readable complete process/scenario/reuse work, interface/data inspection, goal/view comparisons, state-action evidence and artifact-target navigation. The deliberate initial diagnostic count is not a claim that a subsequently edited model has the same count. The native NameTake path can create a new semantic-drift notice elsewhere; inspect it rather than treating the status-bar count alone as corruption.

Process9672 was closed cleanly with Alt+F4 before the next rebuild. Runtime logs are .local/native-qa/studio-source6-behavior-context.{stdout,stderr}.log; no recovery or forced stop was part of this tutorial pass. Earlier communication reverse checks on the same binary retain their separate complete source/history evidence.

Follow-up on the navigation-fixed binary

Process3012, .local/native-qa/bin-source6-review-navigation/arcadia-studio.exe, GUI SHA256 19180FEAB9E80C0CD8DB128E281DF353E74BF966ED9DB8D9CD8556A5EEBCD6C5, was exercised at the same minimum1100×700 size. Server and DLL hashes above are unchanged. The copy is .local/native-qa/water-pressure-navigation-working; the OA-only baseline remains preserved separately. The NameTake navigation fix and its three exact first-submission Save/Undo/Redo results are recorded in release-semantic-review-navigation-20260906.md.

• Data & interfaces opened the actual @sa_repair_interface allocation: Valve repair, Synchronous/Accept. Open item selected the Information Operation @sa_repair_operation; its pressure parameter displayed1..1, Value, InOut, kPa, no default. Open named type selected Measured pressure, Real0..600kPa, no default. These fields and navigation were readable at minimum size; this inspection made no model edit.
• Saved view2 displayed functional and boundary exchanges; view3 displayed only the boundary conversation with NameAndItems. View3 properties retained work category Any([]), participant Field contact (@sa_contact_category) and one matching member. View4 displayed System participation in the mission, mission exploitation of Restore capability, and the included Assess capability. View5 selected the actual state machine and opened Behavior States automatically. Overview labels were small; this does not establish full minimum-size diagram readability.
• An invalid view alias invalid view alias 雨 blocked a switch from view3 to view4 with invalid_alias, retaining the exact draft and original canvas. Revert restored sa_service_view and clean state, after which switching succeeded.
• After NameTake, Model checks showed the intended Audit pressure thresholds warning plus a linked-description BothChanged notice on the Confirm trace. The two-count state is explained prose drift, not a claim of the original unedited one-warning condition.
• Clicking the Awaiting repair Entry row selected the real @sa_assess_on_entry relation. Properties showed Entry, source Awaiting repair (@sa_waiting), and target Assess pressure alarm (@sa_assess). Right-click region Fold contents and Save matched the independent full model/all30source fold oracle. Unfold contents and Save matched the full reviewed baseline again. Both saves succeeded first submission. This tests presentation folding without deleting states or typed actions; no fold Undo/Redo claim is made.
• Renamed SA function @sa_assess to Assess incoming pressure alarm through its normal Name/Apply controls. The state entry label updated live. At69% with blank-canvas pan, selecting the row showed the unchanged action identity/name and the full new target name with the same @sa_assess identity. Save matched the independent state-rename oracle: complete Project and all30source files, no identity/metadata/ordering/whitespace normalization. One Undo/Save matched the full review baseline; one Redo/Save matched state-rename again. All three saves succeeded first submission. Home recent-model Open reloaded the saved copy; selecting saved SAview5 and its Entry row displayed entry / Assess incoming pressure alarm and unchanged @sa_assess_on_entry, with clean state.

The checker extension is harness/native-release1-review-check.rs; the executable .local/native-qa/native-release1-state-check.exe is pinned to the source6 core libraries used by this binary. It compiled with rustc -D warnings and reran the original review oracle successfully before use. Independent rename outputs are .local/native-qa/water-pressure-{state-rename-oracle,state-rename-undo-oracle,state-rename-redo-oracle}. The renamed model adds another check, giving three; Undo visibly restored two. The additional check was not individually opened in this trial.

For source6 reproduction, use the core and teaching generator from checkpoint4b6b5fc together with this checker extension. The subsequently edited main workspace now uses source7; compiling its generator against a source6 library is not a supported combination. A later checker guard requires the loaded raw bundle to equal the compiled bundle, refusing cross-version normalization or automatic identity stabilization. That extra guard was added after the native binary was pinned and has no separate execution claim yet. The original run used source6 throughout; its exact folder hashes and source comparisons retain their recorded scope.

The same process subsequently opened Traceability and scrolled past the68trace cards to Development artifacts. Selecting Repair conversation acceptance notes opened @repair_test_evidence: its unchanged owner was Repair request and measured reply (@sa_conversation), relation Verifies, URI evidence/repair-check.md, revision lesson-1, and description explicitly qualified it as a local teaching artifact. These fields were readable at minimum size and the model remained clean. No external file was opened; URIs are maintained references. Finding: there is no artifact jump/filter before the long trace list, so useful evidence access requires excessive scrolling. A focused artifact navigation/filter correction needs new-binary acceptance.

Remaining lesson acceptance concerns complete process/scenario/reuse authoring and efficient artifact navigation. The source7 implementation must receive its own rebuilt native checks; none of these passes transfers automatically to that code.