repo create without a framework produces a repository init rejects (Legacy Builder enabled)

[angeloashmore]

Versions

• prismic-cli-poc: v1.13.0
• node: v24.x

Reproduction

Additional Details

repo create sends framework: "other" when run outside a supported framework project (src/commands/repo-create.ts:49). The backend then provisions the repository with quotas.sliceMachineEnabled: false, and init rejects it via checkIsTypeBuilderEnabled (src/project.ts:226-235) with:

This command requires the Type Builder in your repository.

Verified against a live repository: framework: "other" → sliceMachineEnabled: false; the same flow through init in a Next.js project → framework: "next", sliceMachineEnabled: true.

Steps to reproduce

1. In an empty directory, run prismic repo create --name my-repo.
2. Run prismic init --repo <domain> (in any directory, or add a framework later).

What is expected?

A repository created by the CLI is usable by the CLI: init and model commands work without manually turning off Legacy Builder in repository settings.

What is actually happening?

The new repository has the Legacy Builder enabled (quotas.sliceMachineEnabled: false), so init fails with TypeBuilderRequired until the user flips the setting in the repository settings UI.

🤖 Generated with Claude Code