docs: sync AI_CURATOR_RECIPE with CLI skeleton

Author: Arturo R Montesinos

AI_CURATOR_RECIPE.md

@@ -21,17 +21,19 @@ curated_by: arturo
 ## 2) Product Contract (plain language) <!-- @curator:required -->
 
 Describe the externally visible behavior of the CLI.
-For now, this is aspirational and aligned with `docs/curation/BLUEPRINT.md`.
+This section reflects the **currently implemented skeleton** plus
+near-term intent from `docs/curation/BLUEPRINT.md`.
 
 | Aspect | Description |
 |--------|-------------|
-| **Inputs** | CLI invocation `odsview <file.ods> [options]` (TBD), filesystem `.ods` files |
-| **Outputs/streams** | `stdout` → human-readable table or metadata; `stderr` → diagnostics and error messages |
-| **Exit codes** | `0` on success; non-zero for invalid CLI usage, file-not-found, parse errors, and internal failures (exact mapping TBD) |
-| **Determinism** | Given the same file, CLI options, and environment, output is deterministic (no randomness; locale and encoding rules to be defined in Appendix A) |
+| **Inputs** | CLI invocation `odsview [FILE] [options]`; `FILE` is optional in the current skeleton |
+| **Outputs/streams** | `stdout` → help/usage text (currently); `stderr` → diagnostics and error messages (future work) |
+| **Exit codes** | `0` on success (e.g. `--help` or no arguments); `2` for CLI usage errors such as attempting to view a file before viewing is implemented |
+| **Determinism** | Given the same CLI arguments and environment, help/usage output is deterministic; data rendering determinism will be specified alongside the first real viewing implementation in Appendix A |
 
-> Appendix A will refine these contracts once the first CLI behavior and
-> tests are implemented.
+As of this milestone, the CLI is **read-only and non-functional for
+actual `.ods` viewing**; attempting to pass a file path results in a
+usage error indicating that viewing is not implemented yet.
 
 ## 3) Curation Principles <!-- @curator:required -->
 - AI drafts; human curator approves and is accountable.
@@ -108,15 +110,32 @@ Curator docs under `docs/curation/` are validated via `scripts/validate_recipe.p
   first end-to-end tests.
 
 ## Appendix A — Project-Specific Contracts <!-- @curator:required -->
-- **CLI entrypoint**: TBD (likely `odsview` console script).
+
+**Current implemented behavior (skeleton)**
+
+- **CLI entrypoint**: `odsview` console script (via `pyproject.toml`).
+- **Inputs**:
+  - No arguments → prints help to `stdout`, exits with code `0`.
+  - `--help` → prints help to `stdout`, exits with code `0`.
+  - `FILE` argument → currently treated as unsupported; the CLI reports
+    that viewing `.ods` files is not implemented yet and exits with a
+    non-zero usage error code (`2`).
+- **Outputs**:
+  - Help/usage text only; no data rendering yet.
+- **Invariants (even at this stage)**:
+  - Never mutates any input file.
+  - Avoids interactive prompts by default.
+
+**Planned behavior (not yet implemented, subject to future ADRs)**
+
 - **Inputs**: `.ods` file path; optional flags for sheet selection,
-  max rows, and display options (to be formalized).
+  max rows, and display options.
 - **Outputs**: Human-readable table on `stdout` with truncation rules for
   very wide or long sheets.
 - **Invariants**:
   - Never mutates the source file.
   - Fails fast and clearly on unreadable or unsupported files.
   - Avoids interactive prompts by default (suitable for automation).
 
-These contracts will be refined and linked to concrete tests and ADRs as the
-implementation emerges.
+Planned contracts become authoritative only once backed by tests and,
+where appropriate, ADRs.