kitaru-importer-builderlisted

# Kitaru importer builder Turn a representative provider export into a locally validated Kitaru importer. Keep the path from source evidence to normalized sessions explicit so the user can see what is preserved, approximated, or unavailable. Finish locally by default. Register code or upload trace data only when the user asks and approves each action separately. ## Core contract - Treat the installed Kitaru version and its offline schema as authoritative. Use repository examples as patterns, not proof that a command or field is installed. - Treat trace content as sensitive. Keep raw exports out of version control and redact fixtures before writing them into the target repository. - Keep export acquisition outside the importer. The parser consumes static bytes and parameters without network calls, filesystem writes, subprocesses, or credential reads. - Map the source before writing code. Record accepted payload shapes, identity, hierarchy, ordering, node fields, status, completeness, and intentionally unsupported data. - Prefer a private, single-file script importer. Use a package only when the user already has a distribution reason and the worker can install one exact pinned version. - Preserve useful incomplete evidence. Distinguish an unreadable payload, an invalid item, and a valid but incomplete session. - Join traces conservatively. A common key is insufficient without source-instance scope and meaningful turn order. - Do not overwrite an existing importer file, regi