Skip to content

CHANGELOG.md

Latest commit

 

History

History
45 lines (33 loc) · 2.09 KB

CHANGELOG.md

File metadata and controls

45 lines (33 loc) · 2.09 KB
Raw

Changelog

All notable changes to QuestionForge are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

Added

  • README — a "Development status" section (the honest maturity framing the sibling suites carry) and a Support section.

Changed

  • Data-protection policy moved to SECURITY.md — a new Data protection section states the non-negotiable "no real personal data in the repo" rule where readers expect it. The three .claude/rules/ policy files are no longer shipped; .claude/ is local development tooling and is fully git-ignored again (ADR-017 marked superseded).
  • CONTRIBUTING — sentence-case headings and a standardised licence line. Corrected documentation pointers: ADRs live in docs/decisions/ (not docs/adr/), and significant changes start as an issue or discussion (the repo carries no RFC folder).
  • SECURITY — vulnerability reporting standardised to GitHub's private vulnerability reporting link, with an aligned supported-versions table and a response-time expectation.

0.1.0 — First public release

First public release of QuestionForge: a teacher-led, AI-assisted framework for creating educational assessment questions from real teaching materials and exporting them to QTI.

Added

  • qf-scaffolding (Node) — MCP server providing the M1–M4 methodology guidance (content analysis, assessment planning, question generation, quality assurance) plus an M5 formatting flow.
  • qf-pipeline (Python) — MCP server for the technical pipeline: validation, auto-fix, and QTI export.
  • qti-core (Python) — standalone library that turns question markdown into QTI 2.2 packages; 16 supported question types.
  • Methodology guides (M1–M5) and a question-format reference.
  • Getting-started and workflow documentation.