145 lines
8.8 KiB
Markdown
145 lines
8.8 KiB
Markdown
# Separate-host checkpoint incorporated 2026-09-10
|
|
|
|
The following sections are preserved from Codex-956atf commit 01bb52a during integration on Codex-9e8r6t. Paths, process handles, toolchains and validation statements describe that separate host at that commit; they are not current local evidence. See STATE.md for current local status.
|
|
|
|
Follow-up `b6b76ef` fixes the independently identified optional-value constructor
|
|
cache collision and expands stored-history coverage from ten to twelve tests.
|
|
Its host ledger records an anonymous fetch of our palette `7d1df4f`, an earlier
|
|
full-platform dependency fetch stopped after network timeouts, and a cold Windows
|
|
desktop compilation under its own exec handle 51036. That handle is not local.
|
|
Neither their source review nor bundle transfer establishes a test pass.
|
|
The follow-up bundle includes both commits from prerequisite `1797516`, is
|
|
60,757 bytes, and has SHA256
|
|
`2CC21D7B1B8D9F5895C7239F5C37615C4167E732A14EA5480CBD4ECB99CAE45B`.
|
|
Root verified the decoded bundle and is merging the correction separately from
|
|
the immutable earlier 618-test artifact. Original host-specific history follows.
|
|
|
|
## STATE
|
|
|
|
The renewed user request is preserved in `PROJECT_GOAL.md`. Root is integrating
|
|
the first release, prioritizing direct diagram authoring and behavior/scenario
|
|
usability. The checkout began clean at `1797516` on `codex/release1-continuation`.
|
|
Gitea issue #1 and Wiki Home were read; ownership and progress are coordinated there.
|
|
|
|
- Root owns integration, serialized builds, native Computer Use and these ledgers.
|
|
`palette_repair` owns architecture authoring and `diagram.rs`; `behavior_audit`
|
|
and `release_audit` independently inspect ergonomics and release coverage.
|
|
- The recorded palette compilation errors have local corrections pending a fresh
|
|
build. Earlier 584-test evidence does not cover those corrections.
|
|
- This checkout began without the historical `.local` toolchain/cache/packages.
|
|
Project-local Rust/Cargo 1.98.1 GNU/LLVM and verified LLVM-MinGW 20260908
|
|
(clang 23.1.1) are installed. Locked dependencies are being fetched.
|
|
Host: four logical processors, 8 GiB RAM; builds remain serialized.
|
|
- Computer Use initialized successfully. The renewed request authorizes native
|
|
evaluation; old session Escape holds and process IDs are historical. No Arcadia
|
|
or Capella window is currently running.
|
|
- WSL lists no installed distribution. Linux runtime/build acceptance remains an
|
|
open gate; no historical denied guest workaround is being retried.
|
|
|
|
**Current branch is `codex/behavior-authoring-20260910`.** A distinct Gitea user
|
|
`Codex-9e8r6t` is running another root/team on a separate environment with the old
|
|
build cache. Our identity is **Codex-956atf**. Gitea #25 and #38 acknowledge the
|
|
scope split: their palette/platform/package and subsequent scenario layout work;
|
|
our process/scenario adapters and typed-history work. We will publish a clearly
|
|
untested coherent snapshot on this distinct branch for their warm-cache checks.
|
|
No shared branch-tip push or merge has occurred here.
|
|
Their reports/results must not be claimed as local validation or overwritten.
|
|
|
|
Implemented locally, awaiting compilation:
|
|
|
|
- Palette compile repair, retained inline name after rejected stale Submit,
|
|
nonfinite click rejection and rename/allocation/history regressions.
|
|
- One interactive process renderer with presentation-only inferred ordered
|
|
paths; first editing batch preserves adjacency atomically. Independent source
|
|
review found no confirmed defect. Root added 3+ step/before-first insertion
|
|
and incompatible imported conversion tests after the reviewer hit model capacity.
|
|
- Scenario Action/State/Reuse/empty Fragment tools capture clicked operand/slot
|
|
and optional lifeline. Pointer-to-App, recovery, stale-event and history tests
|
|
are written. A bounded exact caller/use return path and scoped mounted-scroll
|
|
restoration are implemented with regressions, also untested.
|
|
- Advanced typed stored-history editor uses existing OpenAPI type descriptors;
|
|
ten focused tests cover typed selectors, historical IDs, invalid raw input,
|
|
recovery and source/history. Core validation remains authoritative.
|
|
- Normative catalogs now include ExchangeCategory, ContextualLink and both
|
|
Exchange trace pairs. Manual trace help and scope source version corrected;
|
|
strict Docutils 0.22.2 HTML regeneration passed.
|
|
|
|
Reference evidence: actual Capella 7.1 scenario/lifeline/LOOP creation and saved
|
|
XML are recorded in `release-capella-scenario-benchmark-20260910.md`; the isolated
|
|
Capella process closed normally and is absent. This is not Studio acceptance.
|
|
|
|
Toolchain bootstrap exec session **20812** completed successfully: verified
|
|
LLVM-MinGW 20260908 ZIP SHA256
|
|
`1bcf74d06b724aeecaa6412ca85f5b26fb1da770e7cdcefa9263c9c5c3ad34b6`, extracted
|
|
successfully; stable **1.98.1** GNU/LLVM, rustfmt and Clippy installed.
|
|
`.local/toolchain/env.ps1` configures task-local Cargo/Rustup/PATH and one build
|
|
job. Locked dependency fetch is local exec session **13108**. No build/test pass
|
|
is established; the target cache is still cold.
|
|
|
|
The coherent candidate passed `cargo fmt --all` and `git diff --check`. It is
|
|
published as an **UNTESTED integration snapshot** so the other host can use its
|
|
warm build cache; publication is not acceptance. Their broader architecture
|
|
palette/Escape repair should be reconciled with our overlapping compile/stale
|
|
repairs while retaining the additional invariant tests. Their measured minimum
|
|
scenario canvas is too small; they own the subsequent layout implementation.
|
|
|
|
Next: focused `architecture_authoring_tests`,
|
|
`behavior::topology`, `direct_clicked`, caller-navigation and `history_fields::tests`,
|
|
then full relevant gates and a fresh native binary. Root owns all Cargo on this
|
|
host. Worker output or tests existing in source are not passes.
|
|
|
|
Gitea Actions run16 is queued for both ubuntu-latest and windows-latest with no
|
|
started steps, as are older listed runs. No usable current Linux runner result
|
|
is established and no duplicate dispatch was made. Progress is concrete;
|
|
release acceptance remains incomplete. Older checkpoint paragraphs below retain
|
|
their original revision scope.
|
|
|
|
## PLAN
|
|
|
|
## Active execution — 2026-09-10
|
|
|
|
1. Restore a reproducible local toolchain; repair the interrupted compact palette;
|
|
verify focused history/draft/placement regressions and the actual native workflow.
|
|
2. Independently reassess current behavior/scenario ergonomics and OA/SA semantic,
|
|
source/API and documentation completeness. Resolve verified high-impact gaps
|
|
with bounded changes and cross-representation acceptance criteria.
|
|
3. Complete realistic graphical OA/SA teaching, transition, behavior, recovery and
|
|
hosted workflows. Exercise minimum and wide layouts, rejected edits and history.
|
|
4. Run current Windows/Linux automated and native acceptance, fresh independent
|
|
end-state reviews, optimized builds and package verification. Publish accurate
|
|
build/run evidence and handoff only when the original release criteria hold.
|
|
|
|
This ordering supersedes historical stopped-session next actions below. Preserve
|
|
their scoped evidence; no test or runtime result transfers to a new binary without
|
|
verification. Root holds the serialized build/native lease; Gitea #1 tracks workers.
|
|
|
|
## TASK_LEDGER
|
|
|
|
## 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.
|