Set up Polylane

[polylane]

Polylane is connected to jonnyparris/dodo. This pull request wires the repository's coding agents to Polylane so they can investigate production directly, and records what Polylane sees in this codebase.

The button opens the investigation behind this pull request in the Polylane console.

What this pull request changes

• Updates AGENTS.md with a section that points coding agents at Polylane for production questions.

What Polylane sees

• Primary language: TypeScript.
• Deployment signals at the repository root: a CI pipeline, hosting platform configuration, a package manifest.
• Package manifests: package.json.
• Default branch: main.

Signal coverage

Polylane is indexing the codebase now. This section updates with route instrumentation coverage when the first review completes.

What happens next

• Polylane is preparing a follow-up pull request that improves logging on the paths operators need during an incident. It only opens when the changes are substantive.
• Every pull request in this repository gets a review against the live infrastructure.
• When something breaks in production, Polylane investigates and brings the evidence to your team.

Progress is visible in the Polylane console.

Came here from the CLI? Head back to your terminal to finish setup; this pull request can merge whenever your team is ready.

[polylane]

Note

Production impact unlikely.

Documentation, test, or CI-only change; nothing that runs in production is affected.

_{Polylane analysed ed78a51 for production impact.}