v2 reset: define new-computer bootstrap flow

[shpoont]

Problem

A key use case is setting up a new computer: install the apps, then apply the stored settings. The current product materials do not make this flow concrete enough.

Scope

Define and implement the new-computer bootstrap workflow from a settings storage folder.

Expected user story

1. User installs applications, for example with brew bundle from a Brewfile.
2. User points dotfiles-manager at an existing settings storage folder.
3. dotfiles-manager shows which apps/settings can be applied, which apps are missing, and what will change.
4. User applies all or selected settings safely.
5. Missing or unsupported apps are reported clearly without blocking unrelated settings.

Acceptance criteria

• A first-run/new-computer flow is specified with concrete commands and expected output.
• The flow does not require the storage folder to be a Git repository, though Git usage is documented as recommended.
• Missing app handling is explicit and user-friendly.
• All-app apply from storage is supported with preview and confirmation.
• Partial apply is supported where recipe granularity allows it.
• Docs include a Homebrew Bundle example as one common app-installation path without making Homebrew mandatory.
• Tests cover applying from an existing storage fixture into a clean temp home.

#219 audit follow-up: split sequence

Source: #219 audit merged in #220 (docs/internal/project/v2-reset-audit-issue-219.md).

This issue is now a parent delivery area. Use these split issues:

• v2 bootstrap: specify new-computer UX and output #230 — specify new-computer UX and output.
• v2 bootstrap: implement apply-from-storage flow after sync model #231 — implement apply-from-storage flow after the sync model.

Additional gate:

• v2 bootstrap: specify new-computer UX and output #230 must use v2 reset: revise product concept and vocabulary around settings storage #210 vocabulary and v2 reset: redesign status, diff, and sync as the primary UX #211 sync planning/write concepts.
• v2 bootstrap: implement apply-from-storage flow after sync model #231 must depend on accepted v2 reset: revise product concept and vocabulary around settings storage #210 vocabulary and v2 reset: redesign status, diff, and sync as the primary UX #211 mutating sync execution contract.
• Bootstrap must not invent a separate apply mechanism outside the sync model.
• Homebrew Bundle remains an example app-install path, not a dependency.

Project Execution Standards alignment

Latest standard read for this update: /Users/shpoont/Work/shpoont/project-execution-standards/project-execution-standard.md, last-updated 2026-06-29.

Project record / source of truth: #209 plus docs/internal/project/v2-reset-execution-record.md; this issue is the bootstrap parent.

Role of this issue: parent delivery area for new-computer bootstrap, not a direct implementation package.

Risk tier: parent mixed Tier 1/Tier 2. #230 is Tier 1 UX/design work because it defines a user-facing setup flow and output. #231 is Tier 2 implementation work because it can write stored settings into live app settings on a new machine.

Required sequence:

• v2 bootstrap: specify new-computer UX and output #230 must produce documentation-first / runnable or replayable UX evidence before v2 bootstrap: implement apply-from-storage flow after sync model #231 starts.
• v2 bootstrap: implement apply-from-storage flow after sync model #231 must use accepted sync/write semantics; it must not invent a separate apply mechanism outside the sync model.
• End-user docs from v2 bootstrap: specify new-computer UX and output #230/v2 bootstrap: implement apply-from-storage flow after sync model #231 must be reconciled through v2 docs: rewrite end-user documentation after product reset #216 after real behavior is verified.

Change rule:

• Changes to bootstrap scope, command/output shape, write semantics, mandatory prerequisites, or implementation sequence are managed changes requiring Project Owner decision.

No-go actions:

• Do not implement new-computer apply behavior before v2 bootstrap: specify new-computer UX and output #230 is accepted and an implementation-start gate exists for v2 bootstrap: implement apply-from-storage flow after sync model #231.
• Do not make Homebrew mandatory; Homebrew Bundle remains one example app-installation path.
• Do not write live settings without preview, confirmation, real-result verification, validation, and acceptance evidence.

Acceptance rule / closure rule:

• Project Owner acceptance is required before closing this parent.
• Keep this parent open until v2 bootstrap: specify new-computer UX and output #230 and v2 bootstrap: implement apply-from-storage flow after sync model #231 are accepted or explicitly deferred, then record a project-level checkpoint in v2 reset: realign product plan around settings-folder sync #209 and docs/internal/project/v2-reset-execution-record.md.