# Import provenance and version history

Rich Markdown (also called richmd) was imported into `Pi/rich-markdown` from the maintainer's existing local Pi package on 2026-10-17. Its manifest, lockfile, runtime release constant and README identify the available snapshot as **0.0.4**. The import leaves the active local installation untouched.

## Available evidence

The original local README describes this sequence:

| Version | Recorded local change | Repository source availability |
| --- | --- | --- |
| 0.0.1 | Initial local TUI rendering and MathJax formulas | No separate snapshot available |
| 0.0.2 | Richer Markdown layouts and private browser previews | No separate snapshot available |
| 0.0.3 | Full-row colored backgrounds, terminal Mermaid and local raster thumbnails | No separate snapshot available |
| 0.0.4 | Structural text math, frameless equations, expanded inline-formatting regression coverage and display-only recovery of translated CJK bold labels | Imported source snapshot |

The earlier summaries are preserved as **documented local history** in both changelogs. They are not verified historical source releases. Original dates are unknown, so no dates, source snapshots, commits, branches or tags are synthesized for 0.0.1–0.0.3. Existing repository tags for other tools are untouched. If authentic older snapshots become available, review their provenance separately; do not point older tags at the current implementation.

## Import boundary

- Include `index.ts`, `src/`, the synthetic `assets/demo.png`, tests and pinned dependency manifests.
- Preserve the renderer, command names, configuration filename, package identity and persisted entry identifiers. This is a repository integration, not a renderer redesign.
- Apply one safety correction found during import review: reject local image reads on unsupported platforms and network file paths before filesystem lookup. The previous Windows rejection occurred after a potential UNC lookup. Isolated mocks verify that rejected inputs cannot reach `realpath` or `open`; no real network share is contacted. The active local installation remains unchanged.
- Replace machine-specific test/typecheck paths with discovered Pi 1.3.0 SDK/TUI paths and the repository's Translator card. Add isolated host-discovery regressions.
- Add bilingual guides/changelogs, repository/license metadata, ignore rules and this provenance record.
- Exclude `node_modules`, `.pi`, private settings, credentials, conversations, logs and generated proof/preview files. The demo image is a synthetic three-panel illustration.
- Do not reinstall the extension, patch Pi's managed files, alter user preferences, or publish to npm as part of this import.

## Release policy

`rich-markdown` is the independent long-lived branch, and `rich-markdown-v0.0.4` is the first repository release tag. The release-policy baseline **0.0.3** denotes the last documented local predecessor, not an existing Git snapshot. With no Rich Markdown package on main, only the available 0.0.4 snapshot is eligible; lower versions and jumps to 0.0.5 are rejected. Once imported, normal current-main comparison applies: the next routine release is 0.0.5, with all manifests and both changelogs updated together. Other tools' versions and release histories do not change.

Release only through a tested version-release PR and a merge commit on main. Tag that merge commit, never a development commit. Keep the branch and merge released main back. The repository has no active CI; report local tests, dependency audit and manual visual limitations honestly. See the [repository release workflow](https://github.com/Orbit-Labs-AI/Orbit-Tools/blob/main/docs/releases.md).