Skip to content

docs: add CHANGELOG.md with version history#38

Closed
TerminalGravity wants to merge 4 commits intomainfrom
docs/add-changelog
Closed

docs: add CHANGELOG.md with version history#38
TerminalGravity wants to merge 4 commits intomainfrom
docs/add-changelog

Conversation

@TerminalGravity
Copy link
Copy Markdown
Collaborator

Adds a CHANGELOG.md covering v3.0.0 through v3.2.0 with categorized changes (Added/Fixed/Improved/Breaking). Also links it from the README nav bar.

… and contracts

The README references .preflight/ config extensively but there were no
concrete example files to copy. This adds a ready-to-use examples/.preflight/
directory with annotated config.yml, triage.yml, and contracts/api.yml,
plus a README explaining how to use them.
Created examples/USAGE_EXAMPLES.md with 8 real-world scenarios showing
what each tool looks like in practice: preflight_check catching vague
prompts, scope_work creating execution plans, enrich_agent_task for
sub-agents, sharpen_followup resolving ambiguity, session health checks,
semantic history search, weekly scorecards, and prompt grading.

Added link to usage examples in README nav bar.
Copy link
Copy Markdown
Collaborator Author

@TerminalGravity TerminalGravity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CHANGELOG looks great — covers all the major releases with the right level of detail. The link refs at the bottom are a nice touch.

Two things:

  1. Overlap with #36 and #37 — this PR includes the troubleshooting section and the Usage Examples nav link, which are also in those PRs. You'll hit merge conflicts if any of them land first. Suggest rebasing this onto whichever lands first, or consolidating the README changes into one PR.

  2. The 2.x entry2025-01-xx as a date looks placeholder-ish. Either pin it to an approximate date or just say Early 2025 without the bracket format since it wasn't a formal release anyway.

Otherwise solid — ship it after sorting out the rebase order.

@TerminalGravity
Copy link
Copy Markdown
Collaborator Author

Superseded by newer PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant