feat(stackgen): switch to CLI MCP and expand deploy guidance (1.1.0)

[jigar-appcd]

Summary

• Switch the stackgen MCP server from the hosted HTTPS SSE endpoint to the local stackgen CLI over stdio, and update the README MCP line to match
• Expand POWER.md with the deploy flow, pre-flight validation, failure-recovery guidance, and an optional post-Apply ServiceNow change record; bump the power to 1.1.0
• Add steering docs (intent-to-deploy, deploy-setup, module-authoring, change-record), module/app-code authoring config, and the Aiden change-record helper scripts

Why

The hosted SSE endpoint doesn't expose the full tool set the deploy workflow depends on, and PAT-based auth is handled cleanly by the CLI. Moving to stackgen mcp over stdio makes the documented Plan/Apply flow actually reachable, and the new steering files keep that guidance out of the always-loaded POWER.md context.

Changes

File	Change
stackgen/mcp.json	HTTPS SSE -> local CLI stdio with STACKGEN_URL / STACKGEN_TOKEN, plus autoApprove for read and deploy tools
stackgen/POWER.md	Deploy flow, hard rules, pre-flight checks, API reference, troubleshooting; version 1.1.0
stackgen/steering/*.md	New: deploy setup, intent-to-deploy, module authoring, change record
stackgen/config/*	Module and app-code authoring rules
stackgen/scripts/*.sh	Aiden workflow + change-record setup check
README.md	stackgen MCP entry now reads CLI stdio

The change-record integration is entirely optional and never blocks a deploy: if the Aiden environment variables are unset, the step is skipped and the deploy result is unchanged.

Test plan

• Install the power locally and confirm the MCP server connects via stackgen mcp
• Confirm activation keywords load the power and that steering files load only when needed
• Run an end-to-end appstack create -> Plan -> Apply and verify the documented flow matches behavior
• Run stackgen/scripts/check-change-record-setup.sh and confirm both READY and NOT_CONFIGURED paths report correctly
• Verify the README stackgen entry shows CLI stdio

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.