lpm-config

# Configure lpm Create and modify lpm config on macOS exclusively through `lpm config get` and `lpm config apply`. Never modify a live project, repo, global, or template config directly with an editor, filesystem tool, patch, redirection, or script. The CLI validates the candidate before the app atomically replaces the destination. ## Load only the relevant reference - Read [references/core.md](references/core.md) for project identity, services, dependencies, profiles, duplicates, linked Git worktrees, and project creation. - Read [references/actions.md](references/actions.md) when adding or changing actions, buttons, terminals, inputs, ports, shortcuts, or nested menus. - Read [references/sharing.md](references/sharing.md) for `.lpm.yml`, global config, templates, `extends`, layering, and sparse overrides. - Read [references/ssh.md](references/ssh.md) for remote projects or `mode: sync`. - Read [references/validation.md](references/validation.md) before preparing a candidate and follow its transactional workflow. ## Resolve the target Honor an explicit project or layer from the user. Otherwise run: ```bash lpm config resolve --cwd . --json ``` Interpret the result: - One match: use the returned project name with `lpm config get`; never edit the returned `path`. - Multiple matches: ask which candidate to use. - No match: offer to create a project for the current directory or configure one of the returned `available` projects. Use these explicit layer overrides: - “g...