Record updated usability objective and integration evidence
This commit is contained in:
@@ -2,6 +2,23 @@
|
||||
|
||||
## Active continuation — 2026-09-10
|
||||
|
||||
Latest checkpoint: read updated objective attachment `578cf63e-08b7-411f-a01e-20416441d5e2`
|
||||
fully and updated `PROJECT_GOAL.md`. Its emphasis on Capella-level useful modeling
|
||||
and usability keeps behavior authoring central. Packaging is committed `b98f135`;
|
||||
current product/release acceptance remains incomplete. First merged desktop
|
||||
artifact finished **615/618 passed**, with three concrete failures assigned;
|
||||
the previous running status below is historical. Full evidence and diagnosis:
|
||||
`release-integrated-gates-20260910.md`.
|
||||
|
||||
Current leases: behavior_audit owns scenario workspace/B3 corrections and sole
|
||||
Cargo compilation; release_audit now owns only new behavior/creation.rs/tests
|
||||
pending coordinated shared wiring, with packaging frozen; palette_finish owns
|
||||
exclusive native input for a bounded Capella behavior-creation study. Root does
|
||||
not operate native UI until that lease returns. Candidate 2 closed cleanly after
|
||||
F2 equality and saved Actor checkpoint; no process 648 remains. Root owns merges,
|
||||
specification checks and ledgers. Other host owns remaining typed-history seed
|
||||
fix, standalone scenario lifetimes and its own native scenario contract.
|
||||
|
||||
Integration update (2026-09-10): local branch is `codex/release1-9e8r6t`.
|
||||
Palette `7d1df4f` is published separately. Received Codex-956atf's exact Git
|
||||
bundle (57,658 bytes, SHA256 `85A38B00207036DCB8DB24ED4A7E80B2BE670275EEB7B00413D36153322ADA5D`),
|
||||
|
||||
@@ -1,5 +1,29 @@
|
||||
# Task Ledger — first release
|
||||
|
||||
## Updated objective and current strategy — 2026-09-10
|
||||
|
||||
Given: the latest authoritative request is
|
||||
`578cf63e-08b7-411f-a01e-20416441d5e2/goal-objective.md`, copied into
|
||||
`PROJECT_GOAL.md`. It preserves complete OA/SA, parity, API, traceability,
|
||||
cross-platform and review requirements, and explicitly emphasizes that current
|
||||
usability/functionality remains below Capella. The next changes must address
|
||||
actual engineer workflows; passing narrow technical checks is insufficient.
|
||||
|
||||
Verified: palette F2/Save/Undo/Redo and the exact Entity source oracle passed
|
||||
on candidate 2. Named Actor placement is saved; full basic workflow is pending.
|
||||
Merged desktop ran 618 tests: 615 passed and 3 failed, with concrete navigation
|
||||
and history-seed causes now assigned. Schema fixtures and strict reST rendering
|
||||
passed. Packaging is committed with independent review and exact notice bytes.
|
||||
See `release-integrated-gates-20260910.md` for scope and failures.
|
||||
|
||||
Strategy: finish the actual remaining-height scenario workspace, repair its
|
||||
navigation and typed-history failures, and make starting a named behavior local
|
||||
with explicit viewpoint/owner choices. An independent native Capella study
|
||||
informs that workflow while the creation worker implements its isolated module.
|
||||
Root integrates and then evaluates realistic current-build tasks. Assumption:
|
||||
these changes will reduce navigation/draft detours; native acceptance must prove
|
||||
that. Linux runtime and broader parity/release gates remain unresolved.
|
||||
|
||||
**18:10 UTC checkpoint, 2026-09-10:** palette repair candidate 2 passes focused
|
||||
tests/build/format/strict Clippy and native recovered-draft Escape/save plus the
|
||||
complete Entity source oracle. The user stopped Computer Use; native verification
|
||||
|
||||
@@ -0,0 +1,61 @@
|
||||
# Integrated checks — 2026-09-10
|
||||
|
||||
Root identity: Codex-9e8r6t. These are intermediate results, not release acceptance.
|
||||
|
||||
## First merged desktop artifact
|
||||
|
||||
Source: merge `057eddd` plus the checkpoint autofocus patch later committed in
|
||||
`31b7dc3`. The Rust sources were frozen throughout compilation. After the 13
|
||||
checkpoint tests passed, root copied the built test executable and matching
|
||||
libunwind into `.local/integration-20260910/tests-057eddd/`; later source edits
|
||||
could not change this running artifact. SHA256:
|
||||
`D504C59BC2A5853F4FBE54A9DFA841DA0AC8DD2475342E45A91DBAA6533372B4`.
|
||||
The exact additional source patch and execution metadata are retained there.
|
||||
|
||||
Full inventory execution ran from 18:21:36 to 18:29:26 UTC, 469.21 test seconds,
|
||||
and exited 101: **615 passed, 3 failed, 0 ignored**. Failures:
|
||||
|
||||
- Scenario return after rename/deletion/retarget: selected identity differed
|
||||
from the asserted caller/use or still-open scenario. The layout worker found
|
||||
that generic retarget commands can leave a cross-owner selection, and a
|
||||
same-ID selection shortcut can skip changing the active scenario on successful
|
||||
Back. A narrow correction and stronger active-scenario assertion are in the
|
||||
next candidate; they have not yet passed.
|
||||
- Both exhaustive stored-history choice and exact-string tests failed with
|
||||
UUID parsing of `NotApplicable`. Root found `seed()` using permissive shape
|
||||
matching to identify that enum, so nullable UUID/string branches receive the
|
||||
literal instead of null. The other host's forms owner is correcting explicit
|
||||
enum admission while preserving raw invalid-input editing.
|
||||
|
||||
This artifact predates nullable constructor-cache fix `b6b76ef`, merged locally
|
||||
in `a70de55`, and the later scenario workspace. That cache fix is distinct from
|
||||
the seed defect. Gitea issue 1 comments 68–69 carry the failures and diagnosis.
|
||||
No assertions were weakened or failed checks reported as acceptance.
|
||||
|
||||
## Specification check
|
||||
|
||||
On merged source, `semantic_schema.py --check --validate` passed **72 fixtures**,
|
||||
**204 schemas**, **14 families** and **90 scalar leaves** using the retained
|
||||
local jsonschema dependency directory. The first invocation with the bundled
|
||||
Python alone lacked jsonschema; setting its task-local PYTHONPATH resolved that
|
||||
environment issue without changing the script or dependencies.
|
||||
|
||||
Docutils 0.22.2 rendered both `docs/language.rst` and `docs/api.rst` under
|
||||
`--strict`, with no warnings. API HTML was byte-identical. Language HTML was
|
||||
identical after newline normalization: the Git checkout has LF and the Windows
|
||||
renderer produced 2,776 CRLF lines. The rendered files remain under the local
|
||||
integration directory. This establishes specification/render synchronization,
|
||||
not full graphical/textual/REST runtime parity.
|
||||
|
||||
## Packaging integration
|
||||
|
||||
Commit `b98f135` includes the independently reviewed packaging changes. Root
|
||||
explicitly renormalized the two Fira notices after applying their exact `-text`
|
||||
attributes. The three upstream notice exceptions retain intentional original
|
||||
whitespace; all other staged files passed the whitespace check. Raw and staged
|
||||
bytes of all three checksum-bound notices were independently compared exactly
|
||||
in `.local/packaging-20260910/root-staged-verbatim-notices.json`. The author's
|
||||
separate alternate-index check covers all 25 referenced notice files through
|
||||
checkout. Native Linux, a real Linux desktop/server archive, container execution
|
||||
and final optimized packages remain open gates. See the packaging reports for
|
||||
the explicit synthetic/full-graph versus real-Windows evidence distinction.
|
||||
@@ -139,3 +139,30 @@ that state; explicit refocus and a second type_text produced the intended name.
|
||||
The cause is not established, so this is not recorded as a proven application
|
||||
typing defect or as uninterrupted first-attempt typing. Applying, history and
|
||||
source persistence were tested only after the correct text was visible.
|
||||
|
||||
## Actor continuation and clean close
|
||||
|
||||
Continued the ordinary root-creation sequence at 1442×932 outer size. Four minus
|
||||
steps changed the 150% overview to approximately 72%; camera translation and
|
||||
the existing Entity's world placement remained stable. Compact Actor tool,
|
||||
blank point (817,440), `Control centre`, Enter created the Actor at that point.
|
||||
The actual placement property values were approximately (680.1408,120.8218),
|
||||
consistent with the fractional zoom. As the independent contract requires,
|
||||
the operator explicitly set X=680 and Y=120 in Placement properties and applied.
|
||||
Ctrl+S saved successfully, and `checkpoint-actor` preserves the complete bundle.
|
||||
Its Actor ID is `b3cd865b-b1df-43b4-9396-2e4aaec65367`, placement ID
|
||||
`ee9a090c-b322-4e37-b6d4-40e2a1af725f`. The complete `basic` oracle is still
|
||||
pending the Activity, existing placement, allocation, Interaction and rename.
|
||||
No complete Actor-only model oracle is claimed from the property inspection.
|
||||
|
||||
One attempted Y replacement appended text after a multi-click selection. The
|
||||
operator observed it, explicitly selected all and cleared, then entered `120`;
|
||||
only the visibly correct X/Y values were applied. User input interrupted one
|
||||
typing attempt; root reobserved before continuing. These automation observations
|
||||
remain distinct from a demonstrated application defect.
|
||||
|
||||
The candidate closed through its title-bar button with all changes saved.
|
||||
The subsequent process query found process 648 absent; stderr was empty. Root
|
||||
transferred the exclusive native-input lease to the independent Capella creation
|
||||
workflow investigator. A future current-build session can resume from the whole
|
||||
`checkpoint-actor` directory without redoing earlier accepted fixture creation.
|
||||
|
||||
Reference in New Issue
Block a user