TFX v0.2.0: Terminal Toolkit Release

TFX v0.2.0

RUNTIME DOGFOODING RELEASE

TFX v0.2.0 turns the toolkit into a more portable and proven runtime: the
release line now includes install scripts, Windows archives, explicit safe-vs-
strict API entrypoints, and real adoption outside the repo in both morfx and
mitl.

Highlights

• Try* is now the recoverable contract across the main runtime APIs, with
  explicit Must* wrappers for strict call sites.
• Release packaging now covers linux, darwin, and windows on amd64 and
  arm64.
• TFX now documents and demonstrates real dogfooding beyond itself, including
  orchestration of external tools and CI flows in other repos.
• The public docs, roadmap, and design guidance now draw a sharper line between
  “CLI runtime/toolkit” and “application/framework”.

What Changed

Safer Runtime Surface

• runfx, progrefx, flowfx, and the shared overload helpers now expose
  clear Try* / Must* semantics instead of relying on ambiguous short names
  for panic-prone paths.
• The docs now treat the safe path as the default contract and reserve panic
  wrappers for deliberate strict usage.

Better Distribution

• Release packaging now produces:
  • linux/amd64
  • linux/arm64
  • darwin/amd64
  • darwin/arm64
  • windows/amd64
  • windows/arm64
• Install scripts are now documented for Unix-like shells and PowerShell.
• The GitHub release workflow uploads both .tar.gz and .zip archives, so
  Windows assets are first-class instead of being built and then dropped.

Real Adoption

• morfx documents and uses TFX as a runtime around standalone refactoring
  workflows.
• mitl now carries a real tfx.yaml and validates core flows through TFX in
  CI.
• TFX’s own docs now describe those adopters directly instead of presenting the
  runtime as only a template or internal demo.

Validation

This release passes:

• make verify
• go run ./cmd/tfx --flow quality --run --quiet
• go run ./cmd/tfx --flow release --lane canary --run --quiet
• make release-archives

Notes

• The packaged wrapper reports v0.2.0 through ./dist/tfx --version.
• The project remains in v0.x, but this release is the clearest point yet
  where TFX behaves like a reusable runtime product rather than an internal
  toolkit experiment.

TFX v0.1.1: Terminal Toolkit Release

TFX v0.1.1

MAINLINE PATCH RELEASE

TFX v0.1.1 tightens the release story after the inaugural launch: the
project now publishes from main, the public docs match the actual package
surface, and local release packaging follows the current version automatically.

Highlights

• main is now the canonical default branch for the project.
• Stale remote release and Codex branches were removed from the public repo.
• The README now reflects the real public toolkit shape: runfx, formfx,
  flowfx, logfx, progrefx, writer, terminal, and the integrated
  cmd/tfx wrapper.
• make release-artifacts now resolves release notes from the current
  VERSION, so patch releases no longer inherit v0.1.0 notes by accident.

What Changed

Mainline Publishing

• GitHub default branch is now main
• Release work now lands and publishes from the canonical branch
• Remote branch noise was removed to keep the public repository clean

Documentation Accuracy

• Package coverage in README.md now includes runfx, formfx, and flowfx
• Feature bullets now include runtime orchestration and the config-driven wrapper
• cmd/tfx is described as the integrated wrapper across the full toolkit,
  not just runfx

Release Hygiene

• VERSION now reports v0.1.1
• Local release bundles copy docs/release-notes-$(VERSION).md
• The patch release leaves the v0.1.0 inaugural tag intact and publishes a
  new patch line instead of rewriting history

Validation

This release passes:

• make verify
• make release-artifacts

Notes

• The packaged wrapper reports v0.1.1 through ./dist/tfx --version.
• This is a patch release for correctness and publishing hygiene. The toolkit
  surface introduced in v0.1.0 remains the same.

TFX v0.1.0: Inaugural Terminal Toolkit Release

TFX v0.1.0

INAUGURAL RELEASE

TFX v0.1.0 is the first cohesive public release of the toolkit: a modular,
terminal-native Go stack for styled output, structured logs, progress UI,
forms, runtime orchestration, and a self-hosted wrapper that proves the whole
thing can ship real work end to end.

Highlights

• cmd/tfx is now a real integrated wrapper, not a throwaway demo.
• Pipelines run from tfx.yaml with named flows / profiles, --flow,
  --lane, --run, --json, --quiet, and --version.
• Wrapper sessions persist selected flow, lane, project, last run, and recent history.
• Lifecycle hooks (before_all, after_all, on_failure) are first-class.
• Step artifacts can be declared explicitly and are also discovered from common output directories.
• TFX now ships its own repository pipeline and can verify and release itself through TFX.

What Landed

Integrated Wrapper

• Live Overview, Flow, Forms, and Logs sections in cmd/tfx
• Interactive and non-interactive execution paths backed by the same runtime
• Structured machine-readable output for CI and automation

Modular Toolkit

• color, logfx, progrefx, runfx, flowfx, formfx, writer, and terminal
• progrefx.Stepper() and progrefx.Table() as first-class UI primitives
• Deterministic runtime behavior, cleaned public APIs, and a hardened lint/test baseline

Self-Hosted Delivery

• Root tfx.yaml with real ci, quality, and release flows
• Versioned release artifacts produced directly by the wrapper pipeline
• Release bundles with binaries, checksums, changelog, and release notes

Quick Start

go run ./cmd/tfx
go run ./cmd/tfx --flow ci --run
go run ./cmd/tfx --flow quality --run --quiet
go run ./cmd/tfx --flow release --lane canary --run
./dist/tfx --version

Validation

This release passes:

• go test ./...
• go build ./...
• go vet ./...
• golangci-lint run --timeout=5m
• go run ./cmd/tfx --flow ci --run --quiet
• go run ./cmd/tfx --flow quality --run --quiet
• go run ./cmd/tfx --flow release --lane canary --run --quiet

Notes

• The packaged wrapper reports v0.1.0 through ./dist/tfx --version.
• GitHub releases now have a matching tag workflow that builds multi-platform archives and publishes checksums automatically.
• This is the first release that looks like the original TFX vision: modular, expressive, terminal-native, and self-hosted.