lagora-cli 1.1.0

package/dist/skills/legato-site-feedback/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: legato-site-feedback
+description: "Use this skill when handling Lagora site feedback from the in-site feedback popup: fetch reports, cluster meaningful site issues, plan improvements with ULW, implement, verify, deploy, and resolve feedback only after live validation."
+---
+
+# Legato Site Feedback
+
+This skill handles feedback about the Lagora site itself: UI layout, navigation, settings, workflow friction, confusing behavior, missing controls, and agent or CLI affordances. Do not use it for Legato kernel/lowering bugs; those belong in normal Lagora issues.
+
+## Workflow
+
+1. Fetch all open feedback before planning.
+
+```bash
+lagora feedback fetch --api-url https://legato-dev-agora.hyperaccel.net/legato-dev-agora --status open
+```
+
+For local development or a mounted issue store:
+
+```bash
+lagora feedback fetch --store /path/to/issue-store --status open
+```
+
+2. Record the feedback IDs, reporter names, page paths, timestamps, and exact user-facing complaints in the work log.
+3. Analyze every report, then cluster them into meaningful improvements. Multiple feedback reports may map to one improvement when they share the same root cause.
+4. Separate actionable work from duplicates, already-fixed behavior, kernel issue reports, vague requests, and declined changes. Keep declined or non-actionable items explicit with a reason.
+5. Create a ULW plan for the actionable improvements. The plan must include RED evidence, implementation steps, verification, review, deploy, and feedback resolution.
+6. Implement the smallest site change that addresses the cluster. Preserve the existing design system and avoid expanding notification or feedback handling beyond the reported workflow.
+7. Verify with automated checks and browser QA on the actual affected surfaces. Capture evidence for the original complaint, the fixed behavior, and a mobile layout when UI is touched.
+8. Review the change, commit it, merge or push to `main`, wait for CI and deployment, then validate the live site.
+9. Resolve feedback only after live validation passes:
+
+```bash
+lagora feedback resolve \
+  --api-url https://legato-dev-agora.hyperaccel.net/legato-dev-agora \
+  --id <feedback-id> \
+  --author "agent"
+```
+
+## Output Contract
+
+When finished, report:
+
+- Feedback IDs handled.
+- Clusters found and which implementation resolved each cluster.
+- Files changed.
+- Verification commands and browser QA evidence.
+- Deployment status and live validation result.
+- Feedback IDs resolved or intentionally left open with the reason.

package/dist/skills/legato-site-feedback/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Legato Site Feedback"
+  short_description: "Triage, cluster, fix, verify, deploy, and resolve Lagora site feedback"
+  default_prompt: "Use $legato-site-feedback to process open Lagora site feedback end to end."
+
+policy:
+  allow_implicit_invocation: true

package/package.json

@@ -0,0 +1,16 @@
+{
+  "name": "lagora-cli",
+  "version": "1.1.0",
+  "description": "Lean Legato Agora command-line client",
+  "license": "ISC",
+  "type": "module",
+  "bin": { "lagora": "dist/lagora.js" },
+  "files": ["dist/"],
+  "engines": { "node": ">=22.16.0" },
+  "publishConfig": { "access": "public", "registry": "https://registry.npmjs.org/" },
+  "scripts": {
+    "build": "node build.mjs",
+    "prepack": "node build.mjs",
+    "test": "node --import tsx --test test/*.test.mjs test/*.test.ts"
+  }
+}