feat: deploy is a button again — one visible action, honest feedback, no phantom docs - #160
Merged
Conversation
… no phantom docs Moving every write into the ⌘K palette (#73) left the header with zero action buttons: behold looked read-only unless you happened to press ⌘K, the docs still said "click Run floci-apply" about buttons that no longer existed, and an estate had three differently-named routes to the same apply. Concretely: - The PRIMARY deploy gesture is a header button again. A committed ApplyOp gets `▶ Deploy (<op>)` (+ `Approve <gate>` beside it when gated); a project with only components gets `▶ Deploy…`, which opens the dial's component picker. One intent, one word — the tooltip carries the mechanism. Everything else stays in ⌘K. - The dial no longer vanishes wordlessly when no env is picked — it says what's missing and where to pick it. A static export keeps the silence (there is genuinely nothing to offer). - Errors get a toast at the point of gesture, not only a line in a bottom log pane that is display:none until something writes to it. Successes toast too ("running <op> — output streams in the log below"), so a palette action no longer closes into dead air. - The Floci #16 warnings (re-apply collides on the emulator) only appear when the estate actually targets Floci — a k3d/helm estate used to be warned about an emulator it doesn't use, in dialogs and in the 409 (the server side of this gating landed in #159). - Docs describe the UI that exists: README, example-k8s/README, run-it.mdx, and acting.mdx's action table (button vs palette, per action). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NEtbXBSwLiYFMKv2o4VMb4
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moving every write into the ⌘K palette (#73) left the header with zero action buttons: behold looked read-only unless you happened to press ⌘K, the docs still said "click Run floci-apply" about buttons that no longer existed, and an estate had three differently-named routes to the same apply.
▶ Deploy (<op>)for a committed ApplyOp (+Approve <gate>beside it when gated),▶ Deploy…(opens the dial's component picker) for a components-only project. One intent, one word — the tooltip carries the mechanism. Everything else stays in ⌘K.display:noneuntil something writes to it; successes toast too, so a palette action no longer closes into dead air.🤖 Generated with Claude Code
https://claude.ai/code/session_01NEtbXBSwLiYFMKv2o4VMb4