Put template guides beside channel, web, and mobile code - #15
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Template links currently open setup documents apart from the runnable code. This removes
templates/and makes each app README its setup guide, with one homepage CTA opening the code directory.The app layout is now
apps/channel,apps/web, andapps/mobile. The standalone MCP and terminal-chat demos are removed because the retained templates do not depend on them. Workspace configuration, the lockfile, development/verification commands, documentation, and coding-agent instructions follow the new paths. The default development command starts web when a managed Channel is not configured.This preserves the approved web persistence flow and mobile runtime. Remote Ambiguous MCP integration remains available. Slack delivery work stays in #8.
Validation: clean install, root verification, web production build, development-command smoke checks, tracked stale-path scan, and relative Markdown links. Mobile source and dependencies are unchanged.