Update project host model implementation status

Co-authored-by: Orca <help@stably.ai>

notes/project-first-host-model-change-inventory.md

@@ -329,8 +329,9 @@ Needs:
 - bulk setup when adding a new host
 - future cloud provisioning hook
 
-Current branch status: existing-folder API plumbing is partially implemented;
-full user-facing setup UI is not complete.
+Current branch status: existing-folder setup is partially implemented through
+API/CLI plumbing and a project settings import form for known local, SSH, and
+active runtime hosts. Clone, provisioning, and bulk setup are not complete.
 
 ### 6. Sidebar Row Model
 
@@ -359,8 +360,9 @@ Needs:
 - host dropdown/table inside settings
 - provider-neutral source-control settings
 
-Current branch status: in progress; a read-only available-hosts section has been
-started, but full ownership split is not complete.
+Current branch status: in progress. Project settings now include an
+available-hosts table, navigation between setup-specific settings panes, and an
+existing-folder import form. The full ownership split is not complete.
 
 ### 8. Host Settings
 
@@ -456,6 +458,8 @@ Already partially landed:
 - optional workspace metadata for `projectId`, `hostId`, and
   `projectHostSetupId`
 - setup-existing-folder API plumbing through local IPC/preload/runtime paths
+- project settings existing-folder setup form for known local, SSH, and active
+  runtime hosts
 - CLI commands for listing projects/setups and creating worktrees by
   project/setup
 - composer `Run on` selector when a project has multiple ready setups
@@ -463,8 +467,8 @@ Already partially landed:
 Not complete yet:
 
 - full project-first default sidebar
-- full setup-on-host UI for local and SSH
 - clone/provision flows
+- bulk setup flows and setup for hosts that are not already known to the client
 - project settings split into global and host-specific ownership
 - host settings/capability UI aligned with project setup
 - complete cache/request ownership audit

notes/project-first-host-model.md

@@ -731,6 +731,11 @@ Landed so far:
   and reuses the existing local/SSH/runtime repo import behavior underneath,
   with an identity guard so an imported folder does not silently become a
   different project.
+- Added a project settings "Available Hosts" section that lists setups for the
+  current durable project, lets users navigate between setup-specific settings
+  panes, and imports an existing folder on another known local, SSH, or active
+  runtime host. Setup routing now follows the selected setup host instead of the
+  currently focused runtime.
 - Added tests for local repos, SSH repos, same-provider multi-host grouping,
   no-identity same-name non-grouping, selector cache behavior, persistence
   backfill, repo mutation synchronization, renderer hydration, and runtime RPC
@@ -746,16 +751,16 @@ Important limitation:
   compatibility records, and workspace creation still maps the resolved
   project-host setup back into the existing repo-centric `createWorktree` API.
   Existing workspaces without the new ownership metadata still infer host/project
-  through their repo compatibility record. Settings and setup-on-host flows still
-  use the current repo-centric APIs until later steps are implemented.
+  through their repo compatibility record. Settings now expose setup-specific
+  host panes and existing-folder setup, but still use repo compatibility records
+  underneath.
 
 Remaining end-to-end work:
 
 - teach workspace creation to resolve `{ projectId, hostId }` through a ready
   project-host setup
-- add setup-on-host flows for local paths and SSH paths
-- add clone/provision setup-on-host flows; existing-folder setup now has an API
-  bridge, but not a complete user-facing project settings flow
+- broaden setup-on-host flows beyond known local, SSH, and active runtime hosts
+- add clone/provision setup-on-host flows
 - split settings into explicit client, host, project, and project-host setup
   scopes
 - backfill explicit workspace project/setup/host ownership for existing