zanmaiimportlisted

# import-bundle Filing for material from outside the vault. The AI plans and dialogues, `zanmai.py` does the writes. ## Directives 1. Bundle is the default. Material that shares a theme (a hobby, a project, a recurring topic) lives in one bundle under `<kind>/<theme-slug>/`. Singles only if the material is truly standalone (no thematic siblings in the import or vault, no overlap with existing bundles). See `classify-note` for the decision. 2. Existing bundle wins. If `<kind>/<theme-slug>/` already exists and the new material fits the theme, append. Do not create a sibling bundle for the same theme. 3. State changes via `zanmai.py` only. Never use `Write` or `Edit` directly for filing operations. The script handles created-date, source field, INDEX updates, activity-log appends, master-INDEX refresh and non-schema-field migration to the body. 4. Body verbatim under both modes. "Body verbatim" means user-written prose is preserved. Convention adaption (slug rename, wikilink updates after move, embed-path updates after move, frontmatter migration) is mechanic, not body edit. 5. Mandatory questions: the ones the target state leaves open, via `AskUserQuestion` form, never a fourth. Q2 scope is asked every time, it is the one thing the vault cannot derive. Q1 mode applies when a bundle is created; material going into a bundle that already exists follows the conventions that bundle already carries. Q3 conflict-policy applies when `index find` reports a slug collision, and is not