Files
hanzo.ai/lib/data/rooms.json
zeekay ce9b3d1f7a /dev is Dev's page for a stranger and the builder for a member
Signed out, bare /dev bounced to sign-in, so the address every Dev link
names showed a stranger nothing and a crawler a noindexed room. It is now
Hanzo Dev's page, server-rendered and public: the agent in the terminal, on
the web, in the cloud and in Slack; install by hanzo.sh, npm or Homebrew;
enso-auto by default and Kai deciding each step; Apache-2.0 on GitHub. Open
Dev is /login?next=%2Fdev, so the sign-in comes back to the builder. Every
command was run against the binary it names; the latest release is GitHub's
answer when the page opens and absent when GitHub does not answer.

Nothing changes for a member, nor for any other address under /dev: a
signed-in reader gets the builder in the rooms' frame as before (the frame
is components/rooms Room, which app/(app)/layout.tsx now draws too), an old
query still moves to its path once, and a stranger at a path under /dev, or
at /dev with an old query, still signs in to it. The door is Apex's, the
one / uses, given Dev's two answers; AWAY (app/dev/_away.ts) takes the page
off before it paints at a place, as BOOT does for a live session.

The one visible change for a member is a session ending: a sign-out in
another tab reloads bare /dev, which is now Dev's page rather than a bounce
to sign-in (follow.spec.ts says so); nothing is sent as nobody either way.

/dev leaves app/(app) for the app root, so it is no longer a room
(lib/data/rooms.json). Gates: e2e/gates/dev.spec.ts, and in login.spec.ts
Open Dev through a real sign-in and back.
2026-10-16 10:34:26 -07:00

21 lines
335 B
JSON

[
"/board",
"/bots",
"/cal",
"/chat",
"/chat/shared",
"/contacts",
"/dashboard",
"/drive",
"/home",
"/inbox",
"/meet",
"/settings",
"/settings/organization",
"/settings/organization/billing",
"/settings/organization/keys",
"/settings/organization/members",
"/settings/organization/usage",
"/work"
]