QAMap 0.3.1

QAMap 0.3.1 is a documentation and packaging patch release.

Why this patch exists:

• Removed a stale animated README demo that still showed the previous project name and .codeward/flows.yml.
• Kept the public README text-first until a fresh demo can be recorded from the current published package and .qamap/manifest.yaml flow.
• Published a corrected npm README without the outdated GIF asset.

Install and run:

pnpm dlx @ivorycanvas/qamap qa . --base origin/main --head HEAD

Validation:

• pnpm test passed: 95 tests.
• pnpm pack --dry-run passed with 97 files and no committed demo GIF.
• npm publish --dry-run --access public passed for @ivorycanvas/qamap@0.3.1.
• Published package smoke passed: pnpm dlx @ivorycanvas/qamap --version -> 0.3.1.

Package: https://www.npmjs.com/package/@ivorycanvas/qamap

QAMap 0.3.0

QAMap 0.3.0 is the agent-first QA loop release.

Install and run:

pnpm dlx @ivorycanvas/qamap qa . --base origin/main --head HEAD

Highlights:

• Renames the package to @ivorycanvas/qamap while keeping qamap as the CLI binary.
• Adds qamap qa --format agent for compact coding-agent handoff.
• Binds manifest check hints to generated Playwright draft steps.
• Observes changed endpoints instead of hiding them behind synthetic mocks.
• Excludes generated drafts from test-suite evidence.

Validation:

• pnpm test passed: 95 tests.
• npm publish --dry-run --access public passed for @ivorycanvas/qamap@0.3.0.
• Published package smoke passed: pnpm dlx @ivorycanvas/qamap --version -> 0.3.0.

Package: https://www.npmjs.com/package/@ivorycanvas/qamap

CodeWard 0.2.1

Summary

CodeWard 0.2.1 sharpens the local-first PR QA workflow around manifest-backed E2E planning and agent handoff.

Highlights

• Adds codeward qa as a manifest-free local QA skill entrypoint for PR comment/checklist drafts.
• Ships skills/codeward-pr-qa/SKILL.md so local agent workflows can run CodeWard before PR handoff.
• Adds external manifest preview support with --manifest <file> for read-only adoption testing.
• Improves manifest context capture, repair hints, and validation snapshot docs.

Validation

• pnpm run release:check passed.
• 90 tests passed.
• pnpm scan reported 0 findings.
• Coverage gates passed: 85.27% line, 81.59% branch, 94.26% function.
• npm publish --dry-run --access public passed before publish.

Published to npm as @ivorycanvas/codeward@0.2.1.

CodeWard 0.2.0

Summary

CodeWard 0.2.0 introduces the verification manifest feedback loop: a repo-local QA memory that helps turn branch changes into manifest-backed E2E plans and draft tests.

Highlights

• Adds codeward manifest init, manifest validate, and manifest explain.
• Adds .codeward/manifest.yaml schema support through schema/codeward-manifest.schema.json.
• Uses manifest matches in verify, e2e plan, and e2e draft output.
• Promotes matched manifest flows into Playwright, Maestro, and manual draft generation.
• Documents the default-branch baseline workflow so shared team manifests start from the repository's default QA map.
• Keeps generated drafts conservative with readiness evidence for missing runner setup, selectors, fixtures, and validation proof.

Validation

• pnpm run release:check passed on main.
• npm publish --access public succeeded for @ivorycanvas/codeward@0.2.0.
• Package tarball includes dist, docs, schema, README.md, CHANGELOG.md, LICENSE, and package.json.

CodeWard 0.1.1

Documentation and launch polish release.

Changed

• Refreshed the README first screen with Install & Quick Start, npm install commands, and clearer local-first/no-LLM-token positioning.
• Added a 30-second demo GIF and quick start walkthrough showing how a checkout-form PR becomes a domain-aware Playwright draft.
• Updated npm package metadata keywords and description to match the PR verification and E2E draft generation positioning.

Validation

• pnpm run release:check
• 80/80 Node tests passed
• CodeWard self-scan: 0 findings
• Coverage: lines 85.35%, branches 83.32%, functions 93.48%
• npm package published as @ivorycanvas/codeward@0.1.1

CodeWard 0.1.0

0.1.0 - 2026-07-01

Initial public release.

Added

• Repository guardrail scanning for AI-agent instructions, MCP config, committed local env files, risky scripts, broad workflow permissions, and API contract source-of-truth gaps.
• Text, JSON, Markdown, and SARIF reporting.
• PR-oriented review, eval, and verify commands for branch-aware findings, readiness scoring, validation evidence, and suggested domain tests.
• GitHub Action entrypoint with annotations, step summary, and PR comment output.
• Validation command discovery for JavaScript/TypeScript, Python, Go, Rust, Gradle, and Maven projects.
• E2E planning and draft generation for Playwright, Maestro, and manual checklists.
• CLI package detection that produces command verification checklists for valid arguments, failure paths, stdout/stderr, generated files, and exit codes instead of browser/device journeys.
• Bootstrap planning for projects with little or no E2E history, including required runner setup, first-draft, fixture, selector, and validation steps.
• Execution profiles, draft self-checks, readiness summaries, and action items that distinguish runnable-candidate, near-runnable, and review-only drafts.
• Domain language, domain manifest, and core-flow manifest support through .codeward/domains.yml and .codeward/flows.yml.
• Change-aware domains suggest and flows suggest commands that draft manifest entries from branch context before teams commit durable policy.
• Manifest suggestion promotion plans that classify candidates as commit-candidate, needs-review, or low-signal.
• Fixture/mock readiness and validation matrix output for generated E2E plans and drafts.
• API-dependent Playwright draft scaffolds with endpoint hints and page.route(...).fulfill(...) mock slots.
• Next.js App Router, Next Pages Router, React Router route-object, link, and navigation route inference, including dynamic route parameter placeholders or concrete route hints when available.
• codeward e2e draft --dry-run to preview planned files, readiness, action items, self-checks, and blockers without writing draft files.
• Design token and data catalog project profiles that produce artifact/catalog validation checklists instead of browser or device journeys.
• Local E2E run history snapshots protected by generated .gitignore entries.
• coverage and release:check scripts for the final local release gate.
• README and adoption guidance for repo-local verification bases, shared domain/flow manifests, and ignored generated run history.
• More conservative data-catalog and config/content E2E planning heuristics so generic package schemas or release docs do not create catalog journeys or API fixture blockers.