refactor(ledger): move report bundle download to GraphQL reportDownloadUrl

robosystems_client/api/extensions_robo_ledger/op_create_information_block.py

@@ -122,7 +122,10 @@ def sync_detailed(
 
    Generic Information Block construction entry. `block_type` selects the registered block type;
   `payload` is validated against that type's creation schema at dispatch. Schedule dispatches to the
-  existing Schedule machinery; statement block types raise 501 (use create-report instead).
+  existing Schedule machinery; statement block types raise 501 (use create-report instead). Authoring
+  schedules for a close? Call `get-close-playbook` (mode='initiate') first — one schedule is a single
+  debit/credit element pair, so multi-line entries become multiple schedules, and element ids must be
+  real (discover via get-graph-schema / get-unmapped-elements / suggest-mapping).
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -170,7 +173,10 @@ def sync(
 
    Generic Information Block construction entry. `block_type` selects the registered block type;
   `payload` is validated against that type's creation schema at dispatch. Schedule dispatches to the
-  existing Schedule machinery; statement block types raise 501 (use create-report instead).
+  existing Schedule machinery; statement block types raise 501 (use create-report instead). Authoring
+  schedules for a close? Call `get-close-playbook` (mode='initiate') first — one schedule is a single
+  debit/credit element pair, so multi-line entries become multiple schedules, and element ids must be
+  real (discover via get-graph-schema / get-unmapped-elements / suggest-mapping).
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -213,7 +219,10 @@ async def asyncio_detailed(
 
    Generic Information Block construction entry. `block_type` selects the registered block type;
   `payload` is validated against that type's creation schema at dispatch. Schedule dispatches to the
-  existing Schedule machinery; statement block types raise 501 (use create-report instead).
+  existing Schedule machinery; statement block types raise 501 (use create-report instead). Authoring
+  schedules for a close? Call `get-close-playbook` (mode='initiate') first — one schedule is a single
+  debit/credit element pair, so multi-line entries become multiple schedules, and element ids must be
+  real (discover via get-graph-schema / get-unmapped-elements / suggest-mapping).
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -259,7 +268,10 @@ async def asyncio(
 
    Generic Information Block construction entry. `block_type` selects the registered block type;
   `payload` is validated against that type's creation schema at dispatch. Schedule dispatches to the
-  existing Schedule machinery; statement block types raise 501 (use create-report instead).
+  existing Schedule machinery; statement block types raise 501 (use create-report instead). Authoring
+  schedules for a close? Call `get-close-playbook` (mode='initiate') first — one schedule is a single
+  debit/credit element pair, so multi-line entries become multiple schedules, and element ids must be
+  real (discover via get-graph-schema / get-unmapped-elements / suggest-mapping).
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.

robosystems_client/api/extensions_robo_ledger/op_create_taxonomy_block.py

@@ -116,7 +116,10 @@ def sync_detailed(
    Create a taxonomy block atomically: one envelope carrying the taxonomy row plus its structures,
   elements, associations, and rules. Dispatches by `taxonomy_type` — `chart_of_accounts` (declarative
   tenant CoA) is supported; `reporting_extension` / `custom_ontology` / `reporting_standard` are not
-  yet implemented.
+  yet implemented. NOT the path for a functional close schedule: a structure with
+  block_type='schedule' here is a bare ontology row with none of the schedule machinery (per-period
+  facts, schedule_entry_due obligations, closing-entry generator). To create a working schedule use
+  create-information-block(block_type='schedule').
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -169,7 +172,10 @@ def sync(
    Create a taxonomy block atomically: one envelope carrying the taxonomy row plus its structures,
   elements, associations, and rules. Dispatches by `taxonomy_type` — `chart_of_accounts` (declarative
   tenant CoA) is supported; `reporting_extension` / `custom_ontology` / `reporting_standard` are not
-  yet implemented.
+  yet implemented. NOT the path for a functional close schedule: a structure with
+  block_type='schedule' here is a bare ontology row with none of the schedule machinery (per-period
+  facts, schedule_entry_due obligations, closing-entry generator). To create a working schedule use
+  create-information-block(block_type='schedule').
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -217,7 +223,10 @@ async def asyncio_detailed(
    Create a taxonomy block atomically: one envelope carrying the taxonomy row plus its structures,
   elements, associations, and rules. Dispatches by `taxonomy_type` — `chart_of_accounts` (declarative
   tenant CoA) is supported; `reporting_extension` / `custom_ontology` / `reporting_standard` are not
-  yet implemented.
+  yet implemented. NOT the path for a functional close schedule: a structure with
+  block_type='schedule' here is a bare ontology row with none of the schedule machinery (per-period
+  facts, schedule_entry_due obligations, closing-entry generator). To create a working schedule use
+  create-information-block(block_type='schedule').
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.
@@ -268,7 +277,10 @@ async def asyncio(
    Create a taxonomy block atomically: one envelope carrying the taxonomy row plus its structures,
   elements, associations, and rules. Dispatches by `taxonomy_type` — `chart_of_accounts` (declarative
   tenant CoA) is supported; `reporting_extension` / `custom_ontology` / `reporting_standard` are not
-  yet implemented.
+  yet implemented. NOT the path for a functional close schedule: a structure with
+  block_type='schedule' here is a bare ontology row with none of the schedule machinery (per-period
+  facts, schedule_entry_due obligations, closing-entry generator). To create a working schedule use
+  create-information-block(block_type='schedule').
 
   **Idempotency**: supply an `Idempotency-Key` header to make safe retries; replays within 24 hours
   return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.