featureparity 0.0.20 → 0.0.22

data/lib/fp/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Fp
-  VERSION = '0.0.20'
+  VERSION = '0.0.22'
 end

data/skills/fp/SKILL.md

@@ -336,6 +336,30 @@ This also catches the one regression a green test suite can't: a test that was d
 renamed, or had its `fp:` marker stripped. Every remaining test passes, so CI is happy,
 while the requirement quietly lost its only proof.
 
+### 9. Fill in the client showroom when a surface is deployed
+
+The project's client (the person the software is being built for) sees one page: the
+showroom. It is a welcome note plus a card per surface — a link, a button label, and
+instructions for signing in and trying it. You deployed the surface, created the demo
+accounts, and know the URLs, so you fill the card in; a human retyping it into project
+settings is the step that goes stale.
+
+```bash
+fp showroom --project X                          # current state; hidden surfaces listed
+fp projects edit X --showroom-welcome-file docs/showroom/welcome.txt
+fp surfaces edit web --project X \
+  --showroom-url https://dev.example.com \
+  --showroom-label "Open the web app" \
+  --showroom-instructions-file docs/showroom/web.txt
+```
+
+Write instructions a non-technical reader can follow: where to click, which account to
+sign in as (a dedicated demo account, not the one your e2e suite mutates), what data is
+already there to look at, and one or two things worth trying. Keep the file in the repo
+(`docs/showroom/<surface>.txt`) so the next deploy can re-send it. A surface with neither
+a link nor instructions is not shown; clear both to take a card down. Feedback and the
+share link are human-only, so after writing the content tell a person it's ready.
+
 ### Repo-local config (`.featureparity.yml`)
 
 If a repo has a `.featureparity.yml`, `--project` is optional — `fp` reads the slug from
@@ -419,6 +443,9 @@ not as the fix — you still write the proposal.
 | List projects | `fp projects` |
 | Create a project | `fp projects create <slug> --name "..." --surfaces api,web` |
 | View / edit a project | `fp projects show <slug>`, `fp projects edit <slug> --name "..."` |
+| Preview the client showroom | `fp showroom --project X` |
+| Write a surface's showroom card | `fp surfaces edit <key> --project X --showroom-url ... --showroom-instructions-file ...` |
+| Write the showroom welcome | `fp projects edit <slug> --showroom-welcome-file ...` |
 
 All commands support `--json` for machine-readable output.
 

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]
 ```
 
@@ -54,13 +54,63 @@ owner — or a key minted by one — may delete; a member's key gets 403.
 
 ### fp surfaces
 
-List surfaces for a project.
+List, view, create, edit and delete a project's surfaces.
 
 ```bash
 fp surfaces --project stowzilla
 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]
+fp surfaces delete <key> --project stowzilla [--yes]
 ```
 
+A key is unique within a project. `add` on a key that already exists fails and points
+you at `edit` — use `edit` to fill in the kind or repo of a surface that `fp projects
+create --surfaces` made with defaults. `edit` only sends the flags you pass. `delete`
+asks you to type the key back in a terminal and refuses without `--yes` otherwise.
+
+A surface that requirements still require can't be deleted or re-keyed — the server
+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, then a card per surface with a link, a button label, and instructions
+for signing in and trying it. 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 }
+```
+
+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
+```
+
+A surface is on the showroom once it has a link or instructions, and leaves it when
+both are blank; 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.20
+  version: 0.0.22
 platform: ruby
 authors:
 - Stowzilla
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-10-17 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,7 @@ files:
 - lib/fp/commands/repos.rb
 - lib/fp/commands/setup.rb
 - lib/fp/commands/show.rb
+- lib/fp/commands/showroom.rb
 - lib/fp/commands/surfaces.rb
 - lib/fp/commands/version.rb
 - lib/fp/commands/whoami.rb