chore: regenerate all README.rst and index.html to match CI (Linux/Python 3.11)

Author: emjay0921

endpoint_route_handler/README.rst

@@ -114,31 +114,31 @@ You can see a real life example on shopfloor.app model.
 Known issues / Roadmap
 ======================
 
-- add api docs helpers
+-  add api docs helpers
 
-- allow multiple HTTP methods on the same endpoint
+-  allow multiple HTTP methods on the same endpoint
 
-- multiple values for route and methods
+-  multiple values for route and methods
 
-     keep the same in the ui for now, later own we can imagine a
-     multi-value selection or just add text field w/ proper validation
-     and cleanup
+      keep the same in the ui for now, later own we can imagine a
+      multi-value selection or just add text field w/ proper validation
+      and cleanup
 
-     remove the route field in the table of endpoint_route
+      remove the route field in the table of endpoint_route
 
-     support a comma separated list of routes maybe support comma
-     separated list of methods use only routing.routes for generating
-     the rule sort and freeze its values to update the endpoint hash
+      support a comma separated list of routes maybe support comma
+      separated list of methods use only routing.routes for generating
+      the rule sort and freeze its values to update the endpoint hash
 
-     catch dup route exception on the sync to detect duplicated routes
-     and use the endpoint_hash to retrieve the real record (note: we
-     could store more info in the routing information which will stay in
-     the map)
+      catch dup route exception on the sync to detect duplicated routes
+      and use the endpoint_hash to retrieve the real record (note: we
+      could store more info in the routing information which will stay
+      in the map)
 
-     for customizing the rule behavior the endpoint the hook is to
-     override the registry lookup
+      for customizing the rule behavior the endpoint the hook is to
+      override the registry lookup
 
-     make EndpointRule class overridable on the registry
+      make EndpointRule class overridable on the registry
 
 NOTE in v16 we won't care anymore about odoo controller so the lookup of
 the controller can be simplified to a basic py obj that holds the
@@ -165,8 +165,8 @@ Authors
 Contributors
 ------------
 
-- Simone Orsi <simone.orsi@camptocamp.com>
-- Nguyen Minh Chien <chien@trobz.com>
+-  Simone Orsi <simone.orsi@camptocamp.com>
+-  Nguyen Minh Chien <chien@trobz.com>
 
 Maintainers
 -----------

endpoint_route_handler/static/description/index.html

@@ -476,8 +476,8 @@ <h1><a class="toc-backref" href="#toc-entry-4">Known issues / Roadmap</a></h1>
 the rule sort and freeze its values to update the endpoint hash</p>
 <p>catch dup route exception on the sync to detect duplicated routes
 and use the endpoint_hash to retrieve the real record (note: we
-could store more info in the routing information which will stay in
-the map)</p>
+could store more info in the routing information which will stay
+in the map)</p>
 <p>for customizing the rule behavior the endpoint the hook is to
 override the registry lookup</p>
 <p>make EndpointRule class overridable on the registry</p>

spp_alerts/README.rst

@@ -31,14 +31,14 @@ domain-specific conditions.
 Key Capabilities
 ~~~~~~~~~~~~~~~~
 
-- Track alert lifecycle through state machine: active → acknowledged →
-  resolved
-- Record resolution details including user, timestamp, and notes
-- Classify alerts by type using ``spp.vocabulary`` codes (threshold,
-  expiry, deadline, manual, system)
-- Prioritize alerts as low, medium, high, or critical
-- Send mail notifications via ``mail.thread`` integration
-- Auto-generate alert references in ALR-YYYY-NNNNN format
+-  Track alert lifecycle through state machine: active → acknowledged →
+   resolved
+-  Record resolution details including user, timestamp, and notes
+-  Classify alerts by type using ``spp.vocabulary`` codes (threshold,
+   expiry, deadline, manual, system)
+-  Prioritize alerts as low, medium, high, or critical
+-  Send mail notifications via ``mail.thread`` integration
+-  Auto-generate alert references in ALR-YYYY-NNNNN format
 
 Key Models
 ~~~~~~~~~~
@@ -67,9 +67,9 @@ After installing:
 UI Location
 ~~~~~~~~~~~
 
-- **Menu**: Settings > Technical > Alerts > Alerts
-- **Configuration**: Settings > Technical > Alerts > Alert Rules
-- **Form Tabs**: Details, Resolution (alerts); Thresholds (rules)
+-  **Menu**: Settings > Technical > Alerts > Alerts
+-  **Configuration**: Settings > Technical > Alerts > Alert Rules
+-  **Form Tabs**: Details, Resolution (alerts); Thresholds (rules)
 
 Security
 ~~~~~~~~
@@ -85,14 +85,14 @@ Group                               Access
 Extension Points
 ~~~~~~~~~~~~~~~~
 
-- Inherit ``spp.alert`` to add domain-specific fields (e.g., stock
-  levels, document references)
-- Inherit ``spp.alert.rule`` to add custom threshold or evaluation
-  criteria
-- Override ``action_acknowledge()`` or ``action_resolve()`` to add
-  custom workflow steps
-- Consumer modules implement alert checking via cron jobs or event
-  handlers that evaluate rules and call ``create()`` on ``spp.alert``
+-  Inherit ``spp.alert`` to add domain-specific fields (e.g., stock
+   levels, document references)
+-  Inherit ``spp.alert.rule`` to add custom threshold or evaluation
+   criteria
+-  Override ``action_acknowledge()`` or ``action_resolve()`` to add
+   custom workflow steps
+-  Consumer modules implement alert checking via cron jobs or event
+   handlers that evaluate rules and call ``create()`` on ``spp.alert``
 
 Dependencies
 ~~~~~~~~~~~~

spp_api_v2/README.rst

@@ -30,16 +30,16 @@ all identifiers use namespace URIs for global interoperability.
 Key Capabilities
 ----------------
 
-- **OAuth 2.0 Authentication**: Client credentials flow with
-  scrypt-hashed secrets, scoped access
-- **Consent-Based Access Control**: All reads require active consent,
-  filtered by organization type
-- **External Identifiers Only**: Namespace URIs for lookups, vocabulary
-  IDs for coded values
-- **Source Tracking**: Records data provenance per ADR-008
-- **Extension Registry**: Domain modules register custom fields via
-  ``spp.api.extension``
-- **Batch Operations**: Create/update multiple registrants per request
+-  **OAuth 2.0 Authentication**: Client credentials flow with
+   scrypt-hashed secrets, scoped access
+-  **Consent-Based Access Control**: All reads require active consent,
+   filtered by organization type
+-  **External Identifiers Only**: Namespace URIs for lookups, vocabulary
+   IDs for coded values
+-  **Source Tracking**: Records data provenance per ADR-008
+-  **Extension Registry**: Domain modules register custom fields via
+   ``spp.api.extension``
+-  **Batch Operations**: Create/update multiple registrants per request
 
 Key Models
 ----------
@@ -69,29 +69,29 @@ UI Location
 Navigate to **Registry > Configuration > API V2** for all API
 configuration. Available submenus:
 
-- **API Clients** - Manage OAuth credentials and organization
-  verification
-- **API Extensions** - View registered custom field extensions
-- **API Paths** - Configure available endpoints and static filters
-- **API Filters** - Define queryable field filters per path
-- **Filter Presets** - Create named filter combinations
+-  **API Clients** - Manage OAuth credentials and organization
+   verification
+-  **API Extensions** - View registered custom field extensions
+-  **API Paths** - Configure available endpoints and static filters
+-  **API Filters** - Define queryable field filters per path
+-  **Filter Presets** - Create named filter combinations
 
 **API Client Form Tabs:**
 
-- **Consent & Security** - Consent requirements, legal basis,
-  organization type verification
-- **Scopes** - Resource/action permissions and program restrictions
-- **Description** - Client documentation
+-  **Consent & Security** - Consent requirements, legal basis,
+   organization type verification
+-  **Scopes** - Resource/action permissions and program restrictions
+-  **Description** - Client documentation
 
 **API Extension Form Tabs:**
 
-- **Fields** - Registered custom fields from domain modules
-- **JSON Schema** - Auto-generated schema for extension fields
+-  **Fields** - Registered custom fields from domain modules
+-  **JSON Schema** - Auto-generated schema for extension fields
 
 **API Path Form Tabs:**
 
-- **Filters** - Field-level filter configurations (inline editable)
-- **Presets** - Saved filter combinations (inline editable)
+-  **Filters** - Field-level filter configurations (inline editable)
+-  **Presets** - Saved filter combinations (inline editable)
 
 Configuration
 -------------
@@ -128,9 +128,9 @@ Security
 Extension Points
 ----------------
 
-- Inherit ``spp.api.extension`` to register custom fields
-- Override ``_get_fastapi_routers()`` in ``fastapi.endpoint`` for custom
-  endpoints
+-  Inherit ``spp.api.extension`` to register custom fields
+-  Override ``_get_fastapi_routers()`` in ``fastapi.endpoint`` for
+   custom endpoints
 
 Dependencies
 ------------

spp_api_v2/static/description/index.html

@@ -504,8 +504,8 @@ <h1>Security</h1>
 <h1>Extension Points</h1>
 <ul class="simple">
 <li>Inherit <tt class="docutils literal">spp.api.extension</tt> to register custom fields</li>
-<li>Override <tt class="docutils literal">_get_fastapi_routers()</tt> in <tt class="docutils literal">fastapi.endpoint</tt> for custom
-endpoints</li>
+<li>Override <tt class="docutils literal">_get_fastapi_routers()</tt> in <tt class="docutils literal">fastapi.endpoint</tt> for
+custom endpoints</li>
 </ul>
 </div>
 <div class="section" id="dependencies">

spp_api_v2_change_request/README.rst

@@ -31,16 +31,17 @@ numbers (CR/2024/00001) instead of database IDs for all operations.
 Key Capabilities
 ~~~~~~~~~~~~~~~~
 
-- Create change requests in draft status with registrant and detail data
-- Read individual change requests by reference or search with filters
-  (registrant, type, status, dates)
-- Update detail data on draft change requests with optimistic locking
-  via If-Match headers
-- Submit draft requests for approval workflow
-- Approve, reject, or request revision on pending requests (requires
-  approval scope)
-- Apply approved change requests to registrant records
-- Reset rejected/revision requests to draft for resubmission
+-  Create change requests in draft status with registrant and detail
+   data
+-  Read individual change requests by reference or search with filters
+   (registrant, type, status, dates)
+-  Update detail data on draft change requests with optimistic locking
+   via If-Match headers
+-  Submit draft requests for approval workflow
+-  Approve, reject, or request revision on pending requests (requires
+   approval scope)
+-  Apply approved change requests to registrant records
+-  Reset rejected/revision requests to draft for resubmission
 
 Key Models
 ~~~~~~~~~~
@@ -73,26 +74,26 @@ To configure OAuth 2.0 clients with appropriate scopes:
    by ``spp_api_v2``)
 2. Configure OAuth 2.0 clients with appropriate scopes:
 
-   - ``change_request:read`` - Read and search change requests
-   - ``change_request:create`` - Create new change requests
-   - ``change_request:update`` - Update, submit, and reset requests
-   - ``change_request:approve`` - Approve, reject, or request revision
-   - ``change_request:apply`` - Apply approved changes to registrants
+   -  ``change_request:read`` - Read and search change requests
+   -  ``change_request:create`` - Create new change requests
+   -  ``change_request:update`` - Update, submit, and reset requests
+   -  ``change_request:approve`` - Approve, reject, or request revision
+   -  ``change_request:apply`` - Apply approved changes to registrants
 
 API Endpoints
 ~~~~~~~~~~~~~
 
-- ``POST /ChangeRequest`` - Create new change request
-- ``GET /ChangeRequest/{reference}`` - Read by reference
-- ``GET /ChangeRequest`` - Search with filters
-- ``PUT /ChangeRequest/{reference}`` - Update detail data
-- ``POST /ChangeRequest/{reference}/$submit`` - Submit for approval
-- ``POST /ChangeRequest/{reference}/$approve`` - Approve request
-- ``POST /ChangeRequest/{reference}/$reject`` - Reject request
-- ``POST /ChangeRequest/{reference}/$request-revision`` - Request
-  revision
-- ``POST /ChangeRequest/{reference}/$apply`` - Apply to registrant
-- ``POST /ChangeRequest/{reference}/$reset`` - Reset to draft
+-  ``POST /ChangeRequest`` - Create new change request
+-  ``GET /ChangeRequest/{reference}`` - Read by reference
+-  ``GET /ChangeRequest`` - Search with filters
+-  ``PUT /ChangeRequest/{reference}`` - Update detail data
+-  ``POST /ChangeRequest/{reference}/$submit`` - Submit for approval
+-  ``POST /ChangeRequest/{reference}/$approve`` - Approve request
+-  ``POST /ChangeRequest/{reference}/$reject`` - Reject request
+-  ``POST /ChangeRequest/{reference}/$request-revision`` - Request
+   revision
+-  ``POST /ChangeRequest/{reference}/$apply`` - Apply to registrant
+-  ``POST /ChangeRequest/{reference}/$reset`` - Reset to draft
 
 Security
 ~~~~~~~~
@@ -105,12 +106,12 @@ enforces scope checks on each endpoint. Users must authenticate via the
 Extension Points
 ~~~~~~~~~~~~~~~~
 
-- Inherit ``ChangeRequestService`` to customize serialization,
-  validation, or business logic
-- Override router endpoint functions to add custom validation or side
-  effects
-- Extend the API schema by inheriting the Pydantic models in
-  ``schemas/change_request.py``
+-  Inherit ``ChangeRequestService`` to customize serialization,
+   validation, or business logic
+-  Override router endpoint functions to add custom validation or side
+   effects
+-  Extend the API schema by inheriting the Pydantic models in
+   ``schemas/change_request.py``
 
 UI Location
 ~~~~~~~~~~~

spp_api_v2_change_request/static/description/index.html

@@ -378,7 +378,8 @@ <h1 class="title">OpenSPP API V2 - Change Request</h1>
 <div class="section" id="key-capabilities">
 <h1>Key Capabilities</h1>
 <ul class="simple">
-<li>Create change requests in draft status with registrant and detail data</li>
+<li>Create change requests in draft status with registrant and detail
+data</li>
 <li>Read individual change requests by reference or search with filters
 (registrant, type, status, dates)</li>
 <li>Update detail data on draft change requests with optimistic locking

spp_api_v2_cycles/README.rst

@@ -30,18 +30,18 @@ and requires OAuth 2.0 authentication with resource-based scopes.
 Key Capabilities
 ~~~~~~~~~~~~~~~~
 
-- **Read Cycle**: Retrieve cycle details by name via
-  ``GET /Cycle/{identifier}``
-- **Search Cycles**: Filter cycles by program, state, start/end dates,
-  or last updated timestamp
-- **Pagination**: Support for offset-based pagination with configurable
-  page size (max 100)
-- **Statistics**: Expose beneficiary count, entitlement count, payment
-  count, and total amounts
-- **Cycle Navigation**: Reference to previous and next cycles in
-  sequence
-- **OAuth Scopes**: Extend API client scopes with ``cycle`` resource
-  type for read operations
+-  **Read Cycle**: Retrieve cycle details by name via
+   ``GET /Cycle/{identifier}``
+-  **Search Cycles**: Filter cycles by program, state, start/end dates,
+   or last updated timestamp
+-  **Pagination**: Support for offset-based pagination with configurable
+   page size (max 100)
+-  **Statistics**: Expose beneficiary count, entitlement count, payment
+   count, and total amounts
+-  **Cycle Navigation**: Reference to previous and next cycles in
+   sequence
+-  **OAuth Scopes**: Extend API client scopes with ``cycle`` resource
+   type for read operations
 
 Key Models
 ~~~~~~~~~~
@@ -70,8 +70,8 @@ UI Location
 
 No standalone menu. API endpoints are available at:
 
-- ``/api/v2/spp/Cycle`` - Search cycles
-- ``/api/v2/spp/Cycle/{identifier}`` - Read cycle by name
+-  ``/api/v2/spp/Cycle`` - Search cycles
+-  ``/api/v2/spp/Cycle/{identifier}`` - Read cycle by name
 
 Security
 ~~~~~~~~
@@ -87,12 +87,12 @@ existing models.
 Extension Points
 ~~~~~~~~~~~~~~~~
 
-- Override ``CycleService.to_api_schema()`` to add custom fields to the
-  API response
-- Inherit ``Cycle`` schema to add domain-specific attributes in the
-  ``extension`` field
-- Add search filters by extending ``CycleService.search()`` to support
-  additional query parameters
+-  Override ``CycleService.to_api_schema()`` to add custom fields to the
+   API response
+-  Inherit ``Cycle`` schema to add domain-specific attributes in the
+   ``extension`` field
+-  Add search filters by extending ``CycleService.search()`` to support
+   additional query parameters
 
 Dependencies
 ~~~~~~~~~~~~