konrad/NeitzelFXDesigner
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Connect minimal hosts to snapshots, target workers and shared Kit editing

Browse Source
This commit is contained in:
konrad
2026-11-12 11:07:45 +01:00
parent 28c1e47c95
commit 7db7218a6e
52 changed files with 4236 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/initial-project-contract.md
+2 -2
View File
@@ -84,7 +84,7 @@ Local settings hold installed JDK mappings, absolute machine paths and remembere
## Build and snapshot contract
Work package 5 now implements the shared [Build and Refresh workflow](build-and-refresh.md), including its validation and explicitly bounded input closure. Worker activation and UI wiring remain work package 7.
Work package 5 now implements the shared [Build and Refresh workflow](build-and-refresh.md), including its validation and explicitly bounded input closure. Worker activation and UI wiring are implemented in the [first connected workflow](first-connected-workflow.md).
1. Resolve the selected context and required reactor dependencies, including configured preview sources. Prefer the Maven wrapper; expose the plan, command/output and cancellation. Avoid unrelated applications unless dependency resolution requires them.
2. Identify known unsaved Java, Maven and designer-configuration inputs affecting the build. Offer **Save affected files and build** or **Cancel**, listing the affected files. Do not implicitly build older disk versions. Account for IDE autosave; another process's unsaved buffers are not observable.
@@ -133,4 +133,4 @@ Accept the first milestone only when both minimal hosts use the same core/UI/fix
- Listing examples performs no Model/Controller construction; selecting an example produces fresh state and honors readiness/cleanup.
- Console output cannot corrupt worker messages; owner death, cancellation and timeout terminate workers.
These are acceptance requirements, not newly passed tests. Broader product behavior remains governed by the existing roadmap.
These acceptance requirements are covered by the combined work-package suites; the [connected-workflow report](first-connected-workflow.md) records the qualified platforms and bounded UI scope. Broader product behavior remains governed by the existing roadmap.