fimo 2.8.0-staging.5 → 2.8.0-staging.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fimo",
-  "version": "2.8.0-staging.5",
+  "version": "2.8.0-staging.6",
   "description": "Fimo CLI - create, deploy, and manage Fimo projects",
   "keywords": [
     "astro-component"
@@ -194,13 +194,13 @@
   "devDependencies": {
     "@clack/core": "^1.2.0",
     "@clack/prompts": "^1.2.0",
-    "@fimo/agents-bundle": "2.8.0-staging.5",
-    "@fimo/api-contracts": "2.8.0-staging.5",
-    "@fimo/cli-kit": "2.8.0-staging.5",
-    "@fimo/framework-detect": "2.8.0-staging.5",
-    "@fimo/routes": "2.8.0-staging.5",
-    "@fimo/sdk": "2.8.0-staging.5",
-    "@fimo/tsconfig": "2.8.0-staging.5",
+    "@fimo/agents-bundle": "2.8.0-staging.6",
+    "@fimo/api-contracts": "2.8.0-staging.6",
+    "@fimo/cli-kit": "2.8.0-staging.6",
+    "@fimo/framework-detect": "2.8.0-staging.6",
+    "@fimo/routes": "2.8.0-staging.6",
+    "@fimo/sdk": "2.8.0-staging.6",
+    "@fimo/tsconfig": "2.8.0-staging.6",
     "@types/node": "22.18.6",
     "agent-install": "^0.0.5",
     "astro": "^7.1.6",

package/templates/astro/package.json

@@ -9,9 +9,10 @@
     "check": "astro sync && astro check"
   },
   "dependencies": {
-    "fimo": "2.8.0-staging.5",
-    "fimo-analytics": "2.8.0-staging.5",
-    "fimo-astro": "2.8.0-staging.5"
+    "fimo": "2.8.0-staging.6",
+    "fimo-analytics": "2.8.0-staging.6",
+    "fimo-astro": "2.8.0-staging.6",
+    "zod": "^4.4.3"
   },
   "devDependencies": {
     "@astrojs/check": "^0.9.10",

package/templates/nextjs/package.json

@@ -12,13 +12,14 @@
   },
   "dependencies": {
     "@tanstack/react-query": "^5.80.6",
-    "fimo": "2.8.0-staging.5",
-    "fimo-analytics": "2.8.0-staging.5",
-    "fimo-next": "2.8.0-staging.5",
-    "fimo-react": "2.8.0-staging.5",
+    "fimo": "2.8.0-staging.6",
+    "fimo-analytics": "2.8.0-staging.6",
+    "fimo-next": "2.8.0-staging.6",
+    "fimo-react": "2.8.0-staging.6",
     "next": "^16.3.3",
     "react": "^19.2.7",
-    "react-dom": "^19.2.7"
+    "react-dom": "^19.2.7",
+    "zod": "^4.4.3"
   },
   "devDependencies": {
     "@types/node": "^24.12.0",

package/templates/react-router/package.json

@@ -21,11 +21,11 @@
     "cn": "0.2.4",
     "date-fns": "^4.1.0",
     "embla-carousel-react": "^8.6.0",
-    "fimo": "2.8.0-staging.5",
-    "fimo-analytics": "2.8.0-staging.5",
-    "fimo-react": "2.8.0-staging.5",
-    "fimo-react-router": "2.8.0-staging.5",
-    "fimo-vite": "2.8.0-staging.5",
+    "fimo": "2.8.0-staging.6",
+    "fimo-analytics": "2.8.0-staging.6",
+    "fimo-react": "2.8.0-staging.6",
+    "fimo-react-router": "2.8.0-staging.6",
+    "fimo-vite": "2.8.0-staging.6",
     "input-otp": "^1.4.2",
     "isbot": "^5",
     "lucide-react": "^0.577.0",

package/templates/sveltekit/package.json

@@ -11,9 +11,10 @@
     "prepare": "svelte-kit sync"
   },
   "dependencies": {
-    "fimo": "2.8.0-staging.5",
-    "fimo-analytics": "2.8.0-staging.5",
-    "fimo-sveltekit": "2.8.0-staging.5"
+    "fimo": "2.8.0-staging.6",
+    "fimo-analytics": "2.8.0-staging.6",
+    "fimo-sveltekit": "2.8.0-staging.6",
+    "zod": "^4.4.3"
   },
   "devDependencies": {
     "@sveltejs/kit": "^2.70.2",

package/templates/vite/package.json

@@ -11,14 +11,15 @@
   },
   "dependencies": {
     "@tanstack/react-query": "^5.80.6",
-    "fimo": "2.8.0-staging.5",
-    "fimo-analytics": "2.8.0-staging.5",
-    "fimo-react": "2.8.0-staging.5",
-    "fimo-react-router": "2.8.0-staging.5",
-    "fimo-vite": "2.8.0-staging.5",
+    "fimo": "2.8.0-staging.6",
+    "fimo-analytics": "2.8.0-staging.6",
+    "fimo-react": "2.8.0-staging.6",
+    "fimo-react-router": "2.8.0-staging.6",
+    "fimo-vite": "2.8.0-staging.6",
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
-    "react-router": "^8.3.0"
+    "react-router": "^8.3.0",
+    "zod": "^4.4.3"
   },
   "devDependencies": {
     "@types/react": "^19.2.14",

package/assets/skills/fimo-cli/references/inbox.md

@@ -1,86 +0,0 @@
-# Inbox
-
-The Inbox is what a project's agents tell the people on it: a run finished, a
-run left work for review, a merge conflicted, or a run stopped and is waiting
-for a decision. Only the last one can be acted on from the CLI.
-
-```bash
-fimo inbox list                              # unread first, then read
-fimo inbox list --topic agent_question --unread
-fimo inbox get <notification-id>             # the notification, plus the stored form when it is a question
-fimo inbox answer <notification-id> --body '<compact answer json>'
-```
-
-A notification id is the only id you ever hold. The question, its thread, the
-run it continues, and the Branch that run kept alive are resolved for you.
-
-Use `--project <id>` when there is no local `.fimo/project.json`. `--limit`,
-`--cursor`, and `--all-pages` page the list. `--archived` reads archived items;
-`--unread` stays in the unread stream instead of continuing into read items.
-
-## Answering is the person's decision, not yours
-
-**Never answer a question on someone's behalf.** A question exists because a run
-needed a human decision it could not make correctly. Answer only what the person
-in front of you explicitly chose.
-
-1. `fimo inbox list --topic agent_question --unread --json` to find waiting
-   questions, then `fimo inbox get <notification-id> --json` for the one to
-   answer. `data.question.form` is the stored form, verbatim.
-2. **Reproduce that form in the interface you are in** — the native form or
-   choice UI your harness offers, or a plain enumerated prompt when it offers
-   none. Keep the title, the description, the step order, the wording of every
-   question, every option label, the recommended option where one is marked,
-   image labels and URLs, and each capability's reason. The person is deciding
-   on what the agent actually asked, not on your summary of it.
-3. Collect only explicit answers. Do not default a step, infer one from earlier
-   conversation, or fill a step the person skipped. If the person already gave a
-   complete explicit answer, do not ask again — use what they said.
-4. **Never infer capability approval.** Selecting nothing on a capabilities step
-   is a deliberate deny-all, and omitting the step entirely is refused by the
-   CLI rather than read as a denial.
-5. Pass their notes through verbatim. The note is the one part of the answer
-   only they could write.
-6. Call `fimo inbox answer` once.
-
-## The compact answer
-
-Keyed by the step ids `inbox get` returned, in any order, one entry per step:
-
-```json
-{
-  "answers": [
-    { "stepId": "direction", "selected": ["Editorial studio"], "note": "Keep it calm." },
-    { "stepId": "access", "selected": [] },
-    { "stepId": "notes", "note": "Ship on Friday." }
-  ]
-}
-```
-
-- `selected` holds option **labels**, exactly as the form shows them.
-- `note` is free text. A step that offers options may be answered with a note
-  alone, with a selection alone, or with both.
-- A written step (`"type": "text"`) is answered with `note` only.
-- A capabilities step needs `selected`, empty or not. `[]` approves none.
-- Every step needs its own entry. Nothing is answered by omission.
-
-`--file <path>` and `--stdin` read the same JSON from a file or a pipe.
-
-## What the CLI refuses
-
-| Code                    | Why                                                                                                                                                                     |
-| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `INBOX_ANSWER_INVALID`  | Unknown or missing step, unoffered option, too many selections on a single-select, a written step answered by picking, or a capabilities step with no explicit decision |
-| `INBOX_NOT_A_QUESTION`  | The notification is a run outcome, a review, or a conflict — there is nothing to answer                                                                                 |
-| `INBOX_QUESTION_CLOSED` | Already answered, expired, cancelled, or superseded                                                                                                                     |
-| `INBOX_UNKNOWN_TOPIC`   | `--topic` is not one of the four Inbox topics                                                                                                                           |
-| `INBOX_INVALID_CURSOR`  | `--cursor` was not the `nextCursor` from a previous page                                                                                                                |
-| `INBOX_NOT_FOUND`       | No notification with that id is addressed to you in this project                                                                                                        |
-
-A question is answered once. Answering it starts exactly one continuation run,
-and re-sending the same answer never starts a second one.
-
-## What the CLI does not do
-
-Marking read, archiving, restoring, reviewing retained work, and resolving merge
-conflicts happen in the Fimo Inbox UI. `fimo inbox` reads and answers.