Roadmap

[ SHIP · DONE VS TO DO ]

What's already shipped (repo + site) vs what's still open before npm and "stable" claims line up.

SYSTEM ORIGIN

v1.2.2

  • 01
    DONE

    Core CLI shipped locally

    Done (in repo): init + generate (default), templates, prompts. Matches README / source layout.

  • 02
    DONE

    README: discoverability

    Done: install, badges, quick start, example, usage. Same as documented in the repo README.

  • 03
    DONE

    Package metadata for npm and GitHub

    Done: repository, bugs, PR/discussion URLs, homepage.

  • 04
    DONE

    Public docs / marketing site

    Done (external): site at your homepage; keep it in sync with the real CLI commands.

  • 05
    TO DO

    npm publish: name + account

    To do: fix E404. Confirm npm whoami, who owns Genesis-env on npm, scoped rename or access. Until this works, installs from npm as documented may not match your package.

  • 06
    TO DO

    package.json polish

    To do: fill keywords, author (and optional files / engines) so npm search and trust look complete.

  • 07
    TO DO

    Publish tarball hygiene

    To do: npm warned about .gitignore as fallback. Consider .npmignore or files so only dist + essentials ship (avoid publishing unnecessary src if you don’t want that).

  • 08
    TO DO

    Tests & CI

    To do: npm test is still a stub; add real tests + CI (e.g. GitHub Actions) before calling it “stable.”

  • 09
    TO DO

    Roadmap vs product

    To do: docs/ROADMAP.md lists validation, merge, secret managers, etc. Align site, README, and roadmap so users aren’t misled about what the CLI actually does today.

  • 10
    TO DO

    Post v1 quality and ecosystem

    To do: changelog/releases, issue templates usage, semver discipline, and v0.2+ themes (progress UI, stricter validation, optional keys, etc.).