Complete terminal management workflow

docs/PROJECT_LAYOUT.md

@@ -1,12 +1,19 @@
 # Project Layout
 
-Read this document when creating or reorganizing modules. The paths below are planned until implemented.
+Read this document when creating or reorganizing modules. The layout below
+reflects the current package; sections marked planned describe later test and
+integration work only.
 
 ## Target project layout
 
-Start with one Cargo package containing a binary (`src/main.rs`) and a library (`src/lib.rs`). Keep startup, argument handling, and process exit in `main.rs`; place testable application logic in library modules. A library target does not require publishing a separate library package. Introduce a workspace only when independently reusable or separately built components justify it.
+The repository has one Cargo package with a binary (`src/main.rs`) and a
+library (`src/lib.rs`). Startup and process exit remain in `main.rs`; testable
+application logic and the management TUI are library modules. A library target
+does not require publishing a separate library package. Introduce a workspace
+only when independently reusable or separately built components justify it.
 
-The following is the intended layout, not a claim that these files already exist. Create modules and directories as implementation requires them; do not generate empty scaffolding for the entire tree.
+Implemented modules include the following. Add modules as implementation
+requires them; do not generate empty scaffolding for future integration work.
 
 ```text
 Cargo.toml
@@ -36,12 +43,14 @@ src/
   tui/
     state.rs               # Screen state and navigation
     events.rs              # Keyboard and background events
+    forms.rs               # Short-lived forms and secret owners
     render.rs              # Rendering
     terminal.rs            # Terminal setup and cleanup
 tests/
   config_preservation.rs   # Untouched server configuration remains identical
   commit_restore.rs        # Persistence, backups, restore, runtime isolation
   client_lifecycle.rs      # Import, creation, delivery, deletion, state transitions
+  tui_workflow.rs          # Synthetic worker-level TUI workflows
   fixtures/                # Synthetic configuration and archive inputs
   support/
     mod.rs                 # Shared test adapters and helpers