Improve behavior authoring and typed trace history (untested checkpoint)
Rust checks / check (ubuntu-latest) (push) Canceled after 0s
Rust checks / check (windows-latest) (push) Canceled after 0s

This commit is contained in:
Codex
2026-09-10 11:07:07 -07:00
parent 1797516f46
commit 01bb52a76d
25 changed files with 4078 additions and 171 deletions
+28
View File
@@ -1,5 +1,33 @@
# Task Ledger — first release
## Current knowledge — 2026-09-10
Given: the renewed objective in `PROJECT_GOAL.md` requires a feature-complete,
usable OA/SA first release and prioritizes direct behavior/scenario authoring.
Graphical/source/REST parity, explicit reST semantics, traceability, offline
guidance, Windows/Linux acceptance and independent review remain required.
Older scope deferrals must be checked against this request.
Verified: the checkout began clean at `1797516`; Gitea contains one active
continuation issue and no open PR. Current code includes direct behavior editors,
so old blanket descriptions of static diagrams need workflow-level reassessment.
The machine began without the ignored historical toolchain/cache/distributions.
Local Rust/Cargo 1.98.1 and verified LLVM-MinGW are now installed; dependency
fetch is pending and no current binary has been built. Native Computer Use is
available. Isolated Capella activity/lifeline/LOOP creation was saved and checked;
no Arcadia window is running. Candidate B1/B2/B3 and F1 edits are source-complete,
formatted and whitespace-clean, but have no fresh compile/test/runtime pass.
Assumption: the selected compact architecture palette remains a promising design,
pending real authoring evidence. Decision: repair and evaluate it before further
redesign. Parallel independent audits identify current behavior and semantic gaps
instead of reimplementing integrated work.
Open questions: which remaining menu-only behavior operations prevent a coherent
direct workflow; which first-release semantic/parity gaps remain; and how to
complete current Linux runtime acceptance. Root owns integration and native
control; worker ownership is disjoint. See `STATE.md` and Gitea #1.
**Superseding user direction:** large horizontal creation buttons were rejected as intrusive and unprofessional. The user explicitly authorized consulting the installed Capella; that consultation has resumed and established actual compact palette, inline rename and explicit activity-allocation behavior. See [Capella 7.1 evidence and selected redesign](release-capella-basic-editing-20260907.md). The current candidate replaces creation/connection rows with one compact expandable palette and an in-place name editor. Native acceptance of the redesigned executable is pending; compactness is not assumed to prove usability. The earlier Escape hold and proposed toolbar-only correction below are superseded.
**Latest evidence:** basic editing full desktop584/584, bins, formatting and strictClippy passed. Native named Entity creation works at100%, but changing pending-toolbar height moves the screen placement22px. User Escape stopped the attempted Undo; native checks are paused again. Code-only toolbar correction proceeds. [Current findings](release-basic-editing-reset-20260907.md). The previous goal turn made concrete progress through implementation, integration gates and a native-discovered defect; this is not a no-progress blocker turn.