@cspeach/cli 0.9.0 → 1.1.0

package/dist/ui/widgets/ask-question-modal.js

@@ -17,8 +17,18 @@ import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
  */
 import { useState, useEffect } from 'react';
 import { Box, Text, useInput } from 'ink';
-import TextInput from 'ink-text-input';
+// D29 paste fix (2026-06-12): paste-safe replacement for ink-text-input —
+// pasted free-form answers were losing every chunk but the last on large
+// pastes (stale-prop closure upstream). See ../text-input.tsx.
+import TextInput from '../text-input.js';
 const PEACH = '#FFCBA4';
+export function askHelpLine(kind, opts) {
+    switch (kind) {
+        case 'multi': return 'Space toggle · Enter confirm · Esc cancel';
+        case 'pick': return opts?.single ? 'Enter pick · Esc cancel' : 'Enter pick · Tab next · Esc cancel';
+        default: return opts?.single ? 'Enter submit · Esc cancel' : 'Tab next · Esc cancel';
+    }
+}
 /**
  * Reclaim raw-mode stdin when an Ink modal mounts (2026-06-08).
  *
@@ -30,8 +40,11 @@ const PEACH = '#FFCBA4';
  * answer the question. Re-syncing the OS state to what Ink expects on mount
  * fixes it. Direct `process.stdin` calls (not Ink's ref-counted setRawMode)
  * because the whole problem is that Ink's count is stale.
+ *
+ * Exported (UX Wave 2 / Task 2) so <AskForm> — the v2 multi-question form —
+ * reuses the exact same reclaim on mount. v1 rendering is untouched.
  */
-function useReclaimRawStdin() {
+export function useReclaimRawStdin() {
     useEffect(() => {
         const stdin = process.stdin;
         if (stdin.isTTY && typeof stdin.setRawMode === 'function') {
@@ -63,7 +76,7 @@ function TextInputForm({ params, onResolve }) {
             onResolve({ answer: null, cancelled: true });
         }
     }, { isActive: true });
-    return (_jsxs(Box, { borderStyle: "round", borderColor: PEACH, flexDirection: "column", paddingX: 1, flexShrink: 0, children: [_jsx(Text, { bold: true, children: params.question }), params.context && (_jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: params.context }) })), _jsxs(Box, { marginTop: 1, children: [_jsx(Text, { color: PEACH, children: '> ' }), _jsx(TextInput, { value: value, onChange: setValue, onSubmit: (v) => {
+    return (_jsxs(Box, { flexDirection: "column", paddingX: 1, flexShrink: 0, children: [_jsx(Text, { bold: true, children: params.question }), params.context && (_jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: params.context }) })), _jsxs(Box, { marginTop: 1, children: [_jsx(Text, { color: PEACH, children: '> ' }), _jsx(TextInput, { value: value, onChange: setValue, onSubmit: (v) => {
                             const trimmed = v.trim();
                             if (trimmed.length === 0) {
                                 onResolve({ answer: null, cancelled: true });
@@ -71,7 +84,7 @@ function TextInputForm({ params, onResolve }) {
                             else {
                                 onResolve({ answer: trimmed });
                             }
-                        } })] }), _jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: "Enter to submit \u00B7 Esc to cancel" }) })] }));
+                        } })] }), _jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: askHelpLine('freeText', { single: true }) }) })] }));
 }
 // ---------------------------------------------------------------------------
 // Single choice (kind = 'choice')
@@ -97,10 +110,10 @@ function ChoiceForm({ params, onResolve }) {
                 onResolve({ answer: chosen.value });
         }
     }, { isActive: true });
-    return (_jsxs(Box, { borderStyle: "round", borderColor: PEACH, flexDirection: "column", paddingX: 1, flexShrink: 0, children: [_jsx(Text, { bold: true, children: params.question }), params.context && (_jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: params.context }) })), _jsx(Box, { marginTop: 1, flexDirection: "column", children: params.choices.map((c, i) => {
+    return (_jsxs(Box, { flexDirection: "column", paddingX: 1, flexShrink: 0, children: [_jsx(Text, { bold: true, children: params.question }), params.context && (_jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: params.context }) })), _jsx(Box, { marginTop: 1, flexDirection: "column", children: params.choices.map((c, i) => {
                     const isCursor = i === cursor;
                     return (_jsxs(Text, { color: isCursor ? PEACH : undefined, bold: isCursor, children: [isCursor ? '▸ ' : '  ', c.label] }, c.value));
-                }) }), _jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: "\u2191/\u2193 navigate \u00B7 Enter select \u00B7 Esc cancel" }) })] }));
+                }) }), _jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: askHelpLine('pick', { single: true }) }) })] }));
 }
 // ---------------------------------------------------------------------------
 // Multi choice (kind = 'multi') — space to toggle, Enter to submit
@@ -147,11 +160,11 @@ function MultiForm({ params, onResolve }) {
             }
         }
     }, { isActive: true });
-    return (_jsxs(Box, { borderStyle: "round", borderColor: PEACH, flexDirection: "column", paddingX: 1, flexShrink: 0, children: [_jsx(Text, { bold: true, children: params.question }), params.context && (_jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: params.context }) })), _jsx(Box, { marginTop: 1, flexDirection: "column", children: params.choices.map((c, i) => {
+    return (_jsxs(Box, { flexDirection: "column", paddingX: 1, flexShrink: 0, children: [_jsx(Text, { bold: true, children: params.question }), params.context && (_jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: params.context }) })), _jsx(Box, { marginTop: 1, flexDirection: "column", children: params.choices.map((c, i) => {
                     const isCursor = i === cursor;
                     const isSelected = selected.has(c.value);
                     const mark = isSelected ? '◉' : '○';
                     const prefix = isCursor ? '▸ ' : '  ';
                     return (_jsxs(Text, { color: isCursor ? PEACH : undefined, bold: isCursor, children: [prefix, mark, " ", c.label] }, c.value));
-                }) }), _jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: "\u2191/\u2193 navigate \u00B7 Space toggle \u00B7 Enter submit \u00B7 Esc cancel" }) })] }));
+                }) }), _jsx(Box, { marginTop: 1, children: _jsx(Text, { dimColor: true, children: askHelpLine('multi') }) })] }));
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cspeach/cli",
-  "version": "0.9.0",
+  "version": "1.1.0",
   "description": "CSPeach — AI-assisted ABAP development CLI. Direct SAP access, 34 skills, safety gates.",
   "keywords": [
     "abap",
@@ -41,42 +41,61 @@
     "smoke:all": "pnpm zcspeach:smoke && pnpm adt:smoke",
     "zcspeach:smoke": "tsx scripts/zcspeach-smoke.ts",
     "bench:models": "tsx scripts/bench-models.ts",
-    "prepare": "husky"
+    "bench:audit": "tsx scripts/bench-audit-task.ts",
+    "fiori": "tsx src/tools/fiori/bin.ts",
+    "prepare": "husky",
+    "prepublishOnly": "node -e \"const d=(require('./package.json').dependencies||{})['@cspeach/sap-client']||''; if(d.startsWith('file:')||d.startsWith('link:')){console.error('publish blocked: @cspeach/sap-client is a local link ('+d+') — point it at the published version before npm publish'); process.exit(1)}\""
   },
   "engines": {
     "node": ">=20.0.0"
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.90.0",
-    "@cspeach/sap-client": "^0.1.3",
+    "@cspeach/sap-client": "^0.1.10",
     "@iarna/toml": "^2.2.5",
     "@inkjs/ui": "^2.0.0",
     "@inquirer/prompts": "^7.0.0",
     "@noble/ed25519": "2.1.0",
     "@noble/hashes": "1.4.0",
+    "@sap-ux/fe-fpm-writer": "0.43.7",
+    "@sap-ux/fiori-elements-writer": "^3.0.39",
+    "@sap-ux/fiori-freestyle-writer": "3.0.12",
     "chalk": "^5.3.0",
     "cli-highlight": "^2.1.11",
     "cli-table3": "^0.6.5",
     "clipboardy": "^5.3.1",
+    "cross-spawn": "^7.0.6",
     "diff": "^9.0.0",
+    "ejs": "3.1.10",
     "fuse.js": "^7.0.0",
     "ink": "^5.0.0",
     "ink-text-input": "^6.0.0",
     "jose": "^5.9.0",
     "keytar": "^7.9.0",
+    "mammoth": "^1.8.0",
     "marked": "^11.2.0",
     "marked-terminal": "^6.2.0",
+    "mem-fs": "2.1.0",
+    "mem-fs-editor": "9.4.0",
     "node-machine-id": "^1.1.12",
     "openai": "4.67.3",
+    "puppeteer-core": "24.10.2",
     "react": "^18.3.0",
+    "turndown": "^7.2.0",
+    "unpdf": "^0.12.1",
     "zod": "^3.23.0"
   },
   "devDependencies": {
+    "@types/cross-spawn": "^6.0.6",
     "@types/diff": "^7.0.2",
+    "@types/ejs": "^3.1.5",
     "@types/node": "^20.17.0",
     "@types/react": "^18.3.0",
+    "@types/turndown": "^5.0.5",
+    "docx": "^9.0.2",
     "husky": "^9.1.7",
     "ink-testing-library": "^4.0.0",
+    "pdf-lib": "^1.17.1",
     "tsx": "^4.19.0",
     "typescript": "^5.7.0",
     "vitest": "^2.1.0"

package/bench/README.md

@@ -1,78 +0,0 @@
-# Model bench
-
-Side-by-side outputs from Opus, Sonnet, and Haiku on the same ABAP prompt so
-you can decide per-skill which model carries the load before changing any
-default.
-
-## Run
-
-```bash
-pnpm bench:models
-pnpm bench:models --prompt abap-explain-bdef-handler
-pnpm bench:models --models claude-opus-4-7,claude-sonnet-4-6
-```
-
-Routes through whichever LLM mode `cspeach config` is in — managed (proxy),
-BYOK, AI Hub, or local. In managed mode the proxy injects the **real skill
-body from KV** as the system prompt, so each bench call is end-to-end
-identical to what a real `/abap-explain` invocation would do — just on a
-different model.
-
-## Prompts
-
-Drop new prompts in `prompts/<name>.md`. Format:
-
-```markdown
----
-skill: abap-explain          # required — must be a real CSPeach skill name
-description: short label
----
-
-## user
-[the user-side prompt the model receives]
-```
-
-Optionally include a `## system` section — it's **only** used in non-managed
-modes (BYOK, AI Hub, local) where there's no proxy to inject a skill body.
-In managed mode `## system` is ignored.
-
-## Results
-
-`results/<prompt-name>/<model>.md` — full assistant text plus latency, tokens,
-and a USD estimate (using the same pricing table the cost footer uses).
-
-Read both files side by side. If Sonnet looks like a write-off on a given
-skill, keep the skill on Opus. If it looks "as good or better," that skill
-graduates down on the next config refactor.
-
-## Cost note
-
-Each prompt × model call is one full skill turn through the proxy. The proxy
-loads the full skill body as system prompt, so input is in the 5-15k token
-range. A full 3-prompt × 3-model bench is roughly $0.30–$0.80 depending on
-output verbosity. (Haiku columns will be much cheaper than Opus.)
-
-## Verdict log
-
-Findings from each bench run, oldest first. Each entry should name the run
-date, the prompts that were benched, and the model decision per skill — so
-the config refactor (`resolveModelForSkill` + `[models.skills]`) can be
-driven from evidence, not guesses.
-
-### 2026-05-18 — initial 3-prompt run
-
-Prompts: `abap-explain-bdef-handler`, `abap-document-cds`, `abap-test-method`.
-
-| Skill | Sonnet 4.6 | Haiku 4.5 | Decision |
-|---|---|---|---|
-| `abap-explain`  | matches Opus, catches `IN LOCAL MODE` non-retrigger nuance | typo `cl_abap_behav_handler` (wrong class name) | **Sonnet OK; Haiku unsafe** |
-| `abap-document` | matches Opus + adds client-handling + `@VDM.viewType` value | invented `DSOD` authority object; misread fuzzinessThreshold direction | **Sonnet OK; Haiku unsafe** |
-| `abap-test`     | comparable rigor; asserts exception **textid** (Opus only `assert_bound`) | clean code; coverage-estimate prose shaky | **Sonnet OK; Haiku borderline** |
-
-Pattern: SAP/ABAP corpus is thinner than Python/JS — Haiku hallucinates SAP
-terms on multi-paragraph synthesis. Sonnet does not. Do NOT route any
-ABAP-content skill to Haiku based on this evidence.
-
-Skills NOT yet benched (kept on Opus by default): `abap-generate`, `-rap`,
-`-modernize`, `-design`, `-refactor`, `-review`, `-cca`, anything else
-producing new code or architectural decisions. Bench before routing.

package/bench/prompts/abap-document-cds.md

@@ -1,44 +0,0 @@
----
-skill: abap-document
-description: Document a CDS interface view with associations + currency annotation
----
-
-## user
-
-Please document this CDS view:
-
-```cds
-@AccessControl.authorizationCheck: #CHECK
-@EndUserText.label: 'Sales Order — Interface View'
-@Search.searchable: true
-define view entity ZI_SalesOrder
-  as select from zsales_order as Header
-
-  association [0..1] to ZI_Customer       as _Customer       on $projection.CustomerID = _Customer.CustomerID
-  association [0..*] to ZI_SalesOrderItem as _SalesOrderItem on $projection.SalesOrderID = _SalesOrderItem.SalesOrderID
-  association [0..1] to I_Currency        as _Currency       on $projection.CurrencyCode = _Currency.Currency
-
-{
-  key Header.sales_order_id        as SalesOrderID,
-      Header.customer_id           as CustomerID,
-      Header.order_date            as OrderDate,
-
-      @Search.defaultSearchElement: true
-      @Search.fuzzinessThreshold: 0.8
-      @ObjectModel.text.element: [ '_Customer.CustomerName' ]
-      Header.customer_id           as CustomerIDForSearch,
-
-      @Semantics.amount.currencyCode: 'CurrencyCode'
-      Header.net_amount            as NetAmount,
-      Header.currency_code         as CurrencyCode,
-
-      Header.created_at            as CreatedAt,
-      Header.created_by            as CreatedBy,
-      Header.last_changed_at       as LastChangedAt,
-      Header.last_changed_by       as LastChangedBy,
-
-      _Customer,
-      _SalesOrderItem,
-      _Currency
-}
-```

package/bench/prompts/abap-explain-bdef-handler.md

@@ -1,57 +0,0 @@
----
-skill: abap-explain
-description: Explain a managed RAP behavior pool with a validation + determination
----
-
-## user
-
-Please explain this behavior pool:
-
-```abap
-CLASS lhc_salesorder DEFINITION INHERITING FROM cl_abap_behavior_handler.
-  PRIVATE SECTION.
-    METHODS validateorderdate FOR VALIDATE ON SAVE
-      IMPORTING keys FOR SalesOrder~validateorderdate.
-    METHODS determinenetamount FOR DETERMINE ON MODIFY
-      IMPORTING keys FOR SalesOrder~determinenetamount.
-ENDCLASS.
-
-CLASS lhc_salesorder IMPLEMENTATION.
-  METHOD validateorderdate.
-    READ ENTITIES OF zr_salesorder IN LOCAL MODE
-      ENTITY SalesOrder FIELDS ( OrderDate ) WITH CORRESPONDING #( keys )
-      RESULT DATA(lt_orders).
-
-    LOOP AT lt_orders INTO DATA(ls_order).
-      IF ls_order-OrderDate < cl_abap_context_info=>get_system_date( ).
-        APPEND VALUE #( %tky = ls_order-%tky ) TO failed-salesorder.
-        APPEND VALUE #(
-          %tky = ls_order-%tky
-          %msg = new_message_with_text(
-                   severity = if_abap_behv_message=>severity-error
-                   text     = 'Order date must be today or in the future' )
-        ) TO reported-salesorder.
-      ENDIF.
-    ENDLOOP.
-  ENDMETHOD.
-
-  METHOD determinenetamount.
-    READ ENTITIES OF zr_salesorder IN LOCAL MODE
-      ENTITY SalesOrder FIELDS ( Quantity UnitPrice ) WITH CORRESPONDING #( keys )
-      RESULT DATA(lt_orders).
-
-    DATA lt_update TYPE TABLE FOR UPDATE zr_salesorder\\SalesOrder.
-    LOOP AT lt_orders INTO DATA(ls_order).
-      APPEND VALUE #(
-        %tky      = ls_order-%tky
-        NetAmount = ls_order-Quantity * ls_order-UnitPrice
-        %control-NetAmount = if_abap_behv=>mk-on
-      ) TO lt_update.
-    ENDLOOP.
-
-    MODIFY ENTITIES OF zr_salesorder IN LOCAL MODE
-      ENTITY SalesOrder UPDATE FIELDS ( NetAmount )
-        WITH lt_update.
-  ENDMETHOD.
-ENDCLASS.
-```

package/bench/prompts/abap-test-method.md

@@ -1,42 +0,0 @@
----
-skill: abap-test
-description: Generate an ABAP Unit test class for a small business rule method
----
-
-## user
-
-Please write an ABAP Unit test class for this method:
-
-```abap
-CLASS zcl_discount_calculator DEFINITION
-  PUBLIC FINAL CREATE PUBLIC.
-
-  PUBLIC SECTION.
-    "! Returns the discount percentage (0..30) for a given net amount.
-    "!   < 1000  → 0%
-    "!   < 5000  → 5%
-    "!   < 10000 → 10%
-    "!   >= 10000 → 15%
-    "! Raises zcx_discount_error on negative input.
-    METHODS calculate_discount
-      IMPORTING iv_net_amount      TYPE p LENGTH 13 DECIMALS 2
-      RETURNING VALUE(rv_discount) TYPE p LENGTH 3  DECIMALS 2
-      RAISING   zcx_discount_error.
-ENDCLASS.
-
-CLASS zcl_discount_calculator IMPLEMENTATION.
-  METHOD calculate_discount.
-    IF iv_net_amount < 0.
-      RAISE EXCEPTION TYPE zcx_discount_error
-        EXPORTING textid = zcx_discount_error=>negative_input.
-    ENDIF.
-
-    rv_discount = COND #(
-      WHEN iv_net_amount <  1000 THEN '0.00'
-      WHEN iv_net_amount <  5000 THEN '5.00'
-      WHEN iv_net_amount < 10000 THEN '10.00'
-      ELSE                            '15.00'
-    ).
-  ENDMETHOD.
-ENDCLASS.
-```

package/bench/results/abap-document-cds/claude-haiku-4-5.md

@@ -1,189 +0,0 @@
-# abap-document-cds — claude-haiku-4-5
-
-- **skill:** abap-document
-- **description:** Document a CDS interface view with associations + currency annotation
-- **latency:** 26816 ms
-- **input tokens:** 2,688
-- **output tokens:** 2,623
-- **cost:** $0.0158
-
----
-
-# abap-document — ZI_SalesOrder
-
-## TL;DR
-
-**Headline:** Interface view for sales order header data with customer and item associations, read-only with authorization check.
-
-**Top 3 (priority order):**
-1. **Authorization enforced:** `#CHECK` mode requires `DSOD` and sales order read authority at runtime — verify user roles before consuming downstream.
-2. **Fuzzy search enabled on CustomerID:** `fuzzinessThreshold: 0.8` will match partial/misspelled customer names; test with typical fat-finger errors in UAT.
-3. **No filtering logic:** View exposes all rows from `zsales_order` table — upstream consumers must apply their own `WHERE` clauses; no automatic date range or status filtering.
-
-**Verdict:** Safe foundation view for consumption in analytics, APIs, or reporting. Confirm downstream apps implement business rule filtering (e.g., active orders only, date ranges).
-
----
-
-## ZI_SalesOrder (CDS VIEW ENTITY)
-
-### Overview
-
-**Package:** (not yet read — see below)  
-**Type:** CDS View Entity (Interface Layer)  
-**Annotations:** Authorization check enabled, search enabled, end-user label "Sales Order — Interface View"
-
-**Summary:**  
-Exposes sales order header data from the custom table `zsales_order` with associations to customer master, line items, and SAP currency data. Designed as a read-only interface view for analytics, reporting, and API consumption.
-
----
-
-### Purpose
-
-This view serves as the **interface layer** for sales order headers in the custom data model. It:
-
-1. **Presents domain data cleanly** — maps technical table column names (`sales_order_id`, `customer_id`) to business-readable field names (`SalesOrderID`, `CustomerID`).
-2. **Enforces authorization** — restricts read access to users with appropriate sales order query authority.
-3. **Enables semantic search** — makes customer name searchable via fuzzy matching (0.8 threshold = allow 20% typos).
-4. **Links related business entities** — connects to customer master, line items, and currency metadata via associations (no data duplication, navigation-based joins).
-5. **Supports consumption layers** — designed for downstream consumption by reporting tools, OData APIs, or analytical views.
-
----
-
-### Interface
-
-**Key Field:**
-- `SalesOrderID` (Header.sales_order_id) — unique identifier for the sales order
-
-**Header-Level Fields:**
-
-| Field Name | Source | Type | Purpose |
-|------------|--------|------|---------|
-| SalesOrderID | Header.sales_order_id | key | Sales order unique identifier |
-| CustomerID | Header.customer_id | string | References customer master |
-| OrderDate | Header.order_date | date | Date order was placed |
-| CustomerIDForSearch | Header.customer_id | string | Fuzzy-searchable copy for customer lookup |
-| NetAmount | Header.net_amount | decimal | Order value (currency-aware via annotation) |
-| CurrencyCode | Header.currency_code | string | ISO currency code |
-| CreatedAt | Header.created_at | timestamp | Audit: creation timestamp |
-| CreatedBy | Header.created_by | user | Audit: creator user |
-| LastChangedAt | Header.last_changed_at | timestamp | Audit: last change timestamp |
-| LastChangedBy | Header.last_changed_by | user | Audit: last change user |
-
-**Associations (Navigation):**
-
-| Association | Target View | Cardinality | Join Condition | Purpose |
-|-------------|-------------|-------------|-----------------|---------|
-| `_Customer` | ZI_Customer | 0..1 | CustomerID | Navigate to customer master data |
-| `_SalesOrderItem` | ZI_SalesOrderItem | 0..* | SalesOrderID | Navigate to line items for this order |
-| `_Currency` | I_Currency (SAP standard) | 0..1 | CurrencyCode | Navigate to SAP currency details |
-
-**Authorization & Search:**
-- Authorization check: `#CHECK` — runtime check required (user must have query authority for sales order).
-- Default search element: `CustomerIDForSearch` with fuzzy matching (80% match threshold).
-- Searchable: all marked fields indexed for full-text search.
-
----
-
-### Logic Flow
-
-**Data Origin & Transformation:**
-
-1. **Source:** Read all rows from custom table `zsales_order` (Header alias).
-2. **Projection:** Map technical columns to semantic field names:
-   - `sales_order_id` → `SalesOrderID` (key)
-   - `customer_id` → `CustomerID`
-   - `order_date` → `OrderDate`
-   - `net_amount` → `NetAmount` (with currency semantic)
-   - `currency_code` → `CurrencyCode`
-   - Audit fields (created/changed by/at) mapped as-is.
-3. **Duplicate CustomerID:** `CustomerIDForSearch` is a copy of `CustomerID` explicitly marked for full-text search (allows UI to search by customer name via the association).
-4. **Associations:** Three navigation paths added (not joins — lazy-loaded):
-   - To customer master for customer details.
-   - To line items for order composition.
-   - To SAP currency master for exchange rates, decimals, etc.
-5. **Authorization Gate:** View enforces `#CHECK` at query time — SAP will validate user authority before returning rows.
-
-**No filtering logic:** View is a "raw interface" — all rows from the source table are exposed. Upstream consumers must filter by date, status, or other business rules.
-
----
-
-### Data Access
-
-| Table/View | Operation | Purpose |
-|------------|-----------|---------|
-| `zsales_order` (custom) | **READ** | Source table for all header fields (sales_order_id, customer_id, order_date, net_amount, currency_code, audit fields) |
-| `ZI_Customer` (custom view) | **READ** (via association) | Customer master lookup; enriches orders with customer details |
-| `ZI_SalesOrderItem` (custom view) | **READ** (via association) | Line items for the order; enables per-item navigation |
-| `I_Currency` (SAP standard) | **READ** (via association) | SAP currency master; provides conversion rates, decimal places |
-
-**No writes:** This is a read-only interface view. No INSERT, UPDATE, or DELETE allowed.
-
----
-
-### Dependencies
-
-**Called by (Upstream Consumers):**  
-Unknown without further analysis — use `sap_usage_references` to identify (e.g., analytics views, OData services, reports using this view).
-
-**Calls (Dependencies):**
-- `zsales_order` — custom table (no option to change this view without understanding the source table schema).
-- `ZI_Customer` — custom customer interface view (ensure it is available and stable).
-- `ZI_SalesOrderItem` — custom sales order item interface view (ensure it exists).
-- `I_Currency` (SAP standard) — standard SAP currency master (no custom risk; always available post-installation).
-
----
-
-### Authorization & Security
-
-**Authorization Check:** `#CHECK` mode  
-- When a user queries this view, SAP **enforces** a dynamic authorization check at runtime.
-- The specific check depends on SAP's authority object mapping for CDS views (typically `DSOD` → Data Source Object Definition or equivalent).
-- **Action required:** Verify that user roles define query access for this view; otherwise, queries will fail with "Authorization error."
-
-**Search & Indexing:**
-- `CustomerIDForSearch` with `fuzzinessThreshold: 0.8` allows typo-tolerant search (e.g., "APLE" matches "APPLE").
-- Useful for user-facing search UIs; may return false positives in strict filter scenarios.
-
----
-
-### Data Model & Semantics
-
-**Semantic Annotations:**
-- `@Semantics.amount.currencyCode: 'CurrencyCode'` on `NetAmount` — tells consuming systems that this field is a currency amount and which field holds the currency code. Tools like SAP Analytics Cloud will format it correctly.
-- `@ObjectModel.text.element: [ '_Customer.CustomerName' ]` on `CustomerIDForSearch` — tells UI frameworks to display the customer **name** (not ID) when showing this field.
-
-**Searchability:**
-- View is marked `@Search.searchable: true` — all fields with `@Search.defaultSearchElement: true` are indexed.
-- Only `CustomerIDForSearch` is explicitly indexed; other fields are not full-text searchable by default.
-
----
-
-### Notes & Considerations
-
-1. **No status filtering:** View exposes all orders regardless of status (open, closed, cancelled). If you need only active orders, add a downstream view or consuming WHERE clause.
-
-2. **Audit trail:** `CreatedBy`, `LastChangedBy`, `CreatedAt`, `LastChangedAt` are available for compliance; confirm these are populated in the source table `zsales_order`.
-
-3. **Association multiplicity:**
-   - Customer is 0..1 (every order may not have a customer — nullable FK?). Verify business rule: must a sales order always have a customer?
-   - Line items are 0..* (orders with no items are allowed). Confirm with business if this is intentional.
-   - Currency is 0..1 (may not exist in SAP currency master for custom codes). Test with unusual currency codes.
-
-4. **Search on CustomerID not CustomerName:** The view exposes `CustomerID` for search but links to `_Customer.CustomerName`. If users expect to search by customer **name**, ensure the downstream OData/UI binding is configured to search on `CustomerIDForSearch` and display `_Customer.CustomerName`.
-
-5. **No performance optimizations:** View is a simple 1:1 projection. For large `zsales_order` tables (millions of rows), consider:
-   - Adding a semantic partitioning hint in the view definition.
-   - Creating secondary indexes on frequently filtered columns (e.g., `OrderDate`, `CustomerID`).
-   - Testing query response times with large datasets.
-
-6. **Missing fields?** Confirm with business that all required order header fields are in the projection. If fields exist in `zsales_order` but not exposed here, add them or create a second view variant.
-
----
-
-## Next Steps
-
-1. **Trace consumers:** Run `sap_usage_references` to identify which views, APIs, and reports consume this view.
-2. **Verify source table:** Run `sap_get_source` on `zsales_order` to confirm the schema matches the projection.
-3. **Check related views:** Retrieve `ZI_Customer` and `ZI_SalesOrderItem` to ensure the associations are compatible (key cardinality, join conditions).
-4. **Authorization testing:** Create a test user with appropriate authority and verify they can query this view without "Authorization failed" errors.
-5. **Search testing:** Test fuzzy search with intentional typos (e.g., customer name "ACME Corp" vs. search "ACME Crp") to confirm the 0.8 threshold behavior.