v0.1.0

[0.1.0] — 2026-06-27

Monorepo split + first multi-host release. pi-taskflow is now three
independently published packages built on a host-neutral engine, and the
taskflow engine runs on both Pi and Codex.

Added

• taskflow-core — the host-neutral engine (DSL, runtime, cache, verify,
  FlowIR, shared context tree, agent discovery, persistence, the
  SubagentRunner contract). Zero host-SDK dependency (depends only on
  typebox). Vendors the three small pi helpers it used (StringEnum,
  parseFrontmatter, getAgentDir) so it is fully standalone.
• codex-taskflow — run taskflow on OpenAI Codex: a codex exec-backed
  subagent runner, plus a dependency-free MCP server (codex-taskflow-mcp) that
  exposes taskflow_run/list/show/verify/compile to Codex users. Register with
  codex mcp add taskflow -- codex-taskflow-mcp.
• Host-neutral SubagentRunner seam — the engine drives any host via an
  injected runTask; piSubagentRunner and codexSubagentRunner are the two
  implementations.

Changed

• pi-taskflow is now the Pi adapter package (same published name — existing
  pi install npm:pi-taskflow users are unaffected). It depends on
  taskflow-core.
• Repo restructured to npm workspaces under packages/*. Each package now
  builds to dist/ (tsc → .js + .d.ts) and publishes the compiled
  output — required because Node refuses to type-strip .ts under node_modules.
  Dev still runs the TypeScript sources directly (a development export
  condition + --conditions=development resolves taskflow-core to src, so a
  fresh clone runs typecheck/test with no build step). CI builds and
  publishes the three packages in dependency order (core → pi → codex) on a
  v* tag.

Notes

• All 864 tests pass across the three packages (713 core + 135 pi + 16 codex).
• See RELEASE.md for the publish flow.