@mhosaic/feedback-cli 0.47.0 → 0.47.1

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mhosaic/feedback-cli",
3
- "version": "0.47.0",
3
+ "version": "0.47.1",
4
4
  "description": "CLI to install @mhosaic/feedback into a host app, verify the integration, and drop a guided Claude Code skill (/integrate-feedback) into ~/.claude/skills.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -207,9 +207,9 @@ Follow `references/verify-install.md` for the full end-to-end smoke test:
207
207
  2. Drive Chrome to the dev URL
208
208
  3. Screenshot — confirm the FAB renders (bottom-right corner)
209
209
  4. Click the FAB, fill the form with `[INTEGRATE-FEEDBACK SMOKE TEST]`, submit
210
- 5. Drive Chrome to `https://software-factory-3tbbu.ondigitalocean.app/reports` and confirm the report landed
210
+ 5. Drive Chrome to `https://software-factory-3tbbu.ondigitalocean.app/c/<company-slug>/reports` and confirm the report landed
211
211
 
212
- Both verify (step 8) and smoke test (step 9) write to the report stream — the operator can clean them up after a successful integration (admin SPA → /reports → filter by description → bulk delete).
212
+ Both verify (step 8) and smoke test (step 9) write to the report stream — the operator can clean them up after a successful integration (admin SPA → /c/<company-slug>/reports → filter by description → bulk delete).
213
213
 
214
214
  ---
215
215
 
@@ -331,7 +331,7 @@ Print this to the chat.
331
331
 
332
332
  ## Step 6 — Verify the project really exists
333
333
 
334
- Drive Chrome to `https://software-factory-3tbbu.ondigitalocean.app/companies/<company-slug>` and screenshot. The operator should see the project listed. Then drive to `/settings/widget-keys` and confirm the key shows up there (masked — the plaintext is gone after this point).
334
+ Drive Chrome to `https://software-factory-3tbbu.ondigitalocean.app/c/<company-slug>/settings/projects` and screenshot. The operator should see the project listed. Then drive to `/c/<company-slug>/settings/widget-keys` and confirm the key shows up there (masked — the plaintext is gone after this point).
335
335
 
336
336
  If the project doesn't appear: something silently failed (browser cache, deploy mid-rollout, race condition). Open browser DevTools network tab via `mcp__claude-in-chrome__read_network_requests` filtered to `/api/feedback/v1/projects/` and inspect the actual POST response. Surface the diagnostic to the operator and stop.
337
337
 
@@ -94,7 +94,7 @@ and surface the status code + response body.
94
94
 
95
95
  ## Step 6 — Confirm the report landed in admin
96
96
 
97
- Drive Chrome to `https://software-factory-3tbbu.ondigitalocean.app/reports`. You may need to log in if the operator's session expired.
97
+ Drive Chrome to `https://software-factory-3tbbu.ondigitalocean.app/c/<company-slug>/reports`. You may need to log in if the operator's session expired.
98
98
 
99
99
  Filter by description containing `[INTEGRATE-FEEDBACK SMOKE TEST]`. The new report should appear at the top of the list.
100
100