[morgmart]

What this does

Adds New project beneath New chat in Solo. A project can start empty, with optional instructions and multiple context folders supplied in the same dialog. New chats copy these defaults through the existing project-template path; moving an existing chat preserves its own instructions.

Folder attachments appear as separate cards in a bounded list. Native folder pickers start at the current worktree location and display home-relative paths. Selecting a folder does not change an agent’s working directory or create a worktree: the existing worktree switch remains instructions copied into chats.

Shared design changes

Morgan confirmed the app-wide lighter form and preference labels and tighter outer dialog padding on October 14. Labels use regular-weight 14px text; dialog padding changes from 24px to 20px at the default breakpoint. The spacing between fields and between labels and inputs is unchanged. Shared optional labels, card-list and chevron-free picker treatments replace local variants.

Saving and recovery

Project organization and defaults remain separate existing records. Defaults are validated with their actual community envelope before publication. Submitted values stay locked and visibly disabled; a failed attempt offers Retry with its retained values, and conflicting saved defaults offer Close rather than an impossible retry. An uncertain save reconciles existing defaults and reuses its signed intent. No cross-record transaction is claimed.

Re-entering a project’s New chat updates an already-mounted composer through the existing draft notifications, clearing changed project instructions while preserving pending starts. No new draft store, navigation reset counter, or data-loading subsystem is added. Folder picker completion restores focus to an available control; native folder paths no longer reinterpret ~name as home or silently replace unsupported filename bytes.

Review and validation

Rebased onto main at 0201b54c4, including the landed navigation layer #1132 and newer navigation lifetime fix. Local fixes are at 45188d96c.

• Mandatory pre-commit and pre-push hooks passed for 45188d96c with no bypass (two test workers), including TypeScript/related Vitest, design guards and workspace Clippy.
• Before the final non-overlapping main rebase: 126 focused feature/preference tests and 164 design-system tests passed, with two workers. TypeScript, design type checks, design static checks and design build passed. Two native path-helper tests passed on macOS through pinned Rust; this is not a full native build or Windows execution.
• The mounted-reset, disabled retry, accessibility and picker-focus regressions were observed failing before their fixes. The mounted-reset tests now send and verify the resulting project and instructions, including recovery of a pending start.
• Independent architecture, UI and runtime source reviews ran. The existing save order was retained: changing it would introduce a different partial-save outcome without fixing a demonstrated defect. Global label/padding approval is recorded above; source review does not replace rendered acceptance.
• The previous CI read-frontier failure was traced to observing the whole-channel marker instead of the automatic activity:alpha catch-up marker. The wait now observes the correct durable boundary and retains exact Mark unread/Mark read actions. Main already fixes the recovery-heading and Buzz-link preview failures.
• Browser cases added/removed: 0/0. Existing message-management coverage retains its real portal, pointer/focus and durable-read integration; channel-member coverage retains its rendered alignment/focus contract under the approved padding change. Browser checks have not been rerun locally in this session.

Still pending: fresh hosted CI, rendered light/dark/narrow/wide/enlarged-text and keyboard/pointer acceptance, native picker/full-app acceptance, human testing, and reviewer approval. The PR remains draft until those gates are satisfied; agent and human acceptance are not yet complete.

[kalvinnchau]

🤖 Two P2 findings remain in project reset and defaults validation; details inline.

[wesbillman]

🤖 Carl, an automated reviewer, commenting via Wes’s GitHub account.

Verdict: two blockers. The Court reviewed the PR diff against morganm/berd-navigation at 0c25d928. That diff is identical to the one at 1543fa53. The review was source-only: no native picker, browser, theme or enlarged-text runs.

Blocking

1. CI is red because of this PR. The new read-frontier wait in message-management.spec.mjs fails every repetition in every flake-check shard and in journeys 2/9 on both engines. The flake checks on 0c25d928 are failing the same way.
2. Clicking New chat in a project you are already in does not reset the mounted composer, so the chat can start in the wrong project.

Should fix: the accessible name for Field optional, and the locked retry state in NewProject (details inline).

Optional: the tilde grammar in the folder picker and lossy non-UTF-8 paths, plus focus restoration after pickers and failures.

Merge criteria

• Both blockers fixed, each with a regression test that fails before the fix.
• Hosted browser checks green.
• Design-owner sign-off on the global changes: 20px dialog padding (every Dialog), Regular-weight field/choice/PreferenceRow labels, and 14px Switch labels. Splitting them into their own PR is the alternative. Only channel-members-focus.spec.mjs was updated for the geometry change.
• The pending checks the description already lists.

Non-blocking metadata: Co-authored-by: Carl <carl@agents.block.xyz> is not a verified managed-agent identity.

[kalvinnchau]

🤖 One P2 recovery defect and two P3 findings; details inline.

[kalvinnchau]

🤖 Re-reviewed the latest changes. The stale selectors are fixed, and the full me-polish journey passes in Chromium and WebKit. No remaining actionable findings. Required CI must pass before merge.