Sync wiki from project files

Repo-docs-UI-UX-DECISION-LEDGER.md

@@ -1,4 +1,4 @@
-<!-- codex-wiki-sync:0171e3d15ca7bed6e31d7fa2 -->
+<!-- codex-wiki-sync:2442bb7d8cea13b1a8b677e4 -->
 
 > Mirrored from `/mnt/DATA/git/govoplan-core/docs/UI_UX_DECISION_LEDGER.md`.
 > Origin: `repository`.
@@ -68,6 +68,10 @@ Decision: standard wizard steps and names use this baseline:
 Not every wizard needs every step, but flows should use these names and order
 where applicable.
 
+This applies to explicit assisted setup, onboarding, import, preflight, and
+risky multi-step operations. It is not the default shape for ordinary create or
+edit dialogs.
+
 ### DUE-003: Explanation Placement
 
 Decision: richer explanations should use this placement model:
@@ -112,6 +116,18 @@ Decision: convert file connectors first, then mail servers. They share the same
 server/credential/policy model, are high-value, and will prove the reusable
 patterns quickly.
 
+### DUE-007: Adaptive Create/Edit Forms
+
+Decision: ordinary create/edit dialogs should show the full editable state in an
+adaptive form, not force a linear wizard.
+
+- The user chooses a type, provider, credential mode, or policy mode.
+- The dialog immediately adjusts to show only the fields relevant to that state.
+- Editing an existing object uses the same field grouping and layout as creating
+  it, so users can recognize the state they configured.
+- Wizard shells remain available for assisted setup, first-run guidance,
+  imports, discovery-heavy flows, and operational preflight workflows.
+
 ## Implementation Sequence
 
 | Phase | Scope | Output |
@@ -131,8 +147,8 @@ converted or reviewed.
 
 | Surface | Repository | UX State | Next Action |
 | --- | --- | --- | --- |
-| File connector settings | `govoplan-files` | First guided modal slice started: connections and credentials now use shared wizard, review, advanced, and blocker primitives. Central policy card still needs a layered editor. | Finish provider discovery/test-in-flow, then convert policy editing. |
+| File connector settings | `govoplan-files` | First adaptive modal slice started: connections and credentials now use full-state create/edit forms with conditional fields, advanced panels, and blocker primitives. Wizard shell is retained for later assisted setup. Central policy card still needs a layered editor. | Finish provider discovery/test-in-flow, then convert policy editing. |
-| Mail server settings | `govoplan-mail` / `govoplan-core` | Uses the shared server/credential model visually, but create/edit still needs the same guided flow as files. | Migrate to the guided server/credential/policy wizard after files stabilizes. |
+| Mail server settings | `govoplan-mail` / `govoplan-core` | Uses the shared server/credential model visually, but create/edit still needs the same adaptive pattern as files. | Migrate to adaptive server/credential/policy dialogs, with optional assisted wizard later. |
 | Connector policy/effective rows | `govoplan-core`, module UIs | Effective-policy direction exists, but many editors still expose broad option sets. | Put effective value first, move overrides into modal, and explain blocked edits. |
 | Admin module management | `govoplan-admin` | Has preflight concepts, but operational choices are still technical and dense. | Convert install/uninstall/package changes to operator wizards. |
 | Configuration packages | `govoplan-admin` | Catalog/import work exists, but package editing can still drift toward technical fields. | Add guided import/review/problem-list flow. |
@@ -144,8 +160,8 @@ converted or reviewed.
 
 | Surface | Current Risk | Expected Pattern |
 | --- | --- | --- |
-| File connectors | Too many technical fields and unclear setup order. | Provider wizard with discovery/test, credential binding, policy review, advanced protocol panel. |
+| File connectors | Too many technical fields and unclear setup order. | Adaptive create/edit form with optional assisted wizard, discovery/test, credential binding, policy review, and advanced protocol panel. |
-| Mail servers | Similar server/credential/policy concepts risk diverging from files. | Same tree/list and wizard model as file connectors. |
+| Mail servers | Similar server/credential/policy concepts risk diverging from files. | Same tree/list and adaptive server/credential/policy model as file connectors. |
 | Connector credentials | Security-sensitive details can overwhelm users. | Separate credential flow with secret-reference language and test result explanation. |
 | Policy and effective settings | Users need to know why a value is inherited or locked. | Effective row first, source/provenance, local override action, actionable blocked reason. |
 | Module install/uninstall | Operationally risky, currently inherently technical. | Operator wizard with preflight, maintenance, daemon handoff, review, and rollback explanation. |