malts-project-initlisted

# MALTS Project Init Initialize a workspace with project-level Agent instructions and MALTS control files while preserving the user's execution gate: read-only discovery first, plan second, explicit authorization third, writes last. ## Non-Negotiable Gate - Treat read-only inspection as allowed. - Before any file write, edit, delete, move, dependency install, generated artifact, long-running service, git state change, remote write, or sub-agent dispatch, show a concrete plan and wait for explicit user authorization. - Accept authorization only when it responds to the latest concrete plan and uses words such as "执行", "确认执行", "做吧", "可以", "直接做", "继续", or an equivalent explicit approval. - If the user only asks what init does, whether it is needed, or how it differs from Claude Code `/init`, answer without writing files. - If additional work is discovered outside the approved plan, stop and ask for a new authorization. ## Workflow ### 1. Resolve MALTS Context Read these files before proposing writes: ```text MALTS_BOOT.md, when installed beside the active tool instruction file <GLOBAL_BOOT> <GLOBAL_MEMORY> ``` Derive `MALTS_ROOT` from `MALTS_BOOT.md` or `<GLOBAL_BOOT>` when either boot file is configured. Prefer the nearest active tool boot file for portable installs, and use an explicitly configured global boot file only when the user or project already provides one. If no boot file is configured, use the installed MALTS repository root after verifying that it contains `