router-service-platform-change

To modify router service modules, update apiserver endpoints, authz policy code, or provider adapters outside config and selection chains, then run agent-report to verify surface alignment and update E2E expectations.

Updating authz or rate-limit policy code involves modifying the router-side service modules to align with new governance requirements, enforcing surface alignment checks via agent-ci-gate, and requiring E2E expectation updates for safe, auditable changes.

Yes, you can update provider adapters to support new storage backends within the router service-platform modules without touching business logic, ensuring the changes are validated through agent-report and agent-ci-gate checks.

Yes, this approach applies to changes in memory or response storage flows within the router service-platform, enforcing that modifications are accompanied by surface alignment checks via agent-report and E2E expectation updates.

The best way to ensure safe updates across the service seam is to enforce surface alignment checks via agent-report and agent-ci-gate, while updating E2E expectations to maintain traceability and validation for router service-platform changes.

You should not use this method for changes involving config, decision, selection, or extproc plugin chains, as it specifically targets modifications outside those chains in apiserver endpoints, authz, memory, provider, storage, or runtime modules.