Rebuild the deployment from nothing, and fix what that turned up - #283

Merged

davidmckayv merged 15 commits into

mainfrom

fix/zero-to-running

Aug 28, 2026

Commits on Aug 28, 2026

Point the chart's own examples at Intelligence hosts that exist
davidmckayv
committed
6ee3ba0
Assert the CronJob fallbacks the same way the env-var ones are asserted
davidmckayv
committed
22dfde1
Make the Helm chart reachable from the docs, and say what a cluster needs before it
davidmckayv
committed
da88d08
Say what the release is named for, and how a Bot is actually granted the right to address another
davidmckayv
committed
50308fe
Write down the cluster the chart was proven on
davidmckayv
committed
784f140
Keep each comment above the code it describes
davidmckayv
committed
489323a
Count the chart targets the same way in the changelog as in the README
davidmckayv
committed
745825a
Describe the arm64 failure by what it looks like, not by a string nobody here has seen
davidmckayv
committed
65a3383
Name the Bot that handed work over, on the screen that exists to say who did what
davidmckayv
committed
c0dcbcb
Name the rollback flag on both Helm majors, since Helm 4 renamed it
davidmckayv
committed
3f1b781
Answer a tool call with the result that follows it, not one stored anywhere in the thread
davidmckayv
committed
d359f83
Grant one Bot the right to ask another on the Bot's own screen
davidmckayv
committed
73bbd74
Wrap the roster on the width it has, not on the window's
davidmckayv
committed
290f7ea
Name the Bot on its own screen, rather than calling every one of them Browser Bot
davidmckayv
committed
23843e7
Say where the Intelligence credentials come from on the way into a cluster
davidmckayv
committed
eca485f

Navigation Menu

Uh oh!

Rebuild the deployment from nothing, and fix what that turned up - #283

Rebuild the deployment from nothing, and fix what that turned up#283
davidmckayv merged 15 commits into
mainfrom
fix/zero-to-running

Commits on Aug 28, 2026

Point the chart's own examples at Intelligence hosts that exist

Assert the CronJob fallbacks the same way the env-var ones are asserted

Make the Helm chart reachable from the docs, and say what a cluster needs before it

Say what the release is named for, and how a Bot is actually granted the right to address another

Write down the cluster the chart was proven on

Keep each comment above the code it describes

Count the chart targets the same way in the changelog as in the README

Describe the arm64 failure by what it looks like, not by a string nobody here has seen

Name the Bot that handed work over, on the screen that exists to say who did what

Name the rollback flag on both Helm majors, since Helm 4 renamed it

Answer a tool call with the result that follows it, not one stored anywhere in the thread

Grant one Bot the right to ask another on the Bot's own screen

Wrap the roster on the width it has, not on the window's

Name the Bot on its own screen, rather than calling every one of them Browser Bot

Say where the Intelligence credentials come from on the way into a cluster