🛠️ Update various documentation, scripts, and configuration templates to enhance clarity, functionality, and maintainability across the project
This commit is contained in:
15
README.md
15
README.md
@@ -20,6 +20,7 @@ This initial implementation provides:
|
||||
- Publish, update, and verify scripts
|
||||
- Scripted VS Code settings merge for managed Copilot-related keys
|
||||
- Scripted Copilot CLI environment wiring through a managed sourced fragment
|
||||
- Scripted managed MCP config generation for VS Code and Copilot CLI
|
||||
|
||||
## Operating Model
|
||||
|
||||
@@ -51,6 +52,20 @@ per-machine copies. They also merge the managed VS Code settings keys and add a
|
||||
small managed shell or PowerShell profile block for Copilot CLI environment
|
||||
variables without replacing the rest of the user config.
|
||||
|
||||
Bootstrap also generates managed user-level MCP configuration for VS Code and
|
||||
Copilot CLI from the tracked templates in `config/mcp/`. Machine-local MCP
|
||||
values live in `.local/mcp.local.jsonc`, which bootstrap creates from the
|
||||
tracked example file on first run.
|
||||
|
||||
Today the managed MCP set is:
|
||||
|
||||
- Playwright for VS Code
|
||||
- Filesystem for VS Code and Copilot CLI
|
||||
- Gitea/Forgejo for VS Code and Copilot CLI when enabled locally
|
||||
|
||||
`install/update.*` now reruns bootstrap after pulling so those managed config
|
||||
files propagate when this repository changes.
|
||||
|
||||
## Next Docs
|
||||
|
||||
The rest of the handbook will live in `docs/` and will cover architecture,
|
||||
|
||||
Reference in New Issue
Block a user