sorokin.oleg.edu/ARCADIA-Studio
1
0
Fork 0
Code Issues 37 Pull Requests 2 Packages Projects Releases 9 Wiki Activity

Codex-ytr83r: record focused lifecycle pass and current native gates

Codex-ytr83r
2026-09-11 15:18:28 +00:00
parent d1f1a09595
commit d5f06dae34
1 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ScenarioLifetimeRendering.md
+10 -6
@@ -1,13 +1,17 @@
# Scenario lifetime presentation
Codex-ytr83r /root, 2026-09-11. Source checkpoint `52f6e17` is published on `codex/release1-ytr83r`. This is a reviewed implementation checkpoint; current-host compilation and native acceptance are still pending. It is not a release.
Codex-ytr83r /root, 2026-09-11. Current implementation is published at `29084050a7c020e0fb488be37c6e1ab235769cc0` on `codex/release1-ytr83r`. The current-host focused lifecycle gate passed **22 tests, zero failures** at 15:10:20 UTC. Full desktop regression and native acceptance remain pending; this is not a release.
The semantic Project, commands, source format and REST records are unchanged. `behavior/scenario_lifecycle.rs` derives local structural lifetimes; `scenario_lifecycle/render.rs` maps them onto actual Scene geometry. Neutral lane headers and dotted editing guides identify lifelines, including incomplete representations. Stronger spines and activation bars exist only in the exact scope's definite Alive intervals. Create capsules and Delete crosses belong to the original message-occurrence IDs; neutral headers/guides belong to lifelines.
The semantic Project, commands, source format and REST records are unchanged. `behavior/scenario_lifecycle.rs` derives local structural lifetimes; `behavior/scenario_lifecycle/render.rs` maps them onto actual Scene geometry. Neutral lane headers and dotted editing guides identify lifelines, including incomplete representations. Stronger spines and activation bars exist only in the exact scope's definite Alive intervals. Create capsules and Delete crosses belong to original message-occurrence IDs; neutral headers and guides belong to lifelines.
Alternatives/optional/loop/parallel operands are independent. Lifecycle-bearing fragments leave conservative unresolved continuation, shown with `?`; the existing unanswered Call cue remains `…`. Referenced scenarios are opaque in the caller. Rendering does not infer callee creation/deletion, fabricate a Reply or write the model.
Alternative, optional, loop and parallel operands are independent. Lifecycle-bearing fragments leave conservative unresolved continuation, shown with `?`; the existing unanswered Call cue remains `…`. Referenced scenarios are opaque in the caller. Rendering does not infer called creation/deletion, fabricate a Reply or write the model.
Root lifetime uses the full visible extent (85..height−20), independently of insertion-slot bounds. Empty operands retain their visible allowance. Self-message endpoints, markers and recorded rows align. Exact marker/header/label shapes precede a joint nearest-distance comparison across message strokes and marker shapes under the same screen-pixel tolerance; persistent UUIDs break ties. This avoids neighboring lifecycle targets stealing clicks at minimum Fit.
Root lifetime uses the full visible extent (85 through height minus 20), independently of insertion-slot bounds. Empty operands retain their visible allowance. Self-message endpoints, markers and recorded rows align. Exact marker/header/label shapes precede a joint nearest-distance comparison across message strokes and marker shapes under the same screen-pixel tolerance; persistent UUIDs break ties. This avoids neighboring lifecycle targets stealing clicks at minimum Fit.
Independent review corrected structural-loop wording in language section4.3, self-caption overlap, and two minimum-Fit selection counterexamples. Language section8.1 and built-in scenario guide describe the user-visible meaning. The renderer report records alternatives, findings and ten real-Scene tests; the separate core-only `harness/lifecycle-native-contract.rs` defines twelve fixed-ID OA/SA native scenarios, complete Project/source predictions and explicit retained-file Undo rules. These evaluators still require execution on this host.
Independent review corrected structural-loop wording, self-caption overlap and two minimum-Fit selection counterexamples. A later typography review led to a clipped single-line Create label inside its capsule. The clip is transformed into screen coordinates and intersected with the viewport; the child frame receives the same uniform scale. Future camera changes must update both transforms. Wide Latin/CJK and combining/emoji fixtures are admitted, but their actual native appearance has not yet been accepted.
Next gates: finish current core tests, compile/admit the independent oracle before native output, run lifecycle/direct-canvas and full desktop tests, strict checks, then minimum/wide native selection and Save/Undo/Redo/reopen with exact full-source comparison. Root owns Cargo/native/release acceptance. Other hosts retain staged-source, CLI, chooser and analysis/library implementation ownership.
The first completed desktop compilation failed on two installed-Iced API details: ambiguous `Size` in tests and a floating-point value for integer `LineDash.offset`. Commit 2908405 corrects only those types. The subsequent 22-test gate covers ten pure lifetime cases, ten real-Scene cases and two clipping geometry cases. Exact terminal logs, timestamps and input hashes are in `harness/experiments/lifecycle-native-ytr83r-20260911/`. Earlier failed/interrupted attempts remain separately attributed.
Current core all-targets passed 433 tests with one intentionally ignored scaling probe; that probe separately passed. The independent core-only `harness/lifecycle-native-contract.rs` compiled and passed admission, self-check and complete baseline/name-only predictions. It defines twelve fixed-ID OA/SA scenarios, exact Project/reachable-source/physical-file comparisons and explicit retained-file Undo rules. These oracle preparation passes do not establish native behavior.
Next gates: complete full desktop tests and strict checks, build and launch the actual application, exercise minimum/wide selection and Unicode clipping, then Save/Undo/Redo/reopen with exact full-source comparison. Root owns Cargo/native/release acceptance. Other hosts retain staged-source, CLI, chooser and analysis/library implementation ownership. Linux host/setup evidence is tracked separately in [LinuxHostYtr83r20260911](LinuxHostYtr83r20260911). The full user goal and issues 1/2 remain open.