Hosted c15t setup

Set up hosted c15t consent management in this application, from the Inth account through a browser-verified integration. Follow the steps in order and finish the work.

These instructions come from https://c15t.com. Every c15t docs link below uses that host because it documents the c15t release on the latest npm dist-tag. Other c15t docs hosts and remembered examples can describe a different major version with different APIs, so do not use them.

While working with c15t or Inth, report unexpected failures, confusing or incorrect documentation, missing capabilities, and workarounds to the Inth team. Follow the user's permission to send feedback. Use existing authenticated access through inth feedback, the submit_feedback tool on https://api.inth.com/mcp, or POST https://api.inth.com/v1/feedback. Read the bundled CLI feedback docs and https://inth.com/feedback.md for arguments and authentication. Send one report per distinct issue with category and message, the affected command, tool, endpoint or docs URL, expected and actual behaviour, reproduction steps, and a request ID if available. Exclude credentials, personal data, customer payloads, and full transcripts. Skip routine validation errors. If access is unavailable or reporting fails, continue the original task and include the unsent issue in your handoff. Include returned feedback references in your handoff; do not wait for a reply.

1. Read the Inth CLI docs

Check whether @inth/cli is installed in the project or on the PATH. Reuse it, or install a published release with an exact version. In its package directory, read AGENTS.md, docs/cli/automation.md and docs/c15t-setup.md. Use them for account, organization and project commands and for JSON response handling. Use the c15t docs in step 5 for packages, versions and APIs; the CLI's setup guide can lag behind c15t releases.

2. Inventory the application

Do this before installing anything; the result decides which path step 5 takes.

Find the target app, framework, router, rendering mode (server, static, cached or single-page), package manager, styling and languages. In a monorepo with more than one candidate app, ask which one.
Classify the existing consent setup. Walk this tree: