ekwo-os 0.15.0 → 0.16.0

package/README.md

@@ -48,7 +48,7 @@ You need Node 20 or later. No Supabase CLI, no Docker.
    the language.
 
 4. **Sign in** as that administrator and start booking — in the web
-   application, [Ekwo Cloud](https://cloud.ekwo.ai), which opens your own
+   application, [Ekwo Cloud](https://cloud.ekwo.ai/signup?src=cli), which opens your own
    instance; through an AI agent and the [MCP server](../mcp/README.md); from
    this command line; or through the REST API Supabase generates.
 
@@ -168,7 +168,7 @@ project reports what was already there and creates nothing a second time.
 | `ekwo use <company>` | Picks the company the next commands run on. |
 | `ekwo whoami` | Who you are on which instance, the companies you can see, and what you may do on the one in use. |
 | `ekwo contact add` / `list` | A customer or a supplier, and finding one again. |
-| `ekwo contact duplicates` | The pairs of contacts that are probably one party, strongest first, through `suggest_duplicate_contacts()`: which one to keep, a score, and the evidence — the same VAT or registration number, the same bank account, the same words of the name. Writes nothing. |
+| `ekwo contact duplicates` | The pairs of contacts that are probably one party, strongest first, through `suggest_duplicate_contacts()`: which one to keep, a score, and the evidence — the same VAT or registration number, the same bank account, the words of the name weighed by how few contacts carry them. Writes nothing. |
 | `ekwo contact merge <keep> <absorb>` | One party created twice — two spellings, two imports — joined through `merge_contacts()`: everything that names the second, posted lines and issued documents included, names the first; the first takes the fields it left empty; the second is retired, never deleted, and named by nothing again. By name or id. |
 | `ekwo doc new` / `doc line add` | A draft document — any kind, with `--type` — and one more line on it. A draft books nothing. `ekwo invoice` is the old name of `ekwo doc`, kept as an alias. |
 | `ekwo post <document>` | Books it, through `post_document()`. `--dry-run` shows the entry the database would write and writes nothing. |
@@ -186,7 +186,7 @@ project reports what was already there and creates nothing a second time.
 | `ekwo proof stamp` / `upgrade` / `verify` | The sha256 of a filed file — a declaration, the annual accounts of a financial year, a document — committed to Bitcoin through the public OpenTimestamps calendars; only the hash leaves. `upgrade` completes the pending proofs of the company and is made to run on a schedule; `verify` checks a file against its proof and the block it names, and `--out` writes the `.ots` file any verifier reads. See [`docs/filing-proofs.md`](../../docs/filing-proofs.md). |
 | `ekwo einvoice validate` / `issue` / `status` / `list` | The electronic invoice of a posted sale, in the format its country pack declares, through the `einvoicing` module: `validate` writes it and names the rules it breaks (exit 1 if any), `issue` keeps it and with `--send --to <directory>` writes it to that folder, `status --refresh` follows it. See [`modules/einvoicing`](../../modules/einvoicing/README.md). |
 | `ekwo einvoice fiscalise` / `fiscalisation` | The fiscal record a country's fiscalisation regime requires for every invoice — VERI*FACTU is one — written by the brick its pack names and chained after the last record of the invoicing system described by `--system <file>` (or `EKWO_FISCAL_SYSTEM`); `--dry-run` writes it and chains nothing, a record that breaks a rule is never chained (exit 1). `fiscalisation` walks each chain, and names the records still to send and the posted sales without a record. |
-| `ekwo einvoice clearance <document> submitted\|validated\|rejected\|cancelled` | Under a clearance regime — the authority validates every invoice before it is issued — records what happened to a posted sale: its submission (`--reference`, `--issue`), the authority's validation (`--identifier`, `--validated-at`, `--verification-url`), a rejection by the authority or the buyer (`--reason`, `--by`), its cancellation (`--reason`), each `--at` a moment, `--detail <file>` the answer as JSON. It dials nobody; the database refuses a transition that cannot have happened, and a window of the pack that has closed. `fiscalisation` then counts the sales validated, waiting, rejected and cancelled. |
+| `ekwo einvoice clearance <document> submitted\|validated\|rejected\|cancelled` | Under a clearance regime — the authority validates every invoice before it is issued — records what happened to a posted sale: its submission (`--reference`, `--issue`), the authority's validation (`--identifier`, `--validated-at`, `--verification-url` — or, where the pack builds the link, `--detail` and `--environment`), a rejection by the authority or the buyer (`--reason`, `--by`), its cancellation (`--reason`), each `--at` a moment, `--detail <file>` the answer as JSON. It dials nobody; the database refuses a transition that cannot have happened, and a window of the pack that has closed. `fiscalisation` then counts the sales validated, waiting, rejected and cancelled. |
 | `ekwo peppol validate <file>` / `lookup <participant>` | The Peppol network, with no installation and no sign-in. `validate` reads a UBL invoice or credit note as it arrived and names the rules it breaks — the arithmetic of EN 16931 and the electronic addresses of both parties — with exit 1 if any; nothing is booked. `lookup` checks a participant identifier (`0208:0999999922`, `iso6523-actorid-upis::…` or a symbolic scheme) and asks the DNS of the Service Metadata Locator whether it is registered, and with which Service Metadata Publisher; `--test` asks the acceptance network. Exit 0 only for a registered participant. See [`@ekwo-ai/peppol-ubl`](../formats/peppol-ubl/README.md#participant-identifiers-and-the-sml). |
 
 There is no `eject`, because there is nothing to eject from. The schema is in
@@ -482,6 +482,7 @@ Every command takes `--json`; see [what a command answers](#what-a-command-answe
 | `EKWO_CONFIG_DIR` | Where profiles and sessions are kept. |
 | `EKWO_REGISTRY_URL` | `--registry-url`. Default `https://api.ekwo.ai/v1/registrations`. |
 | `EKWO_NO_REGISTER_INVITE` | Set to `1` to hide the invitation to register that `ekwo init` and `ekwo status` show on an installation that is not registered. The MCP server reads it too. |
+| `EKWO_NO_CLOUD_OFFER` | Set to `1` to hide the one line offering a free Ekwo Cloud account. The MCP server reads it too. See [An Ekwo Cloud account](#an-ekwo-cloud-account-optional). |
 | `NO_COLOR` | Plain output. |
 
 See [`.env.example`](../../.env.example) at the root of the repository.
@@ -528,7 +529,7 @@ exactly six fields:
   "organization": "My Organisation",
   "country": "<cc>",
   "edition": "community",
-  "schema_version": "0.15.0",
+  "schema_version": "0.16.0",
   "contact_email": "you@example.com"
 }
 ```
@@ -538,6 +539,25 @@ by your own database and is not a licence key. A failed announcement is a soft
 message, not a failed install: `ekwo register` retries it. `ekwo unregister`
 clears the local fields.
 
+## An Ekwo Cloud account (optional)
+
+Everything above works without an account, and always will. A free account on
+[Ekwo Cloud](https://cloud.ekwo.ai/signup?src=cli) — an address and a
+six-digit code, no password to invent — adds the web application on the same
+books, a nightly backup of every company you link, and one connector URL,
+`https://mcp.ekwo.ai/mcp`, for your AI agent, approved in your browser, instead
+of a key and a password in a file.
+
+The command line says so in one line, at two moments: at the end of an
+`ekwo init` that succeeded, and after a first `ekwo company export`. Each
+moment once for you: it is remembered in `settings.json`, in your
+configuration directory beside your profiles, and nothing is sent to Ekwo to
+show it or to remember it. The line is never shown under `--json`, when the
+output is not a terminal, or in CI (`CI` set). `EKWO_NO_CLOUD_OFFER=1` hides
+it, and so does `"cloud_offer": false` in that `settings.json`, for good. The
+MCP server carries the same words in its instructions; see
+[its README](../mcp/README.md#what-an-agent-reads-first).
+
 ## Testing it against a real project
 
 The test suite runs against Postgres compiled to WebAssembly. To exercise the