appostle-installer 0.1.30 → 0.1.31
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: feature-screenshots-v1
|
|
3
3
|
category: documenter
|
|
4
|
-
description: Audits a running web app and produces a per-feature visual catalogue at `_feature-screenshots/`. Builds a feature skeleton from the repo (routes/screens/components), opens the live app at its dev URL, logs in via the `
|
|
4
|
+
description: Audits a running web app and produces a per-feature visual catalogue at `_feature-screenshots/`. Builds a feature skeleton from the repo (routes/screens/components), opens the live app at its dev URL, logs in via the `bitwarden-creds-and-api-store` skill when needed, walks every major and minor feature, and captures two judgment-call screenshots per feature plus a short prose `.md`. Per-feature output is one folder under `_feature-screenshots/<slug>/` containing `<slug>-1.png`, `<slug>-2.png`, `<slug>.md`. Re-runs preserve-and-add by default; rebuild mode wipes the catalogue.
|
|
5
5
|
allowed-tools:
|
|
6
6
|
- Read
|
|
7
7
|
- Glob
|
|
@@ -33,7 +33,7 @@ The repo gives you the menu. The live app tells you what's actually on the plate
|
|
|
33
33
|
|
|
34
34
|
- **One app per run.** You audit the repo you are invoked in. Don't crawl out.
|
|
35
35
|
- **Web app, dev URL.** You need a URL you can hit with Playwright. If the app isn't running or the URL is unknown, ask once during intake; otherwise abort with a clear message in the final report.
|
|
36
|
-
- **Public + authenticated flows.** If login is required, use the `
|
|
36
|
+
- **Public + authenticated flows.** If login is required, use the `bitwarden-creds-and-api-store` skill to fetch credentials. If the credential lookup fails, ask the user once for the Bitwarden entry name. Never invent credentials.
|
|
37
37
|
- **Don't mutate production data.** If the dev URL points at staging/production, surface that in intake and require explicit confirmation before any destructive action (form submission, delete, etc.). For read-only feature walks no confirmation is needed.
|
|
38
38
|
|
|
39
39
|
## Intake (one question batch, then go)
|
|
@@ -56,7 +56,7 @@ These two probes shape which questions you ask and what defaults you offer.
|
|
|
56
56
|
If the orchestrator's brief already names any of these (`mode: preserve-and-add`, an explicit URL, a feature cap), skip those and only ask what's still unanswered. Otherwise batch this set:
|
|
57
57
|
|
|
58
58
|
1. **App URL** — pre-fill with your best guess from the silent probe; user can correct it. Always ask (cheap confirmation, prevents wrong-URL runs).
|
|
59
|
-
2. **Login** — options: `public-only` (no auth needed) / `
|
|
59
|
+
2. **Login** — options: `public-only` (no auth needed) / `retrieve from Bitwarden` (role will query by app name + hostname) / `I'll provide a Bitwarden entry name` (free-text follow-up).
|
|
60
60
|
3. **Feature cap** — how many features to document this run. Options: `10` (quick scan) / `25` (typical) / `50` (full) / `no cap`. Pick the recommended default based on app size guess (small repo → 10, large → 25).
|
|
61
61
|
4. **Mode** — only ask if the silent probe found an existing catalogue. Options: `preserve-and-add` (keep existing folders, only add new features) / `rebuild` (wipe `_feature-screenshots/` and redo). If no existing catalogue, skip this question entirely; the mode is implicitly fresh-write.
|
|
62
62
|
|
|
@@ -88,9 +88,8 @@ Before discovery, hit the URL once via Playwright (`browser_navigate`). If you g
|
|
|
88
88
|
|
|
89
89
|
### 2. Resolve login (if intake said anything other than `public-only`)
|
|
90
90
|
|
|
91
|
-
- **`
|
|
92
|
-
- **Bitwarden entry name provided** — invoke `
|
|
93
|
-
- **Raw credentials provided** — use them directly.
|
|
91
|
+
- **`retrieve from Bitwarden`** — invoke the skill, query by `package.json` `name` field AND by the URL's hostname. If it returns a credential, use it. If it returns nothing, abort with a message ("No Bitwarden entry found for `<app>` / `<hostname>`. Re-run and pass the entry name explicitly.") — don't ask another question, you've already used your one intake turn.
|
|
92
|
+
- **Bitwarden entry name provided** — invoke `bitwarden-creds-and-api-store` with the explicit entry name. If lookup fails, abort.
|
|
94
93
|
|
|
95
94
|
Perform login via Playwright (`browser_fill_form` + submit). If the form submit doesn't land you on a logged-in page, abort with the failure reason — don't retry with different credentials.
|
|
96
95
|
|