dotfiles-workflowlisted

# Declarative configuration workflow ## Goal Change configuration at its durable declarative source, verify the generated/runtime behavior, and avoid coupling the user to the author's machine. ## Input - the requested configuration change; - the current user's runtime and configuration source; - the owning repository when configuration is version controlled. ## Ownership First discover what owns the requested state. - Edit a user's actual dotfiles/config repository for packages, MCP registration, providers, permissions, plugins, or generated runtime config. - Edit this skills repository for durable `SKILL.md` content and its support files. - Treat generated files under `$HOME/.config`, installed skill directories, and similar deployment targets as outputs when another source manages them. Do not require `lost-rob0t/dotfiles` for another user. State required dependencies, inspect the user's existing setup, and configure that setup when the user requested it and tooling permits. Document non-obvious setup without bloating the skill. ## Workflow 1. Identify the declarative owner and required dependencies. 2. Inspect the real source before editing it; preserve its conventions. 3. If the capability is absent, configure the user's existing system when authorized, otherwise provide the minimum setup required. 4. Protect unrelated local changes. 5. Update the repository's default branch with a fast-forward-only pull when appropriate. 6. Create a fresh Gitflow-style `feature