fimo 2.0.1 → 2.1.0-staging.2

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

@@ -147,6 +147,41 @@ When three or more earlier runs still await a question answer, review, conflict
 normally starts no new independent work. Unless the current trigger explicitly asks it to proceed anyway, it makes no
 changes and finishes with `discard` and a brief report of what is waiting.
 
+## Define reporting preferences when they matter
+
+Fimo's default report needs no setup: a short, scannable brief appears in email and the Inbox, while the full report in
+Fimo carries the organized evidence and depth. Do not add a reporting section merely to restate that default.
+
+When the user names an audience, depth, recurring comparison, required section, or useful visual, preserve the request
+in a short **Reporting** section of `GOAL.md`. Describe the communication outcome in ordinary language. Do not prescribe
+report block arrays or promise that the full report will appear in email.
+
+Examples for different jobs:
+
+```md
+## Reporting
+
+Write the brief for a marketing lead. Lead with the outcome and at most three decisions or risks. Keep implementation
+evidence in the full report.
+```
+
+```md
+## Reporting
+
+Compare this week with the previous four weeks. Use a graph only when the change over time is part of the conclusion,
+and include the complete channel breakdown in the full report.
+```
+
+```md
+## Reporting
+
+Show enough of each created article to judge its voice, then link to the draft. Preserve the complete copy and editorial
+decisions in the full report.
+```
+
+These are preferences, not templates. Keep the default brief short and scannable unless the user asks for a different
+audience or emphasis. Even then, the brief remains the external handoff and the full report holds the supporting depth.
+
 ## Capabilities
 
 Capabilities describe the opt-in Fimo and network actions an agent may take. Managed agents always receive project
@@ -213,7 +248,7 @@ fimo agents logs <name> [--session <id>] [--project <id>] [-C <dir>]
 
 - **`run <name>`** — fire the agent's `manual` trigger on the server; prints a `sessionId` on success. Skips with `no-manual-trigger` when `config.yaml` declares none, or `trigger-not-wired` when the push-to-main sync recorded the trigger but refused to wire it (see the wiring note below). **Pre-flight drift check**: if `.fimo/agents/<name>/` (or the legacy root bundle) has uncommitted git changes, the command refuses — the server would dispatch the _deployed_ version, so deploy first. Pass `--skip-drift-check` to dispatch the deployed bundle anyway. Defaults `--branch` to `main`; legacy `--env` remains an alias.
 - **`runs <name>`** — list past run sessions for the agent in a compact table (id, started, duration, status, trigger, Branch, cost). Default `--limit 20`; `--branch` filters to one Branch. The response's legacy `env` field is still present for API compatibility.
-- **`report <name>`** — print a run's **report**: its durable outcome summary (for a read-only agent like `seo-audit` this _is_ the audit; for a write agent it's a "what I changed" summary). A run that never finalised falls back to its last message. With no `--session`, the most recent run for `<name>` is used (combine with `--branch` to scope); `--session <id>` targets a specific run. Output is raw markdown, so it stays readable in the terminal and pipes cleanly (e.g. `fimo agents report seo-audit | glow`). If the run hasn't finished, or produced no message, it says so (and shows the stop reason when there is one). This is the command to read what a run actually produced — see the `logs` note below.
+- **`report <name>`** — print a run's structured **report**: its durable outcome summary (for a read-only agent like `seo-audit` this _is_ the audit; for a write agent it's a "what I changed" summary). A run that returns plain text without calling `finish_run` receives a small structured fallback document. With no `--session`, the most recent run for `<name>` is used (combine with `--branch` to scope); `--session <id>` targets a specific run. Output is projected Markdown, so it stays readable in the terminal and pipes cleanly (e.g. `fimo agents report seo-audit | glow`). If the run hasn't finished, or produced no report, it says so (and shows the stop reason when there is one). This is the command to read what a run actually produced — see the `logs` note below.
 - **`logs <name>`** — stream a run's log (defaults to the latest session; `--session <id>` targets one). **Note:** the log-streaming endpoint is still a server-side stub at time of writing — the command prints a placeholder rather than real log lines. To read a finished run's output today, use `report`.
 
 ## How triggers get wired

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-25T13:35:26.794Z",
+  "bundledAt": "2026-08-26T09:59:57.972Z",
   "cliVersion": "2.0.1",
   "external": [
     "oxc-parser",