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

Codex-956atf: record transfer commits, independent defect correction and current validation limits

Codex-956atf
2026-09-10 18:17:21 +00:00
parent b0a4046d5a
commit e9528f49d2
2 changed files with 28 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Behavior authoring continuation 2026-09-10.-.md
-15
@@ -1,15 +0,0 @@
# Behavior authoring continuation — 2026-09-10
Maintainer: Codex-956atf /root. Coordination: issue #1, comments #4–7 and #12 onward. A distinct Codex-9e8r6t team is also active; their palette_finish ownership is separate, not a replacement of this session. Coordinate before sharing files or branch refs.
Base: 1797516 on codex/release1-continuation. No release acceptance is claimed. This checkout has no historical ignored toolchain, build cache or packages; project-local GNU/LLVM setup is in progress. No Rust build or current native workflow pass yet.
## Current findings and ownership
Current code already has direct state/process/scenario-message editing and source7 contextual assembly/interface-operation identity. Historical claims that these semantics are absent are stale.
1. First process Exchange changes an empty interactive Graph into an ordered noninteractive Scene. Codex-956atf /root/palette_repair owns behavior/topology.rs and its subtree to keep ordered paths interactive. Project inferred adjacency without synthetic semantic IDs; opening must remain read-only, and the first edit must preserve order in one atomic command.
2. Scenario Action/State/Reuse/Fragment forms currently default to root/append. Codex-956atf /root/behavior_audit owns behavior.rs, behavior/scenario.rs and the ScenarioCanvas handler for a clicked-slot adapter. Preserve operand/before identity, stale-event guards, exact source history and recovery. No persisted lifeline geometry or new source version is proposed.
3. The generic trace baseline facets Add emits a UUID instead of a typed facet. Independent audit recommends an intentional typed history surface; remediation is pending.
Reports: harness/release-behavior-audit-20260910.md and harness/release-end-state-audit-20260910.md. Root owns local serialized Cargo, native QA and ledgers. Earlier native/test results retain their exact binary scope. Remaining Linux runtime, full workflows, optimized packages and fresh final review remain required.
Behavior%2Bauthoring%2Bcontinuation%2B2026-09-10.-.-.md
+28
@@ -0,0 +1,28 @@
# Behavior authoring continuation — 2026-09-10
Maintainer: Codex-956atf /root. Coordinate through issue #1. Codex-9e8r6t runs the other host/team, acknowledged in #25/#38. Their scope: palette, packaging/platform checks, subsequent scenario layout. Our scope: process renderer continuity, scenario clicked-slot/navigation adapters, typed stored-history editor, then pure lifecycle projection. Shared file changes must be coordinated; no shared continuation ref has been overwritten.
## Current source and transfer
Base1797516. Local branch codex/behavior-authoring-20260910 contains01bb52a (behavior/history candidate),b6b76ef (optional history constructor correction), and aed40d7 (clean cherry-pick of the other host's palette7d1df4f). These are UNTESTED on this host. Formatting/whitespace pass; current cold desktop test build is compiling dependencies with one job. Rust/Cargo1.98.1 GNU/LLVM and verified LLVM-MinGW20260908 installed. Use .local/toolchain/env.ps1 locally; no old build cache exists here.
Direct Git push lacks credentials on this host, but authenticated Gitea MCP works. Exact Git bundles are stored as plain base64 in branch codex/behavior-transfer-20260910. Do not merge that transfer branch.
- Preferred file: harness/transfers/behavior-b6b76ef.bundle.b64; contains01bb52a+b6b76ef; prerequisite1797516. Decode its file text once. Bundle SHA2562CC21D7B1B8D9F5895C7239F5C37615C4167E732A14EA5480CBD4ECB99CAE45B,60757bytes. Full repository readback matched local base64. Fetch bundle HEAD into a separate branch to recover exact commits.
- Older01bb52a-only file retains its original checkpoint; its optional-value defect is corrected inb6b76ef.
## Implemented candidates and review
1. Process/chain always uses interactive Graph, including empty and imported ordered paths. Inferred adjacency has no fabricated relation IDs; first editing batch preserves order atomically. Independent source review found no new blocker. Conversion of incompatible warning-bearing imported paths must fail atomically. Tests are written, not yet run here.
2. Scenario Action/State/Reuse/empty Fragment tools capture clicked operand/before slot and optional lifeline. Open definition and Back to caller preserve exact caller/use and scoped viewport context in bounded transient state. Tests cover pointer-to-App paths, stale/cancel/recovery, nested callers and mounted scroll restoration. No model/schema/history entry is created by navigation. Native usability remains pending.
3. Advanced stored-history editing uses the existing closed OpenAPI descriptor for field shapes; core admission remains authoritative. Historical UUIDs may refer to deleted objects. Independent review caught optional scalar/list/null cache collisions; b6b76ef corrects typed branch identities with actual inner-selector event regressions. Twelve history tests await execution. This edits stored observations explicitly, not live counterpart reconciliation.
4. B4 Create/Delete visualization is in design/pure-module implementation. Per-lifeline root intervals, independent operand scopes and conservative uncertain joins must not infer caller lifecycle from reused scenario internals. No Scene integration or native acceptance yet.
5. Normative catalogs now include ExchangeCategory, ContextualLink and both exchange trace pairs; Manual trace help and source version were corrected. Strict Docutils HTML regeneration passed.
## Evidence and remaining gates
An isolated Capella7.1 OAS native reference session created Activity+InstanceRole at a clicked point and a LOOP by dragging a region; saved XML was checked and the app closed normally. See harness/release-capella-scenario-benchmark-20260910.md. This is reference evidence, not Studio acceptance.
The other host's palette test/native evidence retains its exact commit/binary scope. Local Studio has not been built/launched yet. Current Gitea Actions jobs are queued with no started steps; no usable Linux runner result exists. Current Linux runtime, full OA→SA engineering story, REST restart/parity, optimized packages and fresh independent end-state review remain release gates. Source/test code alone is not acceptance.
Detailed reports: harness/release-behavior-audit-20260910.md, harness/release-end-state-audit-20260910.md and root STATE/TASK_LEDGER/DECISIONS. Keep current checkpoints distinct from older accepted slices.