Bootstrap UX feedback from real project setup (git preflight, install retries, completion semantics)

[stackbilt-admin]

Charter CLI Feedback From This Build

Date: 2026-05-14
Context: bootstrap + governance setup while delivering @stackbilt/email.

Net impact

Charter accelerated governance setup and standardized SDLC wiring quickly. The generated ADF + policy footprint reduced setup ambiguity and made repo guardrail state measurable via charter doctor.

What helped

• One-command bootstrap created .charter/, ADF modules, and CI governance workflow in one pass.
• charter doctor gave immediate machine-checkable status for guardrail completeness.
• package.json script wiring made governance checks repeatable in normal dev flow.
• Hook installers (commit-msg, pre-commit) were straightforward once git state was valid.

Friction observed

• Bootstrap surfaced a generic warning when run before git was fully initialized; more explicit remediation text would help.
• Dependency install behavior in constrained WSL/NTFS contexts required manual retries and lockfile synchronization.
• CLI output said setup succeeded while internal pnpm install failed non-fatally; this can be misread as fully complete.

Suggestions for Charter repo issue

• Improve preflight in bootstrap:
  • hard-check git repo health before setup starts
  • print exact git init / remediation step when missing
• Improve dependency error UX:
  • on install failure, print likely causes bucketed by network/permissions/lockfile
  • offer optional retry flags (--no-frozen-lockfile) hint when lockfile drift detected
• Tighten completion semantics:
  • include an explicit "setup partially complete" summary when install failed
  • provide a next-command checklist at the bottom (pnpm install, charter doctor, hook install)

Evidence from this run

• Initial doctor status: WARN (Not inside a git repository)
• Post git init + hook install: PASS
• Hooks installed:
  • .git/hooks/commit-msg
  • .git/hooks/pre-commit