The compose-personas work shipped (5 vike-* composers + the neutral guardrail, the --compose-extensions flag, and the publish-safe default gate), but the docs never caught up.
Drift to fix:
ai-autopilot/README.md Personas section names a nonexistent universalOrmModeler and calls the default stack "Vike + universal-orm"; the built-in is dataModeler (Prisma), and the code's canonical default is "Vike + Prisma" (steps.ts, index.ts, library.ts). Fix the name + stack, and document the opt-in vikeExtensionPersonas set.framework/README.md CLI section omits --compose-extensions entirely and never explains the composer path or the publish gate. Add both.framework/src/cli.ts --help describes the flag as "vike-auth for auth" only; name the full set.
Docs-only, no behavior change.
Out of scope (flagging, not fixing here): "Vike + universal-orm" also appears across the 7 prompt bodies and test fixtures while the code default is Prisma. That is a separate, agent-facing inconsistency that needs a product call.
The compose-personas work shipped (5 vike-* composers + the neutral guardrail, the
--compose-extensionsflag, and the publish-safe default gate), but the docs never caught up.Drift to fix:
ai-autopilot/README.mdPersonas section names a nonexistentuniversalOrmModelerand calls the default stack "Vike + universal-orm"; the built-in isdataModeler(Prisma), and the code's canonical default is "Vike + Prisma" (steps.ts, index.ts, library.ts). Fix the name + stack, and document the opt-invikeExtensionPersonasset.framework/README.mdCLI section omits--compose-extensionsentirely and never explains the composer path or the publish gate. Add both.framework/src/cli.ts--helpdescribes the flag as "vike-auth for auth" only; name the full set.Docs-only, no behavior change.
Out of scope (flagging, not fixing here): "Vike + universal-orm" also appears across the 7 prompt bodies and test fixtures while the code default is Prisma. That is a separate, agent-facing inconsistency that needs a product call.