remove-demo-limits

Removing session caps from a self-hosted fork requires editing route guards and auth callbacks to bypass managed-template restrictions. This preserves unrelated sandbox behavior while eliminating hosted trial constraints.

Managed-template demo restrictions are hosted-only gating mechanisms that enforce session caps, message caps, and message deletion blockers. They exist to support a trial environment flow and limit forked repository functionality.

Cleaning up dead helper code and stale tests after removing trial caps involves removing or simplifying functions that only supported the hosted demo flow. You must then verify the updated repository still behaves correctly without these restrictions.

You can remove message deletion blockers and auth gating without breaking session behavior by applying coordinated edits to route guards and auth callbacks. This process preserves unrelated session and sandbox behavior intact while removing restrictions.

Removing hosted demo restrictions does require updating route guards and auth callbacks to eliminate hosted-only gating. Coordinated edits across helper code and tests are necessary to ensure the fork behaves like a normal product.