Checkpoint source 7 workflows and in-progress diagram authoring redesign

Preserve current core, source, REST, desktop, recovery, documentation and validation work, including AGENTS.md and the development summary. This is a work-in-progress checkpoint: the new compact palette has outstanding compilation errors and native acceptance; earlier passing gates retain their documented scope.
2026-09-10 10:06:55 -07:00
parent 4b6b5fc197
commit e2ecfea69b
162 changed files with 17595 additions and 926 deletions
@@ -211,6 +211,17 @@ Decision: retain same-layer admission for ordinary diagrams, but allow both-laye

 Alternatives rejected: filtering every view by its labelled layer loses existing Traceability content; ignoring layer validation everywhere hides mistaken references; serializing temporary GUI filters breaks source/API parity. Revisit if native workflows or cross-layer regression evidence exposes ambiguity. Current implementation is pending integrated tests and native acceptance, not an established release result.

+## Basic canvas authoring — 2026-09-07
+
+The user rejected the large horizontal creation row. Actual installed Capella 7.1
+inspection supports a compact contextual side palette and direct label editing.
+Select an explicitly expandable palette, tool → point → inline name creation, F2
+rename and explicit participant allocation. Keep draft phases from changing canvas
+geometry; retain atomic commands and guarded recovery. Context-only creation hides
+the primary action, and a permanently expanded catalogue repeats the original
+problem. [Evidence, alternatives and acceptance criteria](release-capella-basic-editing-20260907.md).
+This is a selected design under implementation, not a native acceptance claim.
+
 ## Behavior transition destination context — 2026-09-06

 Native reverse scenario Apply selected a dependency and inserted five overlapping behavior placements into an unrelated architecture view. Core transition correctness did not make that presentation useful. Select the counterpart of the explicit request root and resolve its nearest scenario/process/chain/state owner. Without an explicit destination diagram, keep the exact core candidate and open Behavior; preserve unrelated architecture views. Retain ordinary architecture transition placement and honor explicit diagram choices.