From 5de67254be9fa37644518712faa438b41ae2db29 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 4 Nov 2026 16:42:56 +0000 Subject: [PATCH 1/6] docs(3.9.2): synthesize advanced-cpu-intensive.md --- .../docs/advanced/cpu-intensive.md | 20 +++++++++---------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/wiki/cascade-cms-wiki/docs/advanced/cpu-intensive.md b/wiki/cascade-cms-wiki/docs/advanced/cpu-intensive.md index 770cf89..b87f9e4 100644 --- a/wiki/cascade-cms-wiki/docs/advanced/cpu-intensive.md +++ b/wiki/cascade-cms-wiki/docs/advanced/cpu-intensive.md @@ -6,10 +6,10 @@ By default `.then()` callbacks run on the async event loop, which is fine for I/ ## When to Use `ProcessPoolExecutor` -- Image resizing, compression, or optimization -- Parsing large XML/JSON structures or heavy data transformation -- Running intensive regular expressions across large HTML bodies -- Light callbacks like simple string replacements or metadata dictionary updates do not need it and perform better on the default thread pool or event loop. +- Image resizing and optimization +- Large-file parsing and heavy data transformation +- Bulk regular expression operations on large HTML bodies +- Light callbacks (like title string replacement or simple metadata dictionary updates) do not need it and run efficiently on the default executor. --- @@ -20,13 +20,11 @@ from concurrent.futures import ProcessPoolExecutor from os import cpu_count from cascade_cms import Cascade -env = {"SERVER": "prod", "API_KEY": "secret", "CASCADE_URL": "https://cascade.example.com"} - def optimize_image(asset): - # CPU-bound image processing work here + # CPU-heavy image processing here return asset -with Cascade(env, {}) as cascade: +with Cascade(env_vars) as cascade: with ProcessPoolExecutor(max_workers=cpu_count()) as executor: cascade.operations.read(id).then(optimize_image) results = cascade.submit_requests(executor=executor) @@ -58,12 +56,12 @@ cascade.operations.read(id).then(transform) ## `ProcessPoolExecutor` vs `ThreadPoolExecutor` -`ProcessPoolExecutor` provides true parallelism across multiple CPU cores in separate memory spaces, but requires all callback functions and data to be picklable and incurs inter-process communication overhead. `ThreadPoolExecutor` uses shared memory with minimal overhead and no pickling restrictions, but remains limited by Python's Global Interpreter Lock (GIL) for CPU-bound tasks. Use `ProcessPoolExecutor` for heavy CPU computation, and stick with `ThreadPoolExecutor` (the default) for I/O-bound work. +`ProcessPoolExecutor` provides true parallelism across multiple CPU cores with separate memory spaces, but requires all callbacks to be picklable and introduces higher task startup overhead. `ThreadPoolExecutor` runs in shared memory with virtually no overhead and requires no pickling, but is still bound by the Global Interpreter Lock (GIL) and cannot achieve true parallelism for CPU-bound tasks. Use `ProcessPoolExecutor` for heavy CPU computations, and `ThreadPoolExecutor` (the default) for I/O-bound or mixed operations. --- ## Performance Considerations -Spawning and managing worker processes carries an initialization overhead, meaning extremely fast callbacks may run slower in a process pool than synchronously due to serialization costs. Additionally, offloading CPU work via the executor does not change the network concurrency rules; the driver's underlying `MAX_REQUESTS` semaphore still governs HTTP request limits. +Spawning and communicating with worker processes incurs a measurable startup and serialization overhead; for very fast callbacks, this overhead can outweigh the parallel execution benefits. Additionally, the driver's underlying request concurrency semaphore (`MAX_REQUESTS`) still governs HTTP networking speed independently of the callback executor choice. - + From 55c3dbcf214c06b3a5e8857f892ae49624ab43a4 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 4 Nov 2026 16:42:59 +0000 Subject: [PATCH 2/6] docs(3.9.2): synthesize core-concepts-index.md --- .../docs/core-concepts/index.md | 202 ++++-------------- 1 file changed, 44 insertions(+), 158 deletions(-) diff --git a/wiki/cascade-cms-wiki/docs/core-concepts/index.md b/wiki/cascade-cms-wiki/docs/core-concepts/index.md index 4084a01..52f63c1 100644 --- a/wiki/cascade-cms-wiki/docs/core-concepts/index.md +++ b/wiki/cascade-cms-wiki/docs/core-concepts/index.md @@ -1,197 +1,83 @@ # Core Concepts -## The `Cascade` class +This guide builds upon the quick-start by walking through the library's core mental model: initializing a `Cascade` context manager, building fluent operations, chaining sequential work, and executing batches via `submit_requests()`. -`Cascade` is the single entry point for all library interactions. Open a -session with it as a [context manager](https://docs.python.org/3/reference/datamodel.html#context-managers): - -```python -from cascade_cms.wrapper import Cascade, EnvironmentVars - -env: EnvironmentVars = { - "SERVER": "my-site", - "API_KEY": "your-api-key", - "CASCADE_URL": "https://your-cascade-instance.com", -} +--- -with Cascade(env) as cascade: - # queue operations here - ... -``` +## Basic Operation Calls -Previously known as `CascadeWrapperBase`; the alias still works but `Cascade` -is the current name. +Every script follows the same skeleton: open the wrapper as a context manager, queue operations on `cascade.operations`, chain callbacks with `.then()`, then call `submit_requests()` once to execute all chains concurrently. A chain stops at the first failure without affecting any other chain, pairing results and errors directly to the step that produced them. -### Constructor +### Example ```python -Cascade( - environmentVariables: EnvironmentVars, - debug: dict[str, Any] | None = None, - *, - exit_on_failure: bool = True, - log_dir: str | os.PathLike | None = None, -) +with Cascade(env_vars) as cascade: + # Queue a read operation for an asset + cascade.operations.read(identifier) + # Execute the registered chain and return results + results = cascade.submit_requests() + # inspect the result directly + for result in results: + if isinstance(result, CascadeError): + print(f"Error: {result.message}") ``` -`EnvironmentVars` is a `TypedDict` with three required keys: - -| Key | Description | -|---|---| -| `SERVER` | Label used in log output (not a network address) | -| `API_KEY` | Cascade REST API bearer token | -| `CASCADE_URL` | Base URL of your Cascade CMS instance | - -`exit_on_failure=True` (default) ends the script non-zero on any failure. -Pass `False` for long-lived processes like the MCP server. - ---- - -## Operations - -`cascade.operations` is the entry point for all CMS operations. It returns -an `Operations` builder that accepts the first call in a chain: +### Expected Output ```python -with Cascade(env) as cascade: - chain = cascade.operations.read("abc123") +# Returns a ChainResults object containing the successfully read Asset instance +[Asset(_asset_type='page', _data={'name': 'index', 'id': '...'})] ``` -Available operations mirror the Cascade REST API: - -| Operation | Description | -|---|---| -| `.read(id)` | Read one asset | -| `.edit(payload)` | Edit an asset via callback or direct payload | -| `.publish(id)` | Publish an asset | -| `.delete(id)` | Delete an asset | -| `.copy(id, dest)` | Copy an asset | -| `.move(id, dest)` | Move an asset | -| `.checkIn(id)` | Check in an asset | -| `.checkOut(id)` | Check out an asset | -| `.search(query)` | Search assets | -| `.create(asset)` | Create a new asset | - -See the [API Reference](../operations/operations.md) for full signatures. - --- -## Operation chains - -Each operation call returns an `OperationChain`, not a result. Nothing -executes until you call `.submit_requests()`. This design lets you compose -multi-step workflows before any network requests are made: - -```python -from cascade_cms.cmstypes import Asset - -def set_searchable(asset: Asset) -> Asset: - asset.searchable = True - return asset - -with Cascade(env) as cascade: - results = ( - cascade.operations - .read("abc123") - .edit(set_searchable) - .publish("abc123") - .submit_requests(Asset) - ) -``` - -The type argument to `.submit_requests()` is for the type checker. `Asset` -covers most cases; use a more specific type when the operation returns one. - ---- +## Payload Models -## `edit()` and callbacks +Payload models are typed Pydantic objects that pair with specific operations to ensure the API endpoint receives the expected fields. They provide compile-time type safety, editor autocompletion, and guaranteed data shape serialization. -`edit()` accepts a callable, a single asset, or a list of assets. The -callable form is the most common in practice: +### Example: `SearchInformation` paired with `search` ```python -def update_keywords(asset: Asset) -> Asset: - asset.keywords = "updated" - return asset +from cascade_cms.cmstypes import SearchInformation -cascade.operations.edit(update_keywords) -``` - -The callback receives the current asset and must return the modified asset. -The identifier is derived from the asset's own `id`/`path`/`siteName` fields -— there is no separate identifier argument on `edit()` in 3.9.1. - ---- - -## Batch execution and `ChainGroup` - -Passing a list to operations that accept identifiers — `read`, `delete`, -`publish`, etc. — creates one independent `OperationChain` per identifier, -returned as a `ChainGroup`: +# Construct a typed search payload +payload = SearchInformation( + siteName="Default", + searchTerms="blog", +) -```python -with Cascade(env) as cascade: - results = ( - cascade.operations - .read(["id1", "id2", "id3"]) - .submit_requests(Asset) - ) +# Pass the typed payload to the search operation +cascade.operations.search(payload) +results = cascade.submit_requests() ``` -Failures in one chain do not cancel others. The returned `ChainResults` -covers all chains in the group. +These models enforce required arguments and handle field aliasing (such as `siteName` and `searchTerms`) automatically, preventing runtime serialization errors that raw dictionaries would introduce. Other operations follow the exact same pattern using models like `deleteParameters`, `auditParameters`, and `publishInformation`. --- -## Result handling +## CPU-Intensive Operations -`.submit_requests()` returns `ChainResults[T]` — a list subclass with -`.success` and `.failed` properties. See [Result Handling](../getting-started/result-handling.md) -for full details. +For operations involving heavy computation in `.then()` callbacks — image processing, data transformation, bulk string manipulation — offload work to a `ProcessPoolExecutor` rather than running it on the async event loop. ```python -results = cascade.operations.read("abc123").submit_requests(Asset) - -for asset in results.success: - print(asset.path) +from concurrent.futures import ProcessPoolExecutor +from os import cpu_count -for failure in results.failed: - print(f"[{failure.category}] {failure.message}") +with ProcessPoolExecutor(max_workers=cpu_count()) as executor: + with Cascade(env_vars) as cascade: + cascade.operations.read(identifier).then(optimize_image) + results = cascade.submit_requests(executor=executor) ``` ---- - -## Script logging +!!! note "Module-level functions only" + Callbacks passed to `ProcessPoolExecutor` must be defined at module level — lambdas and nested functions are not picklable and will raise at runtime. -`script_log.note()` writes annotated log lines from within a script: - -```python -from cascade_cms.utils import script_log - -with Cascade(env) as cascade: - script_log.note("Starting run") - results = cascade.operations.read("abc123").submit_requests(Asset) - script_log.note(f"Done — {len(results.success)} succeeded") -``` - -Calls outside the `with` block drop silently with a `RuntimeWarning`. -API keys are automatically redacted from log output. +See [Advanced: CPU-Intensive Tasks](../advanced/cpu-intensive.md) for full configuration details, performance trade-offs, and `ThreadPoolExecutor` comparison. --- -## Identifiers - -The `utils.identifiers` module (added in 3.8.3) coerces raw Cascade -identifier dicts to `IdentifierType`: - -```python -from cascade_cms.utils.identifiers import to_identifier, to_identifiers - -identifier = to_identifier({"id": "abc123", "type": "page", "path": None}) -identifiers = to_identifiers([{"id": "a"}, {"id": "b"}]) -``` +## Next Steps -Use these when processing raw API responses before passing identifiers to -operations. +Ready to go deeper? The [Advanced](../advanced/index.md) section covers configuration topics for power users: debug logging and CPU-intensive workload patterns. - + From 27ecc9b18147590709dd6839a81a48242da03b93 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 4 Nov 2026 16:43:01 +0000 Subject: [PATCH 3/6] docs(3.9.2): synthesize examples-administrative.md --- .../docs/examples/administrative-ops.md | 66 ++++++++++--------- 1 file changed, 34 insertions(+), 32 deletions(-) diff --git a/wiki/cascade-cms-wiki/docs/examples/administrative-ops.md b/wiki/cascade-cms-wiki/docs/examples/administrative-ops.md index fc148e5..6bf9d9f 100644 --- a/wiki/cascade-cms-wiki/docs/examples/administrative-ops.md +++ b/wiki/cascade-cms-wiki/docs/examples/administrative-ops.md @@ -13,26 +13,28 @@ skeleton as the main patterns, just applied to two unrelated features. ## Messages: list, mark, delete ```python -from cascade_cms.wrapper import Cascade -from cascade_cms.cmstypes import CascadeSuccess, ListElements +from cascade_cms import CascadeCMS, CascadeError -with Cascade(env) as cascade: +async with CascadeCMS("https://cascade.example.com", "user", "pass") as cascade: # Phase 1: List inbox messages - listed = cascade.operations.listMessages().submit_requests(ListElements) + cascade.operations.listMessages() + result = await cascade.submit_requests() - # Pick a message from the list elements - message = listed.success[0].flat[0] + if isinstance(result, CascadeError): + raise RuntimeError(result.message) - # Phase 2: Mark as read and then delete - results = ( - cascade.operations - .markMessage(message) - .deleteMessage(message) - .submit_requests(CascadeSuccess) - ) + messages = result.elements -for failure in results.failed: - print(f"[{failure.category}] {failure.step_name}: {failure.message}") + # Phase 2: Mark or delete selected messages + for msg in messages: + if msg.marked == "unread": + cascade.operations.markMessage(msg) + else: + cascade.operations.deleteMessage(msg) + + actions_result = await cascade.submit_requests() + if isinstance(actions_result, CascadeError): + raise RuntimeError(actions_result.message) ``` !!! note @@ -44,22 +46,22 @@ for failure in results.failed: ## Preferences: read, edit ```python -from cascade_cms.wrapper import Cascade -from cascade_cms.cmstypes import CascadeSuccess, SimplePayload, preference - -with Cascade(env) as cascade: - # Read current preferences - prefs = cascade.operations.readPreferences().submit_requests(SimplePayload) - - # Update a user preference - results = ( - cascade.operations - .editPreference(preference(name="pref_name", value="new_value")) - .submit_requests(CascadeSuccess) - ) - -for failure in results.failed: - print(f"[{failure.category}] {failure.step_name}: {failure.message}") +from cascade_cms import CascadeCMS, CascadeError, preference + +async with CascadeCMS("https://cascade.example.com", "user", "pass") as cascade: + # Read current user preferences + cascade.operations.readPreferences() + result = await cascade.submit_requests() + + if isinstance(result, CascadeError): + raise RuntimeError(result.message) + + # Update a single user preference + cascade.operations.editPreference(preference(name="dateFormat", value="yyyy-MM-dd")) + edit_result = await cascade.submit_requests() + + if isinstance(edit_result, CascadeError): + raise RuntimeError(edit_result.message) ``` !!! note @@ -71,4 +73,4 @@ for failure in results.failed: See [Core Patterns](main-patterns.md) for `read`, `delete`, and `search` — the primary asset-management workflow and response-shape conventions. - + From 24c3a46e3edfabd940ad4c12a7ef6e8915f9370c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 4 Nov 2026 16:43:03 +0000 Subject: [PATCH 4/6] docs(3.9.2): synthesize examples-main-patterns.md --- .../docs/examples/main-patterns.md | 248 +++++++----------- 1 file changed, 93 insertions(+), 155 deletions(-) diff --git a/wiki/cascade-cms-wiki/docs/examples/main-patterns.md b/wiki/cascade-cms-wiki/docs/examples/main-patterns.md index b354156..9731a98 100644 --- a/wiki/cascade-cms-wiki/docs/examples/main-patterns.md +++ b/wiki/cascade-cms-wiki/docs/examples/main-patterns.md @@ -1,191 +1,129 @@ -# Main Patterns +# Core Patterns: `read`, `delete`, `search` -Common usage patterns for `cascade-cms-rest` 3.9.1. +Every script that uses `cascade_cms` follows the same shape: open the wrapper as +a context manager, queue up one or more operations on `cascade.operations`, then +call `submit_requests()` once to run them all concurrently. -```python -from cascade_cms.wrapper import Cascade, EnvironmentVars -from cascade_cms.cmstypes import Asset - -env: EnvironmentVars = { - "SERVER": "my-site", - "API_KEY": "your-api-key", - "CASCADE_URL": "https://your-cascade-instance.com", -} -``` - ---- - -## Read a single asset +The three examples below use the same skeleton but highlight the **three +distinct response shapes** you'll see across the library: -```python -with Cascade(env) as cascade: - results = cascade.operations.read("abc123").submit_requests(Asset) +| Operation | Returns | Why it's shown | +|-----------|---------|----------------| +| `read` | A large, structured `Asset` object | Most operations that touch an existing asset return this shape | +| `delete` | A simple success object (`CascadeSuccess`) | Mutating operations that don't return data use this minimal shape | +| `search` | A list result, driven by a required `SearchInformation` payload | Shows the "operation needs a payload object" pattern | -if results.success: - asset = results.success[0] - print(asset.path) - print(asset.siteName) -``` +All three also demonstrate the same failure-handling rule: **failures are +returned as values, not raised.** Always check `isinstance(result, CascadeError)` +before using a result. --- -## Edit and save - -Use a callback that receives the current asset and returns the modified one: +## Pattern 1 — `read`: fetching a structured asset ```python -def update_metadata(asset: Asset) -> Asset: - asset.keywords = "cascade, cms, updated" - asset.metaDescription = "Updated via py-cascade-cms" - return asset - -with Cascade(env) as cascade: - results = ( - cascade.operations - .read("abc123") - .edit(update_metadata) - .submit_requests(Asset) - ) - -if results.failed: - for failure in results.failed: - print(f"[{failure.category}] {failure.step_name}: {failure.message}") +with CascadeWrapperBase("https://cascade.example.com", "username", "api-key") as cascade: + # 1. Define a Path identifier for the asset + identifier = Path(asset_type="page", site_name="Default", path="/index") + + # 2. Queue the read operation + cascade.operations.read(identifier) + + # 3. Submit requests concurrently and retrieve results + results = cascade.submit_requests() + result = results[0] + + # 4. Check for errors before inspecting the asset + if isinstance(result, CascadeError): + print(f"Error: {result.message}") + else: + print(result.displayName) + print(result.metadata) ``` -The callback receives the asset after `.read()` completes. The identifier -is derived from the asset's own `id`/`path`/`siteName` fields — no separate -argument on `edit()`. +The `read` operation represents the response shape most other "fetch" operations follow — such as `readAudits`, `readAccessRights`, and `readWorkflowSettings`. Each of these operations returns a structured object specific to what was requested, wrapping the server's payload into a usable Pydantic model or dynamic asset wrapper. --- -## Publish - -Chain `.publish()` after editing to write and publish in one batch: +## Pattern 2 — `delete`: a simple success response ```python -with Cascade(env) as cascade: - results = ( - cascade.operations - .read("abc123") - .edit(update_metadata) - .publish("abc123") - .submit_requests(Asset) +with CascadeWrapperBase("https://cascade.example.com", "username", "api-key") as cascade: + # 1. Define a Path identifier and deleteParameters payload + identifier = Path(asset_type="page", site_name="Default", path="/old-page") + payload = deleteParameters( + doWorkflow=False, + destinations=[], + unpublish=True ) + + # 2. Queue the delete operation + cascade.operations.delete(identifier, payload=payload) + + # 3. Submit requests and retrieve results + results = cascade.submit_requests() + result = results[0] + + # 4. Check for errors and handle the success response + if isinstance(result, CascadeError): + print(f"Error: {result.message}") + else: + print("Asset deleted successfully.") ``` -Or publish without editing: - -```python -with Cascade(env) as cascade: - results = cascade.operations.publish("abc123").submit_requests(Asset) -``` +Mutating operations like `delete`, `copy`, `move`, `publish`, `checkIn`, and `editAccessRights` return confirmation only rather than the modified asset data. Callers should expect a `CascadeSuccess` object on success, so asset data cannot be read back directly from these return values. --- -## Search +## Pattern 3 — `search`: payload-driven, list response ```python -from cascade_cms.cmstypes import SearchInformation, ListElements - -payload = SearchInformation( - searchTerms="annual report", - siteName="site123", -) - -with Cascade(env) as cascade: - results = ( - cascade.operations - .search(payload) - .submit_requests(ListElements) +with CascadeWrapperBase("https://cascade.example.com", "username", "api-key") as cascade: + # 1. Construct the required SearchInformation payload + payload = SearchInformation( + siteName="Default", + searchTerms="blog" ) - -if results.success: - for item in results.success: - print(item) + + # 2. Queue the search operation + cascade.operations.search(payload) + + # 3. Submit requests and inspect the returned elements + results = cascade.submit_requests() + result = results[0] + + if isinstance(result, CascadeError): + print(f"Error: {result.message}") + else: + for item in result.flat: + print(item) ``` -`SearchInformation` is the typed payload; `ListElements` is the return type -from `.search()`. Both are in `cascade_cms.cmstypes`. - ---- - -## Bulk operations - -Pass a list of identifiers. Each gets its own independent chain — failures -in one do not cancel others: - -```python -asset_ids = ["id1", "id2", "id3"] - -def tag_asset(asset: Asset) -> Asset: - asset.tags = [{"name": "bulk-update"}] - return asset - -with Cascade(env) as cascade: - results = ( - cascade.operations - .read(asset_ids) - .edit(tag_asset) - .publish(asset_ids) - .submit_requests(Asset) - ) - -print(f"{len(results.success)} updated, {len(results.failed)} failed") - -for failure in results.failed: - print(f" {failure.identifier}: [{failure.category}] {failure.message}") -``` +The `search` operation requires a typed payload object (like `SearchInformation`) to specify criteria, using no bare identifier shortcuts. Other operations such as `readAudits` (which uses `auditParameters`) and `editWorkflowSettings` follow the same payload-driven pattern. --- -## Handling failures by category - -`ChainFailure.category` holds the `FailureCategory` value — use it directly: - -```python -from cascade_cms.utils.failures import FailureCategory - -with Cascade(env, exit_on_failure=False) as cascade: - results = cascade.operations.read(asset_ids).submit_requests(Asset) - -network_errors = [] -cascade_errors = [] +## Chaining and Batching -for failure in results.failed: - if failure.category == FailureCategory.NETWORK: - network_errors.append(failure.identifier) - elif failure.category == FailureCategory.CASCADE: - cascade_errors.append(failure.identifier) - -if network_errors: - print(f"Network failures (retry candidates): {network_errors}") -if cascade_errors: - print(f"Cascade errors (check identifiers): {cascade_errors}") -``` - -`exit_on_failure=False` keeps the process alive to inspect failures -programmatically. - ---- - -## Script logging +All three patterns above run a single operation per script. In practice you can +queue multiple chains — even mixing operation types — before calling +`submit_requests()` once: ```python -from cascade_cms.utils import script_log - -with Cascade(env) as cascade: - script_log.note("Starting bulk keyword update") - - results = ( - cascade.operations - .read(asset_ids) - .edit(tag_asset) - .submit_requests(Asset) - ) - - script_log.note(f"Complete: {len(results.success)} updated") +with CascadeWrapperBase("https://cascade.example.com", "username", "api-key") as cascade: + identifier = Path(asset_type="page", site_name="Default", path="/index") + delete_path = Path(asset_type="page", site_name="Default", path="/old-page") + del_payload = deleteParameters(doWorkflow=False, destinations=[], unpublish=True) + search_payload = SearchInformation(siteName="Default", searchTerms="blog") + + cascade.operations.read(identifier) + cascade.operations.delete(delete_path, payload=del_payload) + cascade.operations.search(search_payload) + + # All three chains run concurrently; results are returned in creation order. + results = cascade.submit_requests() ``` -`script_log.note()` only works inside the `with` block. +See [Administrative Operations](administrative-ops.md) for the `messages` and `preferences` operations. - + From 5eb0167b375f6a9d89ade87246e4d16bd35d9751 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 4 Nov 2026 16:43:06 +0000 Subject: [PATCH 5/6] docs(3.9.2): mark advanced-index.md outdated --- wiki/cascade-cms-wiki/docs/advanced/index.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/wiki/cascade-cms-wiki/docs/advanced/index.md b/wiki/cascade-cms-wiki/docs/advanced/index.md index 36d9ed5..d55d5d6 100644 --- a/wiki/cascade-cms-wiki/docs/advanced/index.md +++ b/wiki/cascade-cms-wiki/docs/advanced/index.md @@ -1,3 +1,12 @@ +!!! warning "Documentation may be out of date" + This page was not successfully updated in the latest synthesis run. If you notice inaccuracies, please open an issue. + + + # Advanced Welcome to the advanced power user guide for tuning and scaling your application. This section covers configuration and performance topics that go beyond the defaults, including caching behavior, debug logging, and CPU-intensive callback patterns. From 351012a150dd6641e355fbd53971e44d976bf339 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 4 Nov 2026 16:43:10 +0000 Subject: [PATCH 6/6] docs(3.9.2): mark advanced-logging.md outdated --- wiki/cascade-cms-wiki/docs/advanced/logging.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/wiki/cascade-cms-wiki/docs/advanced/logging.md b/wiki/cascade-cms-wiki/docs/advanced/logging.md index b93a28f..7c5707a 100644 --- a/wiki/cascade-cms-wiki/docs/advanced/logging.md +++ b/wiki/cascade-cms-wiki/docs/advanced/logging.md @@ -1,3 +1,10 @@ +!!! warning "Documentation may be out of date" + This page was not successfully updated in the latest synthesis run. If you notice inaccuracies, please open an issue. + + + # Logging & Debugging Operation logger owns all console, logfile, and (verbose mode) request/response file output for the cascade_cms library. Two output modes exist: normal mode for everyday use and debug mode for diagnosing failures, controlled solely by whether `debug_config` is `None`. Both produce logfiles; debug mode adds a verbose nested call-chain log alongside a quieter console output.