@mhosaic/feedback-cli 0.48.0 → 0.49.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mhosaic/feedback-cli",
-  "version": "0.48.0",
+  "version": "0.49.0",
   "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.",
   "type": "module",
   "bin": {

package/skills/feedback-from-meeting/SKILL.md

@@ -29,20 +29,30 @@ Load via `ToolSearch`: `project_list`, `project_get_info`,
   answers `insufficient_level`).
 - The project has « Saisie au nom des clients (MCP) » on:
   `project_get_info` returns `allow_proxy_recording: true`. When it is
-  false, stop: an admin turns it on in the project settings. Never work
-  around it with `feedback_create`.
+  false, stop: a project manager turns it on in the project settings.
+  Never work around it with `feedback_create`. The people lookup is
+  refused too while it is off.
+- The project's widget can show « Noté par l'équipe Mhosaic »:
+  `project_get_info` returns `proxy_recording_blocker: null`. Otherwise
+  it holds the reason (for example an environment still serving a widget
+  older than 0.53.0), and every row in a person's name would be refused:
+  stop and show that reason. The operator either deploys 0.53.0 or later
+  to the project first (admin → Versions → Déployer vers…) or chooses to
+  file the whole batch "as me".
 - Notes are available: a file path, pasted text, or a transcript.
 
 ## Steps
 
 1. **Project.** `project_list` / `project_get_info` to pick the project,
-   check `allow_proxy_recording`, and note `peer_validation` (step 4).
+   check `allow_proxy_recording` and `proxy_recording_blocker`, and note
+   `peer_validation` (step 4).
 2. **People.** For each speaker in the notes,
    `project_people_list(project_slug, query=<name>)`. Prefer rows with
    `has_widget: true`. If a name matches several people or none, put it in
    the "to confirm" list of step 5; never guess. Note each person's
-   `widget_version`: below `0.52.0` or null means their widget will not
-   show « Noté par l'équipe Mhosaic » yet.
+   `widget_version`. On a project whose host app bundles the widget, the
+   platform also refuses anyone whose own widget is unknown or older than
+   0.53.0; plan those items "as me" and warn at the gate.
 3. **Items.** Extract each piece of feedback: speaker, what they said (keep
    their words and their language; light cleanup only, it goes out under
    their name), type (`bug` / `feature` / `question` / `praise` / `typo`),
@@ -66,12 +76,14 @@ Load via `ToolSearch`: `project_list`, `project_get_info`,
    A person can reply on or validate a report only when it is theirs
    (its `submitter.person_id` is their `person_id`), or any report of the
    project when `peer_validation` is true. Otherwise the tools answer
-   "Report not found".
+   "Report not found". A report with no `submitter` (filed by the team or
+   by a server) takes no reply or validation in anyone's name: plan a
+   team note on it.
 
    - Open report that says the same thing and is theirs (or
      `peer_validation`): plan a reply in their name on it.
-   - Same thing, but someone else's report and `peer_validation` false:
-     plan a team note on it (an internal `feedback_comment`, step 6), and
+   - Same thing, but someone else's report and `peer_validation` false,
+     or a report with no submitter: plan a team note on it (an internal `feedback_comment`, step 6), and
      flag it "not theirs: team note, not in their widget". The operator may
      switch it to a new report in their name at the gate.
    - A verdict: `feedback_get` the report. A validation needs the same
@@ -84,17 +96,18 @@ Load via `ToolSearch`: `project_list`, `project_get_info`,
    | --- | ------ | ------ | ------ | ---- | ----------- | -------- |
 
    Action is one of: new report, reply on #N, validated #N, reopened #N
-   (with their reason), team note on #N. Warnings: "widget too old to show « Noté par »"
-   (`widget_version` below 0.52.0 or unknown), "known only by email, won't
+   (with their reason), team note on #N. Warnings: "widget version unknown: « Noté
+   par » shows once they open an up-to-date widget", "known only by email, won't
    appear in their widget" (`has_widget: false`), "name matches several
-   people", "not awaiting validation". List the items you are NOT recording
+   people", "not awaiting validation", "widget too old for « Noté par »:
+   filed as me". List the items you are NOT recording
    and why. Proceed only on the operator's explicit approval of this table
    (they may edit rows first).
 
 6. **Execute.** Generate one batch UUID (`uuidgen`). Before any write,
    save the approved table with it, as the operator approved it, to
    `meeting-batch-<first 8 characters of the UUID>.md` next to the notes
-   file: the UUID, then one numbered row per action with every argument
+   file (in the current directory when the notes were pasted): the UUID, then one numbered row per action with every argument
    below (screenshots as file paths: upload ids are minted per run). That
    file is the batch; `<n>` below is its row number and never changes.