Journey Substrate

It asks whether you want to connect your deployed app to your substrate so functions get ctx.substrate for AI memory and agent state. The skill handles the whole flow: checks if your substrate is provisioned, calls the right API or MCP tool to link it, verifies the connection, and writes the artifact. It defaults to skip in hackathon mode, which makes sense since most throwaway apps don't need cross-session memory. One good call here is refusing to auto-link without explicit consent, treating substrate as privacy-sensitive rather than just another feature flag.