docs: refresh QTI documentation scope

Align documentation with the current QTI 2.x/3.0 project scope, capture the review baseline, and remove obsolete planning artifacts.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: chillenious

.claude/CLAUDE.md

@@ -2,13 +2,13 @@
 
 ## Project Context
 
-This is an educational assessment framework implementing QTI 2.x standards for K-12 assessments.
+This is an educational assessment framework implementing QTI standards for K-12 assessments.
 
 **Critical Requirements**:
 
 - **Accessibility**: WCAG 2.2 Level AA compliance is mandatory
 - **Cross-platform**: Components must work on desktop and mobile (touch-friendly)
-- **Standards compliance**: Must adhere to QTI 2.x specification
+- **Standards compliance**: Must adhere to the relevant QTI specification version
 - **Type safety**: TypeScript strict mode is enforced
 - **Modern Svelte**: Using Svelte 5 with runes
 

.claude/skills/api-design-reviewer/SKILL.md

@@ -239,7 +239,7 @@ export class Player {
 ### 7. Framework-Specific Considerations
 
 **For QTI/Educational Assessment Projects:**
-- Does the API respect QTI 2.2 standard terminology?
+- Does the API respect QTI standard terminology for the relevant version?
 - Are QTI roles (candidate, scorer, author, etc.) properly typed?
 - Is response processing type-safe?
 - Are interaction types properly discriminated?

.claude/skills/assessment-content-validator/SKILL.md

@@ -25,7 +25,7 @@ Invoke this skill when:
 This skill performs both **technical validation** and **content quality review**:
 
 ### Technical Validation
-- QTI 2.x specification compliance
+- QTI specification compliance for the relevant version
 - Well-formed XML structure
 - Correct response processing logic
 - Proper interaction configuration
@@ -498,7 +498,7 @@ bun --filter @pie-qti/to-pie test
 
 ## QTI/PIE Knowledge Base
 
-### QTI 2.2 Interaction Types (21 total)
+### Standard QTI Interaction Types (21 total)
 
 1. **choiceInteraction** - Multiple choice (single or multiple response)
 2. **orderInteraction** - Order/sequence items
@@ -524,7 +524,7 @@ bun --filter @pie-qti/to-pie test
 
 ### Response Processing Templates
 
-**QTI 2.2 Standard Templates:**
+**Standard Response Processing Templates:**
 1. `MATCH_CORRECT` - All-or-nothing scoring
 2. `MAP_RESPONSE` - Partial credit via response mapping
 3. `MAP_RESPONSE_POINT` - Partial credit for coordinates
@@ -550,7 +550,7 @@ PIE extends QTI with modern, JavaScript-based elements:
 
 ## References
 
-- **QTI 2.2 Specification**: http://www.imsglobal.org/question/qtiv2p2/imsqti_v2p2.html
+- **QTI Specifications**: https://www.1edtech.org/standards/qti
 - **PIE Documentation**: https://github.com/pie-framework/pie-elements
 - **Item Writing Best Practices**: Educational measurement literature
 - **Accessible Assessment**: WCAG 2.2 + assessment-specific guidelines

CONTRIBUTING.md

@@ -6,34 +6,39 @@ Thank you for your interest in contributing to the PIE-QTI project! This documen
 
 ### Prerequisites
 
-- **Bun** ≥1.1.0 (package manager and runtime)
+- **Bun** ≥1.3.11 (package manager and runtime)
 - **Node.js** ≥20.19.0 (for compatibility)
 - **Git** for version control
 
 ### Getting Started
 
 1. **Clone the repository**
+
    ```bash
    git clone https://github.com/pie-framework/pie-qti.git
    cd pie-qti
    ```
 
 2. **Install dependencies**
+
    ```bash
    bun install
    ```
 
 3. **Build all packages**
+
    ```bash
    bun run build
    ```
 
 4. **Run tests**
+
    ```bash
-   bun test
+   bun run test
    ```
 
 5. **Start development server**
+
    ```bash
    cd apps/demo
    bun run dev
@@ -45,8 +50,13 @@ This is a monorepo with multiple packages:
 
 - **`packages/item-player/`** - Core item player (21 interaction types)
 - **`packages/assessment-player/`** - Multi-item assessment player
+- **`packages/default-components/`** - Default web-component renderers for QTI interactions
+- **`packages/qti-common/`** - QTI 2.x / 3.0 version abstraction utilities
+- **`packages/to-pie/`**, **`packages/pie-to-qti2/`**, **`packages/core/`** - Transformation packages
 - **`packages/player-elements/`** - Web component wrappers
+- **`tools/cli/`** - Transform and analysis CLI
 - **`apps/demo/`** - Demo application
+- **`apps/docs/`** - Published docs site
 - **`apps/transform/`** - Internal transform reference harness; not part of supported app CI
 
 ## Code Standards
@@ -67,9 +77,9 @@ This is a monorepo with multiple packages:
 
 - Write tests for new features
 - Maintain existing test coverage
-- Run tests with `bun test`
+- Run tests with `bun run test`
 - For QTI certification-facing changes, run `bun run test:certification:public`
-- E2E tests: `bun run test:e2e` (requires dev server running)
+- E2E tests: `bun run test:e2e` (Playwright starts the demo server unless `PLAYWRIGHT_REUSE_EXISTING_SERVER=true`)
 
 ### Commits
 
@@ -79,17 +89,18 @@ This is a monorepo with multiple packages:
 
 ## Pull Request Process
 
-1. **Fork the repository** and create a branch from `main`
+1. **Fork the repository** and create a branch from `master`
 
 2. **Make your changes**
    - Follow code standards
    - Add tests for new functionality
    - Update documentation as needed
 
 3. **Test your changes**
+
    ```bash
    bun run build
-   bun test
+   bun run test
    bun run test:certification:public  # Required for QTI delivery behavior changes
    bun run test:e2e  # If applicable
    ```
@@ -108,11 +119,11 @@ This is a monorepo with multiple packages:
 
 ### Adding New Interaction Types
 
-1. Create processor in `packages/item-player/src/processors/`
-2. Add Svelte component in `packages/item-player/src/components/`
-3. Update `InlineInteractionRenderer.svelte` or `BlockInteractionRenderer.svelte`
-4. Add tests in `packages/item-player/tests/processors/`
-5. Update documentation in README
+1. Add extraction and data-model support under `packages/item-player/src/interactions/<interaction>/`.
+2. Add the default Svelte custom element under `packages/default-components/src/plugins/<interaction>/`.
+3. Register the interaction in the item-player interaction modules and the default-components plugin index.
+4. Add extractor, component, and browser-visible tests that cover the interaction's QTI attributes and response semantics.
+5. Update the relevant README, PRD, eval YAML, and certification matrix entries when behavior or coverage changes.
 
 ### Fixing Bugs
 
@@ -129,7 +140,7 @@ This is a monorepo with multiple packages:
 
 ## Security
 
-If you discover a security vulnerability, please follow our [Security Policy](SECURITY.md) for responsible disclosure.
+If you discover a security vulnerability, please follow the security model in [docs/prds/architecture/security.md](docs/prds/architecture/security.md) and contact the maintainers privately before opening a public issue.
 
 ## Questions?
 

README.md

@@ -30,15 +30,15 @@ This project provides two major capabilities:
 
 Many Renaissance partners exchange content in **QTI format**, so bidirectional QTI ↔ PIE transformation is essential. This project **open sources that transformation framework** for partners and the broader community.
 
-We also built a **spec-complete QTI player** because a modern, open-source option was missing—and we needed one for previewing, analysis, and "convert then render" workflows.
+We also built a **standards-oriented QTI player** because a modern, open-source option was missing—and we needed one for previewing, analysis, and "convert then render" workflows.
 
 ---
 
-## Part 1: QTI Players (2.2 & 3.0)
+## Part 1: QTI Players
 
-> **Status**: Production-ready (QTI 2.2); QTI 3.0 infrastructure complete; PCI/PNP/Catalog implemented (see STATUS.md)
+> **Status**: Production-ready for the supported QTI delivery scope; QTI 3.0 infrastructure, PCI, PNP, and Catalog support are implemented (see STATUS.md)
 
-Full-featured players for rendering QTI 2.2 and 3.0 assessment content in the browser.
+Full-featured players for rendering QTI assessment content in the browser.
 
 ### Version-Agnostic Architecture
 
@@ -55,7 +55,7 @@ See [`@pie-qti/qti-common`](packages/qti-common/README.md) for the version abstr
 
 Renders and scores individual QTI items:
 
-- **21 interaction types** — All QTI 2.2 interactions supported
+- **21 standard interaction types** — Standard QTI interactions supported through the shared extraction/rendering path
 - **45 response processing operators** — Complete client-side scoring
 - **Role/view-aware rendering** — candidate, scorer, author, tutor, proctor, testConstructor
 - **Adaptive items** — Multi-attempt workflows with progressive feedback
@@ -90,7 +90,7 @@ See the [ACME Likert plugin](packages/acme-likert-plugin/) for a complete extens
 
 Components render via web components (Shadow DOM) with a CSS variable contract:
 
-- **Theme tokens** — DaisyUI-compatible variables (`--p`, `--a`, `--b1`, `--bc`, etc.)
+- **Theme tokens** — PIE-QTI CSS variables (`--pie-qti-*`) with DaisyUI bridge support
 - **`::part()` hooks** — Stable part names for host-side style refinement
 - **Zero-CSS fallback** — Components render correctly with no host styles
 
@@ -113,7 +113,7 @@ See [`@pie-qti/i18n`](packages/i18n/) for the complete i18n API and [custom tran
 
 > **Status**: Under active development
 
-Bidirectional transformation between QTI 2.2 XML and PIE JSON.
+Bidirectional transformation between QTI XML and PIE JSON: QTI → PIE ingest, plus PIE → QTI 2.2 export.
 
 ### Architecture Overview
 
@@ -138,7 +138,7 @@ See [Transformation Engine Documentation](docs/TRANSFORMATION-ENGINE.md) for com
 - Best-effort semantic transformation otherwise
 - Vendor extension system for custom QTI variants
 
-**PIE → QTI** (`@pie-qti/pie-to-qti`)
+**PIE → QTI** (`@pie-qti/pie-to-qti2`)
 
 - Lossless reconstruction when PIE contains embedded QTI
 - Generator registry for custom PIE model handling
@@ -172,7 +172,7 @@ Command-line tool for batch operations:
 bun run pie-qti -- transform input.xml --format qti22:pie --output output.json
 
 # Analyze QTI content
-bun run pie-qti -- analyze ./content-package/
+bun run pie-qti -- analyze-qti ./content-package/
 
 # See all commands
 bun run pie-qti -- --help
@@ -206,10 +206,13 @@ bun run verify:apps:deploy
 bun run verify:publish
 ```
 
-CI uses two required quality lanes on PRs:
+CI runs the main quality gates on PRs:
 
-- **Deployability lane:** `verify:apps:deploy` (apps/docs and apps/demo production buildability)
-- **Publishability lane:** `verify:publish:quick` (metadata, exports, publint, attw, pack, deps, source exports)
+- **Lint/type gates:** Biome, Svelte checks, TypeScript, translation coverage, and unit tests
+- **Certification gate:** `test:certification:public`
+- **Accessibility gate:** `verify:a11y`
+- **Deployability gate:** `verify:apps:deploy` (apps/docs and apps/demo production buildability)
+- **Publishability gate:** `verify:publish:quick` (metadata, exports, publint, attw, pack, deps, source exports)
 
 Release behavior is lockstep and patch-only for publishable `packages/*`:
 
@@ -225,9 +228,10 @@ To test with [pie-players](https://github.com/pie-framework/pie-players) locally
 ### GitHub Pages Preview
 
 ```bash
-bun run build:pages
+bun run verify:apps:deploy
+bun run docs:preview
+# In another shell, preview the examples app if needed:
 bun run preview:pages
-# Open http://localhost:4173/pie-qti/
 ```
 
 ---
@@ -237,6 +241,8 @@ bun run preview:pages
 ### Architecture & Project Layout
 
 - **[Architecture Guide](docs/ARCHITECTURE.md)** — System design, package map, extensibility, theming, and security
+- **[PRD Inventory](docs/prds/INVENTORY.md)** — Canonical rationale and acceptance criteria map
+- **[Documentation Review](docs/DOCUMENTATION-REVIEW.md)** — Documentation inventory, review findings, and maintenance rules
 
 ### Players
 
@@ -251,17 +257,16 @@ bun run preview:pages
 - **[Transformation Engine](docs/TRANSFORMATION-ENGINE.md)** — Architecture, plugin system, and extensibility
 - **[Transformation Guide](docs/PIE-QTI-TRANSFORMATION-GUIDE.md)** — Bidirectional transform overview
 - **[Vendor Plugin Guide](docs/VENDOR-TRANSFORM-PLUGIN-GUIDE.md)** — Building custom vendor plugins
-- **[Configuration Guide](docs/CONFIGURATION.md)** — Storage backends, plugins, and environment setup
-- **[Migration Guide](docs/MIGRATION_GUIDE.md)** — Upgrading from legacy storage to new architecture
+- **[Source Profiles](docs/SOURCE-PROFILES.md)** — Real-world QTI source detection and import adaptation
 - **[Transform Reference Harness](apps/transform/README.md)** — Internal playground for transformation experiments
 - **[CLI](tools/cli/README.md)** — Command-line batch operations
 - **[QTI → PIE](packages/to-pie/README.md)** — QTI to PIE transformer
-- **[PIE → QTI](packages/pie-to-qti/README.md)** — PIE to QTI transformer
-- **[IMS Content Packages](packages/pie-to-qti/docs/MANIFEST-GENERATION.md)** — Manifest generation
+- **[PIE → QTI](packages/pie-to-qti2/README.md)** — PIE to QTI transformer
+- **[IMS Content Packages](packages/pie-to-qti2/docs/MANIFEST-GENERATION.md)** — Manifest generation
 
 ### Extensibility
 
-- **[Custom Generators](packages/pie-to-qti/CUSTOM-GENERATORS.md)** — Adding PIE model support
+- **[Custom Generators](packages/pie-to-qti2/CUSTOM-GENERATORS.md)** — Adding PIE model support
 - **[ACME Likert Plugin](packages/acme-likert-plugin/README.md)** — Player extensibility example
 
 ---

STATUS.md

@@ -12,8 +12,8 @@ workflows are the authoritative sources for detailed behavior.
 The core player packages are pre-1.0 but considered production-ready for the
 supported QTI delivery scope.
 
-- `@pie-qti/item-player` renders single QTI items and supports all standard QTI
-  2.2 item interaction types.
+- `@pie-qti/item-player` renders single QTI items and supports standard QTI
+  item interaction types across the supported delivery scope.
 - `@pie-qti/assessment-player` sequences QTI assessment tests, sections, item
   refs, item session control, rubric blocks, and response submission.
 - `@pie-qti/default-components` supplies the default web-component renderers.
@@ -77,6 +77,9 @@ The current high-signal verification commands are:
 - `bun run typecheck`
 - `bun run build`
 - `bun run test:certification:public`
+- `bun run verify:a11y`
+- `bun run verify:apps:deploy`
+- `bun run verify:publish:quick`
 
 The full suite was last run successfully as part of the interaction module
 refactor on 2026-05-04.