Make the run-it-yourself answer findable, and true

[thalida]

Closes #205

People kept asking whether codecity can open private or local repos. The landing already answered them, in 11px type, tinted to match the card it sat on, in the helper-text slot under an input, and it said something that wasn't quite true.

The answer was wrong

api/ has no git credential support, so clones are anonymous. Running codecity yourself does not open a private remote URL. The only path, for private repos and local folders alike, is clone it yourself and mount the folder. The old copy said "Private and local repos need codecity running on your own machine", which sends people to a docker run that cannot open the repo they just failed to open.

And nobody saw it

--cc-font-xs (11px, the smallest type on the page) in --cc-accent-bg-soft (accent at 10% alpha) over --cc-glass-fill, deliberately shaped to read as part of the input group. It also vanished the moment the field read as a URL, so it was gone for the whole act of pasting a private repo URL.

What ships

The landing answers in the hero. Two lines, one type step, no glyph, whenever this instance can't open a local folder:

Yes, private and local repos work
Clone a repo locally, then run codecity on your machine.

The hero is grouped. It was six siblings at one even 12px gap, with the wallpaper caption sitting between the tagline and the cues it introduces. Three groups now at 24px with 12px inside them (identity, pitch, scope), caption dropped to the foot of the column.

The notice collapsed from eight states to three. It used to branch on hosted and allowLocal and reason. hosted says which deployment this is; the message is about whether this instance can open a local folder, so keying on it made the same sentence move between the hero and the field slot. Now placement is decided by what happened (resting statement in the hero, failure under the field) and the remedy by one boolean:

Couldn't open that path.  Run codecity with a volume mount to access local repos.
[ Run it yourself v ]  Setup guide

Couldn't reach that repo.  If it's private, clone it yourself, then run codecity locally.
[ Run it yourself v ]  Setup guide

Couldn't reach that repo.  If it's private, clone it yourself and open the folder.
$ git clone <src>                                     Setup guide

NoticeReason.Standing is gone (the band owns it), and with it the notice's second visual variant and its glyph: it only answers failures now, so it is always an alert. hosted leaves the frontend entirely, though CODECITY_HOSTED stays in the API and the config table.

Every state hands over a command, never just a link. The old copy told an unmounted local instance to "turn on local paths" and stopped, but -e CODECITY_ALLOW_LOCAL_REPOS=1 plus a -v is turning them on, and it is the same command a visitor needs. Where the repo is known, the disclosure carries the clone and the run together, in that order.

Also

• README: Run it yourself leads with the mounted command; the bare one is a Public repos only aside. Local directories dissolves into it, so LOCAL_DOCS_URL and a component-private RUN_DOCS_URL collapse to one anchor.
• SetupGuideLink: three surfaces linked the same README section under three names (See docs, Full setup, See local setup). One component owns the href and the name.
• MetaLine: about is now GitHub. Same href, same title, same three items; changes the city footer too.

Checks

Full pre-push gate green (7/7) on every commit. 2153 frontend tests. Each new guard was verified to go red against the behavior it protects: the plain docker run, an always-open disclosure, the hosted "turned off" wording, the band removed, the caption back inside the pitch, a blocked path told to clone a folder it already has, and a folder-reading instance told to go run codecity. Contrast computed from the OKLCH tokens rather than eyeballed; the tightest was the command hint at 4.55:1, moved from secondary to primary.

🤖 Generated with Claude Code