[prk-Jr]

Summary

• Reject unknown integration IDs during config validate/push and name unknown fields, preventing typos from silently changing integration behavior.
• Apply strict known-field schemas to enabled and disabled integration blocks, tester-cookie settings and Tinybird, while preserving minimal disabled blocks, open payload maps and explicit compatibility fields.
• Warn and continue at runtime for unknown integration IDs; document the cleanup-before-deploy migration for unknown fields.

Known tables containing unknown fields will fail startup with the new binary. Run the new CLI's ts config validate, correct the reported settings, push the cleaned config while the old binary runs, then deploy the new binary.

Changes

File	Change
crates/trusted-server-core/src/config.rs	Reject unknown IDs at deploy validation, warn at runtime, and cover every known integration schema.
crates/trusted-server-core/src/settings.rs	Include serde error details in CLI-facing contexts; make tester-cookie and Tinybird schemas strict.
crates/trusted-server-core/src/integrations/adserver_mock.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/didomi.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/google_tag_manager.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/gpt.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/js_asset_proxy.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/lockr.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/nextjs/mod.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/permutive.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/sourcepoint.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/integrations/testlight.rs	Reject unknown configuration fields.
crates/trusted-server-core/src/test_support/async_html_finalization.rs	Keep the optional fixture schema consistent with strict integration validation.
crates/trusted-server-integration-tests/tests/html_eof_runtime.rs	Build the harness CLI with the fixture feature so strict validation accepts the test integration used by the runtime.
crates/trusted-server-cli/tests/config_env_overlay.rs	Exercise actual validate/push refusal and verify no invalid local blob is written.
docs/guide/configuration.md	Explain field validation, runtime ID warnings and safe upgrade order.
docs/guide/integrations/lockr.md	Replace unsupported fields with the actual schema and defaults; align troubleshooting with app_id.
docs/guide/error-reference.md	Use an existing integration and supported route in the troubleshooting example.
CHANGELOG.md	Document the compatibility break and config-first cleanup order.
docs/superpowers/specs/2026-10-27-strict-integration-validation-design.md	Record behavior, alternatives and preservation requirements.
docs/superpowers/plans/2026-10-27-strict-integration-validation.md	Record implementation and verification steps.

Closes

Closes #1201

Spec

Not a feature (bug fix). The technical design is in docs/superpowers/specs/2026-10-27-strict-integration-validation-design.md.

Test plan

Run with Rust 1.98.1, Node 24.20.0 and Viceroy 0.21.0. Initial sandbox listener/keychain-access failures were resolved by full reruns with the required local access.

• cargo test-fastly && cargo test-axum
• cargo clippy-fastly && cargo clippy-axum
• cargo fmt --all -- --check
• JS tests: cd crates/trusted-server-js/lib && npx vitest run — 1,211 tests passed, no type errors
• JS format: cd crates/trusted-server-js/lib && npm run format
• Docs format: cd docs && npm run format
• Remaining adapter/host Clippy gates, including Cloudflare WASM, Spin native/WASM, CLI and codegen
• cargo test-fastly-reuse, cargo test-cloudflare, cargo test-spin
• Full host-target CLI suite, native core suite and feature-on core configuration tests
• Integration parity and native template-build-digest tests/lint
• JS build, Markdown formatting, WASM clock lint and documentation-proposal script checks
• EOF harness native unit tests and Clippy
• ./scripts/async-html-finalization-local-test.sh axum --auction
• ./scripts/async-html-finalization-local-test.sh fastly --release --auction — includes the test-utils release WASM build
• Manual fastly compute serve — not performed

Regressions distinguish the original acceptance/diagnostic failures and cover all 15 production integration IDs, enabled/disabled fields, runtime warnings, open payload maps and deprecated compatibility fields.

The EOF harness builds its CLI with trusted-server-core/test-utils so validation recognizes the fixture integration selected by its runtimes. Ordinary production CLI builds retain the production ID list.

Checklist

• Not a feature; feature-specific spec-review requirement is inapplicable
• Changes follow AGENTS.md conventions
• No unwrap() in production code
• Uses log macros (not println!)
• New code has tests
• No secrets or credentials committed