cut-lifecycle

Apply Guillotine chamber (tenant) isolation on every read and write.

Diagnose failing Guillotine requests in production.

Restore access for a customer chamber during an incident.

Land Guillotine changes quickly when the typechecker is already clean.

Add or change PostgreSQL schema for Guillotine using TypeORM migrations.

Place new Guillotine HTTP endpoints and domain logic in the correct NestJS module.

Keep Guillotine list and gallery endpoints fast under large chambers.

Make local Guillotine setup work on the first clone.

Fix a schema mistake quickly when a migration already ran in shared environments.

Author or change Guillotine recipes that provision blades, pipelines, and sequences.

Create, update, and publish Guillotine cuts (records) with version rows.

Implement computed edges on Guillotine blades.