@flowmind/cli 0.3.8 → 0.3.9

package/README.md

@@ -181,13 +181,15 @@ An ordinary prompt and stop still count; a restart or a gap longer than 12 hours
 
 Upgrading from 0.3.7 needs no new sign-in. A never-bound profile asks the API which account owns its
 stored key (`GET /v1/me`, once). A previously bound key whose credential or origin no longer matches
-is refused locally. Every 0.3.7 proof stays in its original location regardless of timestamps. The
-`unowned` list in `agent pending` shows only neutral metadata. Check Activity before adopting a proof
-that is yours with `flowmind agent adopt <id>`. Only then can it replay its original origin, body and key.
-Use `flowmind agent discard <id>` to delete an unowned proof without sending it. Session
-time recorded by 0.3.7 is not adopted. A revoked key asks you to sign in; an unreachable API reports that the
-account could not be verified and changes nothing. On POSIX the config directory is 0700 and its credential file
-is 0600, including when repairing an older config.
+is refused locally. While a profile has only ever been signed in to one account, which is the normal case
+of one person on their own machine, the session time and saved proofs that 0.3.7 recorded become that
+account's on the first command or hook after the upgrade: an agent session that was running during the
+upgrade stages its whole time as before, and saved proofs are sent with the others. On a profile that has
+switched accounts, 0.3.7 proofs stay in their original location and the `unowned` list in `agent pending`
+shows only neutral metadata. Check Activity before adopting a proof that is yours with
+`flowmind agent adopt <id>`, or delete it unsent with `flowmind agent discard <id>`. A revoked key asks you to
+sign in; an unreachable API reports that the account could not be verified and changes nothing. On POSIX the
+config directory is 0700 and its credential file is 0600, including when repairing an older config.
 
 ## Momentum brief
 
@@ -251,7 +253,7 @@ A valid API rejection also exits with status 1.
 One diagnostic names the action, operation, schema location, and request ID when available.
 Diagnostics omit response values, credentials, query values, and server messages.
 
-A personal log with a transport failure, timeout, or unreadable response is not confirmed. The CLI does not retry it automatically. Run the same log command to replay its saved fields and key. A natural log reuses what you already reviewed. After the 24-hour receipt window the same command is refused, because the server may no longer recognize the key. Check Activity, then close the saved log with `flowmind pending-logs done <id>` when the entry is there, or `flowmind pending-logs discard <id>` to log the work again. `flowmind pending-logs` lists the saved logs; neither action posts anything. Supply hours as a decimal such as `1.5`; commas and unit suffixes are refused.
+A personal log with a transport failure, timeout, or unreadable response is not confirmed. The CLI does not retry it automatically. Run the same log command to replay its saved fields and key. A natural log reuses what you already reviewed. After the 24-hour receipt window the same command is refused, because the server may no longer recognize the key. Check Activity, then close the saved log with `flowmind pending-logs done <id>` when the entry is there, or `flowmind pending-logs discard <id>` to log the work again. `flowmind pending-logs` lists the saved logs; neither action posts anything. `--hours` takes hours or minutes: `1.5`, `1,5`, `2h`, `90m` or `1h30m`, rounded to the nearest minute. Anything else is refused before a request.
 Authentication stops immediately on a failed poll. Pending authorization continues polling.
 Expired authorization exits with status 1. No failed authorization saves a credential.
 Use `fm auth login --no-browser` to open the printed authorization URL yourself.

package/dist/flowmind/SKILL.md

@@ -61,7 +61,7 @@ flowmind agent stage --intention "<what you set out to do>" --outcome "<one line
 - `"reason": "saved"` means that the server did not take the proof yet, for example because Flowmind was unreachable, a limit was reached, or its answer could not be read. The CLI saved it on this machine and sends it automatically: after the next accepted stage, or in the background from the session hooks. Its time already counts as staged. Do not stage it again, do not invent another `--idempotency-key`, and tell the user it waits to be sent.
 - A refused credential also keeps the proof saved, but exits with an error: the user must run `flowmind auth login`. A proof that the server refuses for its content (too long, unknown project) is not saved; fix it and stage again.
 - A stage key conflict means delivery is unknown. The file and its time stay reserved. Tell the owner to check Activity, then retry with the original credential or discard the file with `flowmind agent discard <id>`. Do not stage the same work again. `agent retry --json` lists unresolved `conflicts`.
-- `flowmind agent pending --json` lists this signed-in account’s proofs saved on this machine; `flowmind agent retry --json` sends them now. `unowned` lists neutral metadata for every proof saved by the older CLI; tell the user, who decides with `flowmind agent adopt <id>` or `flowmind agent discard <id>`.
+- `flowmind agent pending --json` lists this signed-in account’s proofs saved on this machine; `flowmind agent retry --json` sends them now. Proofs and session time from CLI 0.3.7 join the account automatically on a machine that has only used one account. `unowned` appears only after an account switch: it lists neutral metadata for proofs saved by the older CLI; tell the user, who decides with `flowmind agent adopt <id>` or `flowmind agent discard <id>`.
 - After 20 minutes of unstaged agent time, each prompt in a linked repository carries a reminder with the unstaged minutes. Stage when the current unit of work is complete; a stage with explicit times also resets the count.
 - Add `--dry-run` to preview the project and minutes without staging.
 - Pass `--project`, `--minutes`, and `--started-at` only when no session record exists. Use observed times only. Never estimate time from tokens or tool calls.