Skip to content

feat(onboarding): a one-window setup tool for the first provider - #240

Merged
Lethabarb merged 1 commit into
mainfrom
feat/setup-tool
Nov 9, 2026
Merged

Lethabarb merged 1 commit into
mainfrom
feat/setup-tool

Conversation

@Lethabarb

Copy link
Copy Markdown
Owner

What

The owner asked on 9 November 2026 for the first provider's set-up to be simple and to need no command line (D102).

ops/setup-tool opens one small window, from Grow2Notes setup.cmd:

  • Create organisation takes the three values, confirms them, and runs D101's bootstrap.sh on the operator's own Azure CLI sign-in, so the first manager's details reach Azure and no AI provider. It refuses a second organisation in production, using the refusal of admin mcp-client add while none exists as the check. It locks itself if the outcome is unknown, and then approves Claude Code.
  • Open Claude Code for Grow2Notes makes the folder that by-hand.md A3 and C3 describe, adds the connection and starts Claude Code there.

Tried, on test

  • The real Create button through a harness, with accented names, $ and a backtick. The names were stored exactly.
  • A repeat was refused word for word (first-use step 221). Nothing was left in /home/LogFiles or ~/.azure, and Application Insights held nothing from the run (step 222).
  • Production's check for no organisation answered as designed and wrote nothing.
  • An independent review found two real bugs and one gap, all fixed here: a retry after an unknown result could have made a second organisation, test and production shared one folder, and two windows could race.

Docs

  • decisions.md D102 records how each go-live D1 line was met and what the owner has left for later.
  • by-hand.md A2 and mcp-switch-on.md D say those lines wait for the first provider's paperwork.
  • T25's Notes record step 142, and releases.md the switch-on date.

No application code changes.

🤖 Generated with Claude Code

The owner asked on 9 November 2026 for the provider's set-up to be simple and to need no command line (D102).

ops/setup-tool opens one small window. Create organisation takes the three values, confirms them, and runs D101's
bootstrap.sh on the operator's own Azure CLI sign-in, so the first manager's details reach Azure and no AI provider.
It refuses a second organisation in production, using the refusal of admin mcp-client add while none exists as the
check, locks itself when the outcome is not known, and then approves Claude Code. Open Claude Code makes the folder
that by-hand.md A3 and C3 describe, adds the connection and starts Claude Code there.

Tried on test: the real Create button with accented names, $ and a backtick; the names stored exactly; a repeat
refused; nothing left in /home/LogFiles or ~/.azure; and production's check for no organisation.

Decision D102 records what was done for go-live D1 and what the owner has left for later. by-hand.md A2 and
mcp-switch-on.md D say that those lines wait for the first provider's paperwork. T25's Notes record step 142, and
releases.md the switch-on date.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Lethabarb
Lethabarb enabled auto-merge (squash) November 9, 2026 22:38
@Lethabarb
Lethabarb merged commit 107fac6 into main Nov 9, 2026
1 check passed
Lethabarb added a commit that referenced this pull request Nov 9, 2026
Main took D102 for the first provider's quick start (#240), so this
branch's hosting-cost decision becomes D103. Both rows are kept in
design/decisions.md, and this branch's citations of the decision are
renamed in the files it changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Lethabarb
Lethabarb deleted the feat/setup-tool branch November 9, 2026 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant