featureparity 0.0.21 → 0.0.23

data/skills/fp/references/cli.md

@@ -36,7 +36,7 @@ fp projects                       # list
 fp projects --json
 fp projects show <slug>           # details + surfaces
 fp projects create <slug> --name "Name" [--description "..."] [--surfaces api,web]
-fp projects edit <slug> [--name "..."] [--description "..."]
+fp projects edit <slug> [--name "..."] [--description "..."] [--showroom-welcome "..." | --showroom-welcome-file PATH]
 fp projects delete <slug> [--yes]
 ```
 
@@ -62,6 +62,7 @@ fp surfaces --project stowzilla --json
 fp surfaces show <key> --project stowzilla
 fp surfaces add <key> --project stowzilla [--name "..."] [--kind api|web|android|ios|other] [--audience ...] [--repo org/repo] [--default-branch main]
 fp surfaces edit <key> --project stowzilla [--name "..."] [--kind ...] [--audience ...] [--repo ...] [--default-branch ...] [--key new_key]
+fp surfaces edit <key> --project stowzilla [--showroom-url URL] [--showroom-label "..."] [--showroom-instructions "..." | --showroom-instructions-file PATH] [--showroom-position N]
 fp surfaces delete <key> --project stowzilla [--yes]
 ```
 
@@ -74,6 +75,68 @@ A surface that requirements still require can't be deleted or re-keyed — the s
 refuses and names them. Taking a surface off a requirement is a human's call, so ask
 one rather than working around it.
 
+### fp showroom
+
+The client showroom is the one page a client of the project sees: the project's
+welcome note and a gallery of screenshots or videos under it, then a card per surface
+with a link, a button label, instructions for signing in and trying it, and its own
+media. The team's agents keep that content; this command
+shows the result.
+
+```bash
+fp showroom --project stowzilla          # what a client sees, plus which surfaces are hidden and why
+fp showroom --project stowzilla --json   # { showroom, hidden, share_link }; showroom.gallery and each surface's media
+```
+
+Writing the content:
+
+```bash
+fp projects edit stowzilla --showroom-welcome "Hi Sam, here's what we built."
+fp projects edit stowzilla --showroom-welcome-file docs/showroom/welcome.txt
+fp surfaces edit web --project stowzilla \
+  --showroom-url https://dev.example.com \
+  --showroom-label "Open the web app" \
+  --showroom-instructions-file docs/showroom/web.txt
+fp surfaces edit ios --project stowzilla --showroom-url "" --showroom-instructions ""   # take the card down
+fp surfaces edit web --project stowzilla --showroom-position 1    # clients see web first
+fp surfaces edit web --project stowzilla --showroom-position ""   # back to alphabetical
+```
+
+Media — screenshots and videos on a surface's card, or in the project gallery under the
+welcome note when `--surface` is omitted:
+
+```bash
+fp showroom media --project stowzilla             # gallery, then each surface in showroom order: id, kind, file, caption, position
+fp showroom media --project stowzilla --json      # { media: [...each with surface_key (null = gallery)], project }
+fp showroom media add e2e/results/checkout.webm --project stowzilla --surface web \
+  --caption "Checking out with a saved card" --position 1
+fp showroom media add docs/showroom/overview.png --project stowzilla    # the gallery
+fp showroom media edit <id> --project stowzilla --caption "New words" --position 2
+fp showroom media edit <id> --project stowzilla --caption "" --position ""   # clear the caption, move it last
+fp showroom media remove <id> --project stowzilla --yes
+```
+
+Accepted: png, jpg/jpeg, gif, webp, mp4, webm, mov, up to 100 MB. Anything else — SVG
+(it can carry script) and PDF included — is refused with the reason before anything is
+sent, as is a `--position` that isn't a whole number of 1 or more. Within a card or the
+gallery, positions run 1..n with no gaps: `--position N` puts the item at slot N and
+shifts the others, an empty `--position` moves it to the end, and `add` without one
+appends. `remove`
+asks you to type the filename back in a terminal and refuses non-interactively without
+`--yes`.
+
+A surface is on the showroom once it has a link, instructions, or media, and leaves it
+when all three are empty; there is no separate on/off switch, so `fp showroom` lists the hidden
+surfaces so a card that dropped out is noticed. Links must be `http://` or `https://`
+(the CLI checks before sending). The `-file` variants are for anything longer than a
+line: the showroom keeps line breaks, so write real paragraphs. Only the flags you pass
+are sent.
+
+Two things are deliberately not available to an agent's key: leaving feedback (that is
+the client talking) and turning the share link on or off (publishing a link anyone can
+open is a person's decision). `fp showroom` reports the share link as `unknown` for
+that reason; a human checks it under Project Settings → Showroom in the web app.
+
 ### fp list
 
 List requirements.

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: featureparity
 version: !ruby/object:Gem::Version
-  version: 0.0.21
+  version: 0.0.23
 platform: ruby
 authors:
 - Stowzilla
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-10-20 00:00:00.000000000 Z
+date: 2026-10-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: net-http
@@ -119,6 +119,8 @@ files:
 - lib/fp/commands/repos.rb
 - lib/fp/commands/setup.rb
 - lib/fp/commands/show.rb
+- lib/fp/commands/showroom.rb
+- lib/fp/commands/showroom_media.rb
 - lib/fp/commands/surfaces.rb
 - lib/fp/commands/version.rb
 - lib/fp/commands/whoami.rb