AI agents' training data routes them to the legacy Slice Machine workflow

[angeloashmore]

Is your feature request related to a problem? Please describe.

AI agents start Prismic projects with npx @slicemachine/init because their training data contains the legacy workflow. Nothing at that entry point tells the agent that a newer path exists. The session goes down the wrong path from the first step: legacy tooling, a different file layout, and no contact with the current CLI.

Describe the solution you'd like

This issue documents the problem for a later brainstorm. It does not prescribe a solution.

One idea: add a deprecation message to the Slice Machine entry points. The message points to npx prismic init and npx prismic docs list. Agents on the legacy path then get redirected at the point where they reliably arrive.

Describe alternatives you've considered

Additional context

This issue is in the CLI repository for visibility. Slice Machine is not in active maintenance.

[angeloashmore]

One possible direction: deprecate Slice Machine and show a message that points the agent to the new workflow.

The npm deprecation notice is a good candidate. npm prints it when the package is installed, so npx @slicemachine/init shows it before any Slice Machine code runs.

Entry points where we can show a message, from earliest to latest:

1. npm registry metadata. Agents often read the package description, the README, or npm view output before they install. Update the description and README of slice-machine-ui, @slicemachine/init, and the adapters to say: deprecated, use npx prismic init.
2. npm deprecation notice. npm prints the notice during install and npx fetch. This is the earliest programmatic point.
3. Runtime banner. Print a redirect message when @slicemachine/init or slice-machine-ui starts. Install output is noisy and agents can miss the npm notice there. A banner in the command output is hard to miss because the agent reads that output directly.
4. GitHub README. Agents fetch repository READMEs when they research a package. An archive notice or deprecation banner reaches them there.

These points are not exclusive. The npm notice is the earliest, and the runtime banner is the most reliable. We can do both.

The message can also tell the agent to install the skill directly (see prismicio/skills#5).