# Wireframe: Patch Notes

Versioned changelog, newest entry first. Wireframe follows semantic
versioning: `MAJOR.MINOR.PATCH`. While the project is pre-1.0, minor bumps
mark meaningful new content or structure (a new module, a new template, a
theme revision) and patch bumps mark fixes or small corrections within
existing content.

---

## v0.25.0, 2026-11-22

### Added
- The Template Interface Web Design Standard, version 1.0, at
  `standards/web-design/`: eight rules, the widths to check, the review
  method, print guidance, recurring bug patterns, tools and a checklist.
  It writes up the method already used in the template reviews and adds
  print as a third surface after mobile and desktop (PRD section 13.16).
- Print header and footer on every page, modelled on a printed report. Both are
  `@page` margin boxes: name and subtitle on the left, contact or version and
  date on the right, a center title naming the section on that page (from CSS
  named pages), and a footer reading "Page N of M". Added to the Web Design
  Standard (a new rule of thumb and the starting CSS block), its own printout,
  and restaurant-site, which prints in 6 pages titled Menu, The Kitchen, and
  Visit and Book.
- restaurant-site: a print stylesheet. The printout is now a take-away
  menu card: every course under its own heading, hours, address and how
  to book, ink on white, in 5 Letter pages instead of 9.
- Roadmap milestone M26: print on every page.

### Fixed
- restaurant-site printed only the open menu tab (one course of five),
  because the other courses sit in `hidden` tab panels.
- restaurant-site printed in dark mode, so with background colours off
  (the browser default) its cream text came out on white paper. It also
  printed the live "Open now" line and "Today" badge, which are wrong by
  the time anyone reads the paper.
- The design notes panel printed on every template. Its new print rule
  uses the panel's doubled-class selector (`.dn-notes.dn-notes`); a
  single-class rule was outranked and did nothing.
- The new standard's own page overflowed by 10px at 320px: an unbreakable
  inline `document.documentElement.scrollWidth`. Inline code in its lists
  may now wrap.

### Changed
- PRD section 4: print design as a discipline stays out of scope; how a
  web page prints is in scope.
- DESIGN.md section 8.6 is now Print; Documentation moves to 8.7.
- `docs/TEMPLATE_DESIGN_REVIEW_PROMPT.md`: print is a review step.
- The Color Standard page links to the Web Design Standard, and the
  sitemap lists it.

### Still open
- 14 templates have no print styles, and 43 of the other 49 have five
  lines or fewer; site pages print light text in dark mode (M26).

---

## v0.24.2, 2026-10-22

### Changed
- documentation-site template: the article column now sits against the
  sidebar instead of being centred in the space beside it.
- PRD section 31: the sharing tag rule now follows the Documentation
  prompt's default (`og:site_name` replaces `twitter:title`; description
  budget 150 to 200). Pages are not yet updated (M25).
- `docs/TODO.md`: replaced the status note with the standard template.
  The note said "Nothing pending" and held no ideas.

### Added
- PRD section 41, Page metadata: the Documentation prompt's default for
  meta descriptions and JSON-LD, recorded as policy only (Project
  Defaults pass).
- DESIGN section 17, Animation and motion, as a placeholder heading.
- Verification checklist rows for PRD 41 and DESIGN 17.
- Roadmap milestone M25: bring every page in line with the new sharing
  tag and page metadata rules.

---

## v0.24.1, 2026-10-06

- Spec files for the five hand-built M24 templates
  (`appointment-booking`, `class-studio`, `clinic-practice`,
  `subscription-box`, `two-sided-marketplace`), so all 43 rebuild from
  `tools/m24/`. The four rebuilt pages now use the generator's shared
  skeleton; their content and behaviour are unchanged.
- `gen.py`: the generated demo form is optional (`form` may be left out).
- class-studio: the "Up next today" panel no longer squeezes its
  end-of-day message into the time column.
- Script header notes no longer end in a doubled full stop.
- Disk use standard: headless browser profiles go to the system temp
  folder and are deleted on close (PRD section 29).

---

## v0.24.0, 2026-10-05

M24: template coverage by business concept.

**Added**
- 43 templates, so each of 100 business concepts has one scoring 9.0 or
  higher (PRD section 13.15): appointment-booking, clinic-practice,
  class-studio, subscription-box, stays-booking, timed-tickets,
  spaces-to-hire, news-front-page, creator-subscription, band-artist,
  app-launch, professional-firm, quote-calculator, project-gallery,
  creative-packages, order-ahead, drinks-producer, two-sided-marketplace,
  school-site, programme-catalogue, b2b-industrial, architecture-studio,
  item-rentals, vehicle-listings, supply-signup, crowdfunding-campaign,
  faith-community, political-campaign, animal-adoption, council-services,
  status-page, open-source-project, ai-tool, fintech-app, market-tracker,
  florist, bookshop, pharmacy, care-home, self-storage,
  car-wash-membership, sports-club and property-management. 64 in all.
- Each has its own palette in both modes, the site bar, a design notes
  panel, a validating demo form and a README.
- `tools/m24/`: the spec files, generator and checks used to build 38 of
  them (see its README).

**Changed**
- The registry, previews, `templates-index.js`, `templates/INDEX.md` and
  the sitemap list all 64 templates. INDEX.md region outlines now show the
  current site bar, `nav.site-nav`, instead of the old `nav.sr-bar`.
- README, PRD and `TEMPLATE_CONTRACT.md` counts say 64.

**Removed**
- `docs/reviews/m24-business-concepts.md`, the temporary scoring file;
  its results are in PRD section 13.15.

**Verified**
- Every new template: contrast in dark and light mode, no overflow at 375
  and 1280px, no console errors, and every button, select and form driven
  headless. The showcase renders 64 cards with no console errors.

---

## v0.23.0, 2026-10-05

M23: the pre-launch pass.

**Added**
- Module 08, Data Visualization: "Choosing the Right Chart" and "Color in
  Charts", each with an interactive demo and a markdown mirror.
- Module 09, E-commerce UX: "Product Pages" and "Cart and Checkout", each
  with an interactive demo and a markdown mirror.
- A light and dark switch at the right of the site bar on every page. It
  shares its stored choice with the templates' toggles.
- `assets/js/site-theme.js`, which applies a stored choice before the
  first paint on site pages.
- `tools/checks/`: the headless Edge checks (site bar, layout sweep, Web
  Safe Colors lesson, Color Standard page) with one runner,
  `run_all.py`, which also runs the color audit.
- `tools/build-new-lessons.py`, which generates the four new lessons.
- PRD section 13.15 and milestone M24 (template coverage by business
  concept), planned after M23.

**Changed**
- Registries, sitemap, search index (29 pages) and three template READMEs
  cover the new lessons; 19 concepts in 9 modules.
- `tools/color-standard/audit.py` uses the shared `tools/checks/cdp.py`.
- Documentation audit rerun (PRD section 40): stale theme, module and
  test suite notes fixed; four concept definitions added to PRD 12.2;
  DESIGN section 16.

**Verified**
- All five checks pass: site bar on 54 pages at 1280 and 375px, no
  overflow or console errors in either mode, both lesson checks and the
  color audit. The new lessons and the switch screenshotted in both
  modes.

---

## v0.22.0, 2026-10-05

M22: the whole site, all 21 templates included, follows the Template
Interface Color Standard in dark and light mode.

**Added**
- Light mode for every site page, following the visitor's setting.
- Site tokens `--color-border-strong`, `--color-on-accent`, `--color-info`,
  `--color-focus`, `--color-scrim`, `--color-shadow`, `--color-bar`.
- A "Color roles" list in every template README's Composition section.

**Changed**
- `assets/css/theme.css` imports `standards/color/tokens.css` and defines
  every site color from a standard role; the six raw colors left in site
  CSS are now tokens. Teal stays `#00d4a0` in dark; teal 60 in light.
- Inputs, selects, search fields, chips and menu buttons on site pages use
  the strong border (3:1 or more).
- The site bar and design notes panel keep the site accent on every
  template (the wiki portal used to recolor them).
- Input, select and search outlines in 16 templates use each template's
  muted text token.
- Pricing page: over-limit prices are no longer dimmed with opacity.
- Wiki portal: the masthead band turns light in light mode.
- Visual Hierarchy lesson: the demo label changes weight, not opacity.
- Accessibility lesson: the photo placeholder has a readable background.
- The template contract and DESIGN.md describe the finished state.

**Verified**
- `tools/color-standard/audit.py`: baseline 12,580 checks with 69
  failing rows, after 12,146 checks with five, all accepted (three
  deliberate failing samples, two boundaries on gradients checked by
  screenshot). Report: `docs/reviews/color-standard-audit.md`.
- Screenshots in both modes of the home, Education, Templates, Color
  Standard and Forms pages, and of the help center, event site,
  onboarding, real estate, wiki portal and landing page templates. One
  defect found that way and fixed (the wiki masthead).
- The site bar check passes on every site page; no page overflows.
- One final review of every edit before these notes; it removed a stray
  Python cache file from the repository.

---

## v0.21.2, 2026-10-04

M22 started; paused after checkpoint 1 at the maintainer's request.

**Added**
- `docs/reviews/m22-checkpoints.md`: the seven M22 checkpoints.
- `tools/color-standard/audit.py`: measures text contrast and control
  boundaries on every page in dark and light mode.
- `docs/reviews/color-standard-audit.md`: the baseline, 12,580 checks.

**Changed**
- Go live (M20) deferred by the maintainer; it is the stopping point.
- PRD section 13.13 and the milestone table record M22's progress and
  the next steps; README row updated.

---

## v0.21.1, 2026-10-04

Documentation: the whole site, templates included, follows the Template
Interface Color Standard. No page changes yet; the work is milestone M22.

**Changed**
- PRD: Tenet 7, "The site follows its own Color Standard"; section 13.13
  defines what following it means (rules, role-based colors, both modes,
  fitted brand colors, status colors for status only), the scope, the
  measured gaps on site pages, the method and acceptance criteria; M22
  added to the milestone table and proposed before M20 in the order.
- DESIGN.md: section 2.1 and 6.2 point to the standard; new section 15
  maps every site token to a standard role.
- Template contract: a new Color section (role map for every prefixed
  token, both modes pass, fitted brand colors), and the Composition
  section now carries the role map.
- Template design review prompt: color and contrast checks now name the
  standard and both modes.
- README: M22 listed as next.

**Measured for the record**
- Site border token `#30363d`: 1.55:1 on the canvas, 1.42:1 on the
  surface, below 3:1 where it outlines controls. Other site text and
  status tokens pass on both dark backgrounds.

---

## v0.21.0, 2026-10-04

The Template Interface Color Standard, version 1.0: a standard for
everyone to follow, built with the maintainer, starting from GitHub and
Google Chrome.

**Added**
- `standards/color/index.html`, a new Standards section in the site
  bar. Six rules from WCAG 2.2; a grade system where the gap between two
  grades guarantees the contrast (40: 3:1, 50: 4.5:1, 70: 7:1); a ten
  hue palette at eleven grades; fifteen light and dark roles with live
  specimens; all 42 required pairings measured; a comparison with GitHub
  Primer 11.10.0 and Chrome's default theme from the Chromium source; a
  brand color fitter; usage, a checklist, sources and version.
- `tokens.css` and `tokens.json` downloads, and `tools/color-standard/`
  to rebuild everything.
- Links to the standard from the Color and Contrast and Web Safe Colors
  lessons, and the sitemap.

**Sources**
- GitHub: `@primer/primitives` 11.10.0 functional light and dark
  themes, fetched from jsDelivr.
- Chrome: `ui/color/ref_color_mixer.cc` and `sys_color_mixer.cc` from the
  Chromium repository, default (not themed) values.

**Verified**
- The build asserts the grade guarantees over every pair of the 112
  colors (worst: 3.35:1 at 40, 4.54:1 at 50, 8.37:1 at 70) and all 42
  role pairings.
- Headless Edge at 1440, 1024 and 375px: no overflow, no console errors,
  110 swatches, Standards marked in the bar, the pair tool, copying and
  the brand tool (a fitted color passes in both modes; #FFCC00 as entered
  fails on light). One defect found and fixed: brand card headings were
  invisible on the light cards. Screenshots of every section looked at.
- The site bar check on all 48 pages still passes.

---

## v0.20.0, 2026-10-04

A new Education lesson, Web Safe Colors, at the maintainer's request:
the 216 color chart from htmlcolorcodes.com rebuilt as this site's own
content page.

**Added**
- `education/03-typography-and-color/web-safe-colors.html`, the third
  lesson in Module 03, in the standard lesson structure. It explains
  where the palette came from, how its codes are built, short hex,
  grays, and why safe is not the same as readable.
- The interactive chart: all 216 colors as swatches in six panels, one
  per red level. Selecting one shows its hex, short hex, RGB and its
  contrast on white and on the site background, with a copy button. The
  chart is one tab stop: arrow keys move, Page Up and Down change panel,
  Home and End jump to the ends. A color input snaps any color to its
  nearest web safe color.
- Its markdown mirror, with every code in six tables.
- Entries in `nav-data.js`, `concepts-index.js`, `education/INDEX.md`,
  the module page, the search index, the sitemap and PRD section 12.
- `WireframeDemo.hexToRgb` is now exported from `demo-utils.js`.

**Verified**
- The 216 codes fetched from the source page match the definition (six
  steps per channel) exactly before the page is generated.
- In headless Edge at 1280 and 375px: 216 distinct swatches at least
  24px wide, no overflow, no console errors; clicking, the arrow, Page
  and End keys, the single tab stop and the snap tool all behave. The
  lesson shows in the rail and the module page; the showcase still loads
  without errors (no template lists the lesson, so it adds no filter).
- The site bar check on all 47 pages still passes.

---

## v0.19.1, 2026-10-04

**Changed**
- The site bar is aligned left: the brand and the Home, Education and
  Templates links sit together in one row starting at the page's left
  edge (16px gutter), instead of the brand left and the links right in
  a centred 1200px row. On phones the menu button stays at the right.

**Verified**
- All 46 pages at 1280 and 375px in headless Edge: same checks as
  v0.19.0, no failures.

---

## v0.19.0, 2026-10-04

One main navigation bar on every page, after azqato.github.io, at the
maintainer's request.

**Added**
- `assets/css/site-nav.css` and `assets/js/site-nav.js`: the site bar.
  Brand on the left; Home, Education and Templates on the right, with
  the current section in teal; a menu button under 640px. Sticky and
  blurred on site pages, scrolling away on template pages.
- `tools/build-site-nav.py` stamps the bar into all 46 pages; re-running
  changes nothing.

**Changed**
- The root page's and the showcase's own headers, the template return
  bar ("Back to Template Interface", "All templates") and the site name
  at the top of the Education rail are replaced by the bar.
  `site-return.css` and the old header styles are removed.
- The Education rail, top bar, "On this page" column, Menu button and
  heading anchors, and the showcase filters, now sit below the bar.
- PRD 13.11, DESIGN 13.2, the template contract, `templates/INDEX.md`,
  every template README and the template index data name the new bar.

**Verified**
- All 46 pages in headless Edge at 1280 and 375px: the bar is present,
  at the top, at most 60px high, marks the right section, loads its
  image, shows the menu button only on phones; no horizontal overflow
  and no console errors. The menu opens, reports `aria-expanded`, and
  closes on Escape with focus back on the button. Screenshots of the
  root, the showcase, a lesson (top and scrolled), wiki-portal and a
  template looked at.

---

## v0.18.0, 2026-10-04

The Brand Identity prompt (prompts v1.110.0) run on this site: the M21
test. Nothing outside `brand/`, the Brand Identity sections and the two
rule notes below changed; the site pages are untouched.

**Added**
- `brand/concepts/`: five concept directions (A to E), E in five GitHub
  Primer accents, and `index.html` to compare them on one page. The
  maintainer chose E (the layout T with the original favicon's
  landscape) in Primer Accent blue.
- `brand/logo/`: 30 files. Lockups, symbol and wordmark in colour,
  reversed, black and white; a single-colour print mark; `favicon.svg`
  with a dark-mode version, `favicon.ico` and PNGs; app icons and
  maskable icons.
- `brand/kit/`: link preview, profile, X and LinkedIn images, email
  signature, `tokens.css`, `tokens.json`, `site.webmanifest`.
- `brand/presentation.html` with six CSS mockups, and
  `brand/brand-guidelines.pdf` (7 pages).
- `brand/index.html`: a 14-slide overview deck with a report view.
- `brand/brand-design.html`: the offline Brand Design page, listed in
  `.gitignore` and not committed.
- PRD and DESIGN `## Brand Identity` sections: brief, competitive
  analysis, concepts, logo system, kit, contrast table, rationale,
  usage guidelines, overview and deliverables checklist.

**Changed**
- The raster rule (PRD section 9) gains a second exception: files
  inside `brand/`. `.gitignore` gains the Brand Design page.

**Verified**
- Every concept and logo file rendered in headless Edge at 16, 32 and
  512px, in grayscale, on light and dark; fixes made for a vanishing
  dark tile and hairline gaps.
- All 12 brand colour pairs pass WCAG AA (lowest 4.62:1).
- The deck: 131 scripted checks pass at 1920x1080, 1280x720 and 375px
  (overflow, title length, images, contrast, keys, hash, Back, view
  switch and memory, 14-page print). One contrast bug, the "Chosen"
  badge, was found and fixed.
- The presentation: no overflow or console errors at 1440px; the PDF
  breaks into one page per section, with the mockups over two.
- The Brand Design page: four sections, 95 tiles, every image loads,
  dark tiles for white files, a download link on each, no horizontal
  scroll at 375px, ignored by git.

**Found in the prompt**
- Phase 3 asks for a pick but builds no page to compare the concepts
  on; `brand/concepts/index.html` was made by hand. The prompt now adds
  it (prompts v1.111.0).

---

## v0.17.0, 2026-10-04

The site interface redesign (M15), and the Brand Identity prompt update
(M21) made in the prompts project.

**Added**
- Template previews drawn in CSS in each template's own colours, type and
  shapes: `assets/js/template-previews.js` and `assets/css/previews.css`.
- Showcase filters by page type and by lesson, with live counts; search;
  sort; a quick view dialog for each template.
- A new root page: a split hero with a mosaic of six template previews,
  figures counted from the data files, "how it works" tabs and the module
  list (`assets/css/home.css`).
- Education: a top bar with breadcrumbs and search (`/` or Ctrl+K), an
  "On this page" list that marks the section being read, and previous and
  next links. The search index is `assets/js/search-index.js`, generated
  by the new `tools/build-search-index.py`.
- Theme tokens `--color-surface-raised` and `--color-tag-bg`.
- DESIGN.md section 14: the specs for all of the above and the accent
  rule.

**Changed**
- Teal now marks only actions, the current location and focus. Tags,
  eyebrows and difficulty badges are neutral.
- The Education menu button reports `aria-expanded`, Escape closes the
  menu, and the rail has an Overview link and marks the current page.
- Two lesson demo colours fixed for contrast where low contrast was not
  the point: the critique demo's flag button text and the accessibility
  demo's "Product photo" placeholder.
- M21: the Brand Identity prompt (prompts v1.110.0) gains Phase 8, a
  committed `brand/index.html` overview deck in 16:9 slides with a
  scrolling report view, linking to `presentation.html`.

**Verified**
- Headless Edge, 17 site pages at eight widths: no horizontal overflow,
  no console errors.
- All 21 templates and `article.html` at 375 and 1440px: no overflow, no
  errors, return bar present (the shared stylesheets gained only new
  tokens).
- About a hundred driven checks with real key and mouse events: filters
  and counts, search, sort, quick view focus in and out, tabs, the
  search dialog's keys, contents marking on scroll, pager order, the
  mobile menu.
- Contrast: 0 failures apart from two lesson demos that are low contrast
  on purpose ("Ceramic mug" at 2.15:1, "Our services" at 3.08:1).

**Not yet done**
- The M21 test run of the Brand Identity prompt on this site. M20 (going
  live) follows it.

---

## v0.16.1, 2026-10-04

The maintainer's answers to the audit's six questions.

**Added**
- Six sharing tags (`og:title`, `og:description`, `og:url`, `og:type`,
  `twitter:card`, `twitter:title`) on all 46 HTML pages.
- `.gitattributes`: text is stored with LF line endings.

**Changed**
- Shorter titles: `blog-article` is "Field Notes - Template Interface
  template" and `event-site` is "Signal Conference 2026 - Template
  Interface template", both under 60 characters.
- D6 decided: `wiki-portal` keeps its skip link, and the review brief
  allows it there.
- Chrome stays the target browser and checks run in Edge (PRD section
  25). The stale offline wording is rewritten as part of M20, right
  before release.
- `docs/TODO.md` emptied: both of its items are on the roadmap.

**Verified**
- A script check of all 46 pages: six tags each, absolute `og:url`,
  descriptions of 155 characters or fewer, titles of 60 or fewer with
  unique first 30 characters.

---

## v0.16.0, 2026-10-04

The documentation audit (M19), run from the Documentation Prompt. No
page, template or script changed.

**Added**
- `LICENSE.md` (all rights reserved), `robots.txt` (open on purpose,
  pointing at the sitemap) and `sitemap.xml` (the public pages at
  `https://templateinterface.com/`, not yet live).
- PRD sections 23 to 40: repository reference, conventions, browser
  testing, verification environment, testing cadence, a security
  addendum, repository hygiene, licensing, the social tags and page
  title policies, deprecation, metrics and runbook notes, documentation
  versus reality, risks and open questions, technical debt, working
  practice and the audit record. Section 14 gains a verification
  checklist and a Future updates heading.
- DESIGN.md section 13: the theme toggle and return bar specs.

**Changed**
- The README is written for a general reader: what the site offers, who
  it is for, that it is not live yet, and its status. The live site, tech
  stack, prerequisites, installation, running locally, environment
  variables, build and deploy, and directory tree sections, and the
  version line, moved to PRD section 23 unchanged.
- Testing cadence (PRD section 27): one browser test before a major
  update ships. It replaces section 21's responsive QA trigger, which
  read: "after any layout-affecting change".
- Stale PRD lines (five templates, no technical debt, "DESIGN.md section
  20", "exactly four markdown documents") are kept and marked as
  discrepancies.

**Fixed**
- DESIGN.md section 3 showed `--color-text-tertiary: #6e7681`; it now
  matches `theme.css` and section 2.1: `#7c8487`.

**Still open**
- PRD section 37's questions, D6, M15, M21 and M20.

---

## v0.15.1, 2026-10-04

Roadmap reordered for the work left after v0.15.0.

**Changed**
- `docs/TODO.md`'s two items join the roadmap as M19 (documentation
  audit) and M21 (Brand Identity prompt page), with M20 for going live.
- PRD section 14 has a new "Recommended order of the remaining work":
  M19, then the D6 decision, then M15, then M21, then M20, with the
  reason for each position. The README status table follows it.

---

## v0.15.0, 2026-10-02

Dark and light mode on every template (M18), design notes on every template
(M17), and the going-live wording (M16).

**Changed**
- Checkpoint 1: `blog-article` (both pages), `waitlist-signup`,
  `resume-site`, `ecommerce-product`, `careers-page`,
  `documentation-site`, `help-center` and `onboarding-flow` have the sun
  or moon toggle and open dark. Each keeps its brand: the dark palette
  is the same hues on a dark ground, and the light mode is the original
  palette, unchanged.
  - Wherever a template used its ink colour as a background (subscribe
    bands, code blocks, footers, quote and apply bands, the resume's
    tool bar), that use now has its own role token (`--xx-night`,
    `--xx-on-night`). It stays dark in both modes.
  - Buttons and badges with white text keep their original fill in both
    modes (`--xx-*-fill`), so the text stays readable.
  - Hard-coded whites (inputs, cards, the docs search, kbd, sticky
    headers, hero glows) became tokens with a dark value.
  - Each README, `templates/INDEX.md` and `templates-index.js` record
    the toggle script.
- Checkpoint 2: `community-forum`, `course-landing`,
  `ecommerce-storefront` and `landing-page` have the toggle.
  - Course-landing's dark mode prints the black, paper and yellow poster
    in reverse: paper-coloured rules, type and offset shadows on black,
    with the yellow unchanged.
  - Accent colours used as text now have their own `--xx-*-text` tokens,
    which lighten in dark mode. Buttons and badges keep the brand fill.
    Dark text on yellow, peach, amber and wheat fills uses
    `--xx-on-fill`, so it stays dark.
- Checkpoint 3: `nonprofit-site`, `portfolio-site`,
  `real-estate-listing` and `small-business` have the toggle. Each keeps
  its own accent for its main action: Wellspring's ochre Donate,
  Larkfield's brass, Brookes and Daughter's copper booking button and
  the portfolio's pistachio.
- Checkpoint 4: `admin-dashboard`, `event-site`, `pricing-page` and
  `wiki-portal` were already dark by design. Each gains a designed light
  palette under `:root[data-theme="light"]` and still opens dark.
  - In light mode, signal colours used as text are deepened (amber,
    lime, orange, magenta and status colours) so they read on pale
    grounds. Lime, amber and gradient fills keep their colour, with the
    same dark text on them.
  - Wiki-portal's hard-coded white and translucent-white text became
    tokens, so its light mode has dark violet text.
  - Their print comments now say print keeps the template's own palette.
- M18 is complete: PRD section 13.10, the roadmap table, README,
  `TEMPLATE_CONTRACT.md` and `templates/INDEX.md` say all 21 templates
  have the toggle.
- Design notes on every template (M17). The other sixteen templates get
  the "How this template was designed" panel. Each has its own brief,
  five design-process steps, four reasons it suits the use case, links to
  its lessons, and a closed "Recreate it with Claude Code" prompt with a
  copy button.
  - Every prompt links the live template, starts with the
    branding-preservation rule, and describes the page section by
    section.
  - All 21 prompts, the five pilots included, now ask for the sun or
    moon dark and light toggle, derived from the target site's
    branding and dark by default (PRD section 13.10).
  - Each README (shared dependencies, region outline, and how to remove
    the panel), `templates-index.js`, `templates/INDEX.md`, PRD section
    13.9, the roadmap and `TEMPLATE_CONTRACT.md` record it. The
    "being rolled out" notes are gone.
- Going-live wording (M16). The project now describes itself as a free
  public site at `templateinterface.com` instead of an offline tool.
  - The root page has the agreed `<meta name="description">`, and its
    hero no longer says "fully offline" or "the files on this disk".
  - The README opening, PRD section 4's non-goal, the goals, the
    maintainer story, section 15, the FAQ and section 22 are reworded.
    Every page still works opened from disk under `file://`.
  - PRD section 13.8, the roadmap and the README mark M16 done.
    Choosing a host and deploying are the maintainer's steps.

**Fixed** (found by the verification pass below)
- `community-forum`: dark mode no longer darkens the cream text on plum
  buttons, flags, the active category and the footer brand.
- `course-landing`: text on the yellow open week, chosen plan, timetable
  row headers and open FAQ stays dark in dark mode.
- `ecommerce-storefront`: the hero lede and specs have a dark-mode
  `--np-ink-2`; the Subscribe button, Sale badge and bag count use dark
  text on orange.
- `admin-dashboard` and `pricing-page`: in light mode, table cells no
  longer take the lesson site's grey from the shared table styles.
- `wiki-portal`: in light mode, the social promo keeps its light text
  and plain links use the template's violet.
- `documentation-site`: the toggle stays in the bar on small screens,
  where the status, version and keys button are hidden.
- `help-center`: the system status hides below 860px so the header fits
  at 768px, and on phones the toggle sits beside the brand.
- `real-estate-listing`: between 761 and 1000px the Saved button shows
  heart and count only (the word stays for screen readers), so the
  header fits.

**Verified**
- Headless Edge, all 21 templates and `blog-article/article.html`, in
  both modes: dark by default, a real click switches to light and the
  choice survives a reload, no console errors, no horizontal overflow at
  320, 375, 768 and 1440px, and every text pairing at 375 and 1440px
  meets WCAG AA. The toggle is reachable at every width; the admin,
  resume and wiki headers already stack on phones by design.
- The design notes panel renders on every template with its copy button
  and lesson links, and the root page has the new description and hero.

---

## v0.14.0, 2026-10-01

The project is renamed Template Interface, and every template page links
back to the main site.

**Changed**
- Renamed from Wireframe to Template Interface everywhere a reader sees
  it: every page `<title>`, the root wordmark, the Education sidebar
  title, visible copy in the lessons, and the docs (M16, PRD section
  13.8). The `WIREFRAME_*`, `WireframeMotion` and `WireframeDemo` script
  identifiers, the folder name, dated history (these patch notes, the
  review findings, section 13.8's account of the rename) are kept.
- The root page's header lets its nav wrap below the wordmark at narrow
  widths; at 320px the longer name had wrapped onto two lines.
- New return bar at the top of all 22 template pages: "Back to Template
  Interface" and "All templates", from a shared
  `assets/css/site-return.css` (PRD section 13.11). Recorded in every
  README's region outline and Recreating section (remove it when
  copying), `templates/INDEX.md`, `templates-index.js` and
  `TEMPLATE_CONTRACT.md`.

**Verified**
- Headless Edge, all 22 template pages at 320, 375 and 1440px: the bar
  is at the top and visible, both links resolve, its text is at 4.5:1 or
  better, no horizontal overflow, no console errors. Header screenshots
  checked by eye.
- The root page, the showcase and all 22 Education pages at 320 and
  1440px: no overflow, no console errors, no title still saying
  Wireframe, and the wordmark on one line.

**Still open**
- M16's going-live wording (the site still describes itself as offline)
  and the meta description, once the domain is live.
- M18 on the remaining 20 templates (in progress), M17's remaining 16,
  M15, D6.

---

## v0.13.4, 2026-10-01

Dark and light mode, first template (milestone M18).

**Changed**
- New shared script `assets/js/theme-toggle.js`. It sets
  `data-theme` on `<html>` before the first paint, defaults to dark,
  remembers the choice under `template-theme` across all templates
  (falling back to dark when storage is blocked), and keeps every
  `.theme-toggle` button's emoji and label in step.
- `restaurant-site` has the toggle: a round button at the right of the
  header showing a sun while dark and a moon while light, with
  "Switch to light mode" or "Switch to dark mode" as its accessible
  name. It opens dark. The dark palette keeps Amaro's bottle green,
  cream and tomato: the paper and cream sections become deep green-black,
  ink becomes cream, tomato text lightens. Form fields, the open and
  closed badges, section surfaces and the select arrow became role
  tokens so both modes can set them; text on red and green fills has
  its own token that stays light. The light mode is the original
  palette, unchanged.
- Below 420px the header's "Book a table" reads "Book" (the rest is
  kept for screen readers) so the header stays one row with the new
  button.
- PRD section 13.10 records the pilot's pattern and drops
  `aria-pressed` from the spec: a toggle whose label changes must not
  also report a pressed state. README, `templates/INDEX.md`,
  `templates-index.js`, `TEMPLATE_CONTRACT.md` and the template's
  README record the new script.

**Verified**
- Headless Edge with a fresh profile: opens dark with a sun and
  "Switch to light mode"; a real click switches to light, a moon and
  "Switch to dark mode", and the choice survives a reload. In both
  modes: no console errors; no horizontal overflow at 320, 375, 768 and
  1440px; the header on one row at all four; every text pairing on
  plain backgrounds at AA at 375 and 1440px; the button shows the gold
  focus ring. Full-page screenshots of both modes checked by eye
  (text over gradients is outside the automated check).

**Still open**
- M18 on the other 20 templates. M17's remaining 16, M16, M15, D6.

---

## v0.13.3, 2026-10-01

Planning only. No page, template or script changed.

**Changed**
- Roadmap milestone M18 added: a dark and light mode toggle on every
  template, a single button showing a sun emoji while dark and a moon
  emoji while light, with every template opening in dark mode. PRD
  section 13.10 holds the brief: the button, how the mode is set and
  remembered without a flash, the dark palette each template needs
  (its current palette becomes light mode), the effect on M17's
  prompts, the rollout and the acceptance criteria. PRD section 14 and
  the README status table list it.

**Still open**
- M18, M17's remaining sixteen templates, M16, M15 and D6.

---

## v0.13.2, 2026-09-27

**Changed**
- Each pilot template's Claude Code prompt now links the template's live
  address (`https://templateinterface.com/templates/<id>/`) and tells
  Claude Code to open it and read it through in detail before writing
  code: the rendered page and its `index.html`, `styles.css` and
  `script.js`, analysing section order, grid, breakpoints, components,
  spacing, type, states and behaviour, and summarising what it found.
  The live page is the source of truth for layout, never for branding.
  PRD section 13.9 and `TEMPLATE_CONTRACT.md` add this to the prompt's
  required parts.
- Copy prompt moved to the right of the "Recreate it with Claude Code"
  header and shows while the prompt is closed, so the prompt can be
  copied without opening it. The button reads "Copied" after a copy. If
  the browser blocks copying, the prompt opens and is selected, ready
  for Ctrl+C. DESIGN.md section 4.11, PRD section 13.9 and
  `TEMPLATE_CONTRACT.md` updated.

**Still open**
- The address does not resolve yet: the domain goes live with M16, and
  the GitHub repository is private. Until then the prompt tells Claude
  Code to say the link failed and work from the written description.

---

## v0.13.1, 2026-09-27

**Changed**
- The "Recreate it with Claude Code" prompt moved to the top of the
  design notes panel, above the "Design notes" label, on the five pilot
  templates, at the maintainer's request. It is still closed by default.
  PRD section 13.9, DESIGN.md section 4.11 and `TEMPLATE_CONTRACT.md`
  give the new order, so the remaining sixteen templates get it too.

**Verified**
- Headless Edge on all five: no console errors, no overflow at 320 and
  375px, panel contrast at 4.5:1 or better, prompt closed on load, and
  Copy prompt reports success on a real click.

---

## v0.13.0, 2026-09-27

Design notes on templates, piloted on five of the 21 (milestone M17).

**Changed**
- `admin-dashboard`, `landing-page`, `nonprofit-site`, `portfolio-site`
  and `restaurant-site` end with a "How this template was designed"
  panel after their footer: the brief, the design process in numbered
  steps, why the result suits the use case, links to the lessons it puts
  into practice, and a "Recreate it with Claude Code" prompt, closed by
  default, with a Copy prompt button. The invented businesses above the
  panel are unchanged.
- Every prompt starts with a branding rule: the template supplies layout
  and interface only, and a site's existing colours, logo, typefaces,
  imagery and voice are kept and mapped onto the layout's roles, with
  the template's palette used only when a site has no branding.
- New shared files `assets/css/design-notes.css` and
  `assets/js/design-notes.js`, so each template still has five files.
  The panel uses only `theme.css` tokens and doubled-class selectors, so
  no template's rules reach it.
- PRD section 13.9 specifies the feature and makes its design philosophy
  a standing rule for every future template; section 14 adds M17, and
  section 13.6 notes the panel. DESIGN.md adds the component spec as
  section 4.11. `TEMPLATE_CONTRACT.md`, `templates/INDEX.md`,
  `templates-index.js` and the five READMEs record the panel, its files
  and its region, and each README says to delete it when copying.

**Verified**
- Headless Edge on all five pilot pages: no console errors; no
  horizontal overflow at 320, 375, 768 and 1440px; the prompt closed on
  load; every text pairing in the panel at 4.5:1 or better, open and
  closed; a real mouse click on Copy prompt reports "Prompt copied".
  Screenshots at 1440 and 375px checked by eye.

**Fixed**
- During the pilot: the Copy button's white text on the light accent
  measured 1.61:1 and now uses the canvas colour; `restaurant-site`'s
  list reset removed the panel's bullets, so the panel sets its own list
  style; the Clipboard API can wait forever on an unfocused page, so the
  copy tries `execCommand` first and gives the API a 1.5s timeout.

**Still open**
- The other 16 templates, rolled out gradually, a few per session, in
  the order PRD section 13.9 lists. None of the prompts has yet been run
  in Claude Code against a real branded site.
- M16, M15 and D6 as before.

---

## v0.12.3, 2026-09-27

Planning only. No page, template or script changed.

**Changed**
- Roadmap milestone M16 added: renaming the project from Wireframe to
  Template Interface (`templateinterface.com`), agreed with the
  maintainer after `wireframe.com` turned out to be taken. It runs
  before M15, so the redesign is built on the final name, and starts once
  the domain is registered. PRD.md section 13.8 holds the brief: what
  changes (every visible use of the name, the docs, template text), what
  deliberately stays (the `WIREFRAME_*` script identifiers, dated
  history, the local folder name), and the acceptance criteria. PRD
  section 14 lists it in the milestone table and feature breakdown, and
  the README status table shows it as next, with M15 after it.
- M16 also covers going live. The project moves from an offline tool to
  a public site at the new domain, so the same pass rewrites its offline
  and not-hosted wording (two places in `index.html`, two in the README,
  eighteen in the PRD), reverses PRD section 4's "not a hosted product"
  non-goal, and adds a `<meta name="description">` with the agreed
  description. The code needs no change to be hosted, and still works
  from disk. Choosing a host and deploying stay with the maintainer.

**Verified**
- The scope figures in section 13.8 come from a case-insensitive search
  on 2026-09-27: 268 uses in 75 files (125 in 28 HTML files, 34 in 32 JS
  files, 109 in 15 Markdown files, none in CSS), and the list of script
  identifiers that carry the old name.

**Still open**
- M16 and M15. D6 from v0.12.0.

---

## v0.12.2, 2026-09-23

An audit of the text in this project that is written for a model to read
and act on, checked against how current Claude models follow
instructions (closely and literally, so a stale fact or a pushy line gets
applied as written). The main finding was stale facts, not tone: nothing
in scope used all-caps commands or "think step by step" scaffolding. No
template or page changed.

**Fixed**
- `docs/TEMPLATE_DESIGN_REVIEW_PROMPT.md` no longer says several templates
  share a near-black background with a teal accent; that stopped being
  true in v0.12.0, and a new run would have gone looking for it.
- The same prompt no longer says the skip link was removed from every
  template. `wiki-portal` still has one; the prompt now says so and says
  to leave it for decision D6.
- DESIGN.md section 9 and the opening of section 3 no longer forbid raw
  hex outside `theme.css`. Both now say the site's own pages read from
  `theme.css` and templates declare their own prefixed palette tokens,
  which section 3 already allowed and all 20 rebuilt templates do.
- DESIGN.md section 9 no longer calls the dark theme provisional; it
  points to the maintainer's decision in PRD section 13.7.
- The review prompt's reading list now names PRD section 18 by its real
  title (Security), which is where the demo-notice rule lives.

**Changed**
- The review prompt names the default styles to avoid: a cream or warm
  off-white page background, italic accent words in headlines, numbered
  "01 / 02 / 03" section labels, monospace eyebrow labels, and pill-shaped
  buttons as the house shape. The previous run put 10 of 21 templates on
  a warm cream or off-white ground and used numbered labels in four; a
  general "treat sameness as a finding" had not prevented that.
- The review prompt's working method states the need (append each
  template's findings as soon as it is done, so a resumed session can
  pick up from the file) instead of a fixed batch size and a status-line
  routine, and "Do not stop at the first few" became a plain statement
  that the review covers all 21.
- DESIGN.md section 9's "not optional ... proactively" wording became a
  plain statement that section 8 is the acceptance bar, checked in a
  rendered browser before a change is called done.

**Verified**
- Every claim the edits correct was checked against the files: the
  template backgrounds and accents, the skip link in `wiki-portal`, the
  raw hex tokens in the templates, and the PRD section 18 heading.
- Each edit replaced exactly one occurrence of its original text.

**Still open**
- None of the prompt edits has been tested by running the review prompt
  again; this project has no evaluation to run them against. The named
  defaults list is the one worth checking first.
- DESIGN.md section 3's theme block shows `--color-text-tertiary` as
  `#6e7681`, while `theme.css` and the section 2.1 table both say
  `#7c8487`. Outside this audit's scope; not changed.
- DESIGN.md's opening paragraph still says the theme revision is
  expected; it happened in M8. Left as history.

---

## v0.12.1, 2026-09-22

Planning, plus one stale figure. No template changed.

**Fixed**
- The root page said "14 concepts across 7 modules · 5 starter
  templates". There are 21 templates; it now says so. The count is still
  typed by hand; M15 derives it from the registry so it cannot go stale
  again.
- `templates/INDEX.md` and the README no longer call the templates'
  content placeholder, and DESIGN.md no longer claims every template
  carries the page-wide `[hidden]` guard (13 do; 8 guard each hidden
  element instead). These corrections were made after v0.12.0 was
  written and are also noted there.

**Changed**
- Roadmap milestone M15 added: a site interface redesign, agreed with
  the maintainer. The site stays dark. The showcase takes its interface
  from `ecommerce-storefront`, the root page from `landing-page`, and
  Education from `documentation-site`; teal is kept for actions, the
  current location and focus, and tags turn neutral. PRD.md section 13.7
  holds the brief, order, risk and acceptance criteria; PRD section 14
  lists it in the milestone table and feature breakdown; section 22's
  stale note about a pending theme change now points to it. DESIGN.md
  gains a short section 12 pointing there, and the README status table
  gains a Next row.

**Verified**
- The four problems M15 addresses were seen in full-page screenshots at
  1440px: the root page and the showcase captured after scrolling
  through, so content that reveals on scroll was shown; the Education
  overview and a concept page captured without scrolling, which shows
  their layout but leaves the concept page's demo blank. Only 1440px was
  captured for this.
- Every template's stylesheet was searched for site colour tokens:
  only `wiki-portal` uses them (three uses), which is the basis for the
  risk note in section 13.7.

**Still open**
- M15 itself. D6 from v0.12.0.

---

## v0.12.0, 2026-09-22

The template design review, run against
`docs/TEMPLATE_DESIGN_REVIEW_PROMPT.md`. Before it, 20 of the 21
templates were clean one-screen sketches of their page type, sharing the
site's dark canvas and teal accent. Each is now a complete, working site
for an invented brand with its own palette, type and shape, built inside
the existing contract: same folder, same five files, same id, same
concepts claim. `wiki-portal`, already full depth, was fixed in place.
The per-template evidence, scores, findings and decisions are in
`docs/reviews/template-design-review-findings.md`.

**Fixed**
- `waitlist-signup`: Loamwork, a garden planning app. Sage paper, moss
  and marigold, a serif display.
- `blog-article`: Field Notes, an engineering journal. A filterable essay
  listing and a long-form article with contents, figures and code.
- `event-site`: Signal Conference. A tabbed two-day schedule, speakers,
  venue, ticket tiers and registration, on a night-indigo poster look.
- `onboarding-flow`: Ledgerline bookkeeping. Four steps with per-step
  validation, a live workspace preview and a done screen.
- `pricing-page`: Tallyhall analytics. A per-person price calculator,
  three plans, a comparison table with a sticky feature column, and a
  trial signup.
- `ecommerce-product`: Kiln and Co ceramics. A recolouring gallery,
  glaze and size options, a cart drawer and reviews.
- `careers-page`: Tessellate. Values, benefits, the hiring process,
  filterable roles that open in place, and an application form.
- `help-center`: Brightdesk support. Live article search, topics, an
  article reader with feedback, quick answers and a contact form.
- `admin-dashboard`: Relaywise delivery operations. Range-switched KPIs,
  a chart, a sortable, filterable table with bulk actions, and alert
  settings.
- `community-forum`: The Proofing Room. Filters, a threaded reader with
  likes and replies, a compose dialog and a bake-along card.
- `course-landing`: Fieldwork School. Places, an accordion syllabus,
  projects, tutors, a price card that follows the plan, and an
  application form.
- `ecommerce-storefront`: Northpass Supply. Sixteen packs with live
  filter counts, chips, search, sort, quick view and a bag drawer.
- `real-estate-listing`: Larkfield and Co. Fourteen drawn homes with
  live filters and a synced map, a detail dialog with a mortgage
  calculator and viewing slots, and a valuation form.
- `resume-site`: Alex Rivera. A print-first CV with skill chips that
  mark matching achievements, a short version and a clean print sheet.
- `nonprofit-site`: Wellspring water charity. An appeal with progress,
  where every pound goes, and a donation form with impact lines and Gift
  Aid.
- `restaurant-site`: Amaro trattoria. Open-now status, a filterable
  tabbed menu, hours, a drawn map and a booking form with live slots.
- `landing-page`: Northline release planning. A sign-up hero beside a
  pausable animated product board, tabs, count-up figures, a pricing
  toggle and a closing sign-up.
- `portfolio-site`: Jordan Ames, product designer. Filterable projects
  on an alternating grid, case studies in a dialog, principles, about,
  quotes and a contact form.
- `small-business`: Brookes and Daughter, plumbers. Live office status
  and next free visit, stated prices, a postcode checker and a booking
  form that offers real day and time windows and sends leaks to the
  phone. It no longer loads `motion-utils.js`.
- `documentation-site`: Parcelpoint shipping API. Seven pages shown by
  address, full-text search in a dialog, code blocks with language tabs
  that follow the reader, a contents list that tracks the section being
  read, and a drawer on phones. Its README had claimed a skip link that
  did not exist; the claim is gone and no skip link was added.
- `wiki-portal`: faint text raised to `#aaa3cc` (it was 3.56:1 on
  panels, in three places; the triage had found one), the CX chip
  darkened to `#2f7a4a` (3.27:1 before), and the footer no longer calls
  its content "placeholder text".
- `event-site` and `wiki-portal` now carry the page-wide `[hidden]`
  guard, as 11 other templates do; the remaining 8 guard each element
  they hide instead. Nothing rendered while hidden in either template,
  before or after.
- Defects the rebuilds introduced were caught by the same evidence
  before shipping; each template's list is in the findings.

**Verified**
- Every template, at its final state: no horizontal overflow at the
  eight documented widths or twelve widths between them; no console
  errors; 0 contrast failures among measured text nodes at 1440 and
  375px; every tab stop visibly focused, with rings at 3:1 or better
  against the surface behind them.
- Every template's full page viewed at 1440 and 375px, plus the states
  that matter to it (errors, confirmations, dialogs, drawers, menus,
  filters), and every interactive control driven with real key and
  mouse events at both widths. Time-based behaviour was driven with a
  faked clock where a template depends on it (`small-business`,
  `restaurant-site`).
- Reduced motion checked by emulation wherever a template moves, and
  print fallbacks present wherever content fades in.

**Changed**
- Manifests and registry entries for the 20 rebuilt templates are at
  2.0.0, `wiki-portal` at 1.1.0. Descriptions and when-to-use lines were
  rewritten to match, and `wiki-portal`'s no longer calls its rail fixed.
- Every rebuilt README has new Composition and Recreating sections, and
  `templates-index.js` and `templates/INDEX.md` were re-derived per
  template. Hooks built by string concatenation, which the derivation
  records truncated, were corrected by hand.
- `templates/INDEX.md`'s list of templates that load `motion-utils.js`
  no longer includes `small-business`.
- The showcase preview for `documentation-site` is now three columns
  under a top bar, matching the page. The other previews are abstract
  wireframes and still fit, so they are unchanged.
- DESIGN.md section 8.2 adds eight defect classes found in more than
  one template: shared element styles outranking a template class,
  template resets outranking their own classes, `display` beating
  `hidden`, targets under sticky headers, focus rings measured against
  the wrong surface, opacity as de-emphasis or reveal, inline content
  as grid items, and `var()` in SVG and derived custom properties.
- PRD section 14 adds M14 for this review and D6 below.
- `event-site`'s countdown cells start at `0`, `00` and `00` instead of
  a double dash, so the project-wide double dash search stays clean. The
  script replaces them on load, as before.
- DESIGN.md section 3 now describes the per-template identity pattern:
  a page class holding the template's own tokens, prefixed selectors,
  `:where()` resets and the `[hidden]` guard.
- `templates/INDEX.md` and the README no longer call the templates'
  content placeholder; it is complete invented content, to be replaced.
- The README's docs tree and documentation list include the review
  findings, its status table mentions the review, and its version is
  v0.12.0.

**Still open**
- D6: `wiki-portal` has a skip link, and the review brief says not to
  add them. It was left alone and needs a decision; see PRD section 14.
- No screen reader was run. Attribute and focus checks are not a screen
  reader test.
- Hover was driven only where the findings say so.
- Text on gradients and drawn artwork was judged by eye in screenshots,
  not measured.
- `documentation-site` is audited on its first page; the other six
  pages were viewed and driven but not contrast-measured, though they
  use the same colour pairs.
- Sampled widths are not a continuum, even at twenty.
- Every form still stops at a visible demo notice, by design (PRD
  section 18).

---

## v0.11.3, 2026-09-06

The first automated responsive sweep of the whole project. It found four
overflow defects, all in the Education section, which is the part whose
verification pass predates every tool used to find them.

**Fixed**
- `.content` now carries `min-width: 0` (`assets/css/components.css`). It
  is a flex item in the wiki layout, so its automatic minimum size was its
  content-based minimum and it would not shrink below the widest thing
  inside it. A demo stage and a table were therefore pushing their whole
  page wider than the viewport even though both already declared
  `overflow-x: auto` for exactly that reason. This one line fixes three of
  the four defects: `responsive-and-mobile-first-thinking.html` (which
  overflowed at 1024, 768, 414, and 320px, laying 590px of content into a
  399px viewport, making the page that teaches mobile-first the only page
  in the project that failed at every width below desktop),
  `education/index.html` at 320px, and `visual-hierarchy.html` and
  `interaction-states-and-feedback.html` at 320px.
- `.portfolio-grid` now uses `minmax(min(320px, 100%), 1fr)` instead of
  `minmax(320px, 1fr)` (`assets/css/portfolio-layout.css`). A bare track
  floor cannot collapse below its own minimum, so on a 320px screen the
  template showcase grid was wider than the screen.

**Verified**
- 0 overflow cases across all 46 pages at 320, 414, 768, 1024, and 1440px,
  and again at the seven widths DESIGN.md section 8.1 documents: 322
  page-width combinations, no failures.
- The elements that should scroll inside their own box now do rather than
  pushing the page: `.table-wrap` reports a 333px scroll width inside a
  257px box.
- The interactive demo on `responsive-and-mobile-first-thinking.html` is
  intact at 414px, slider and frame and readout, not squashed.

**Changed**
- DESIGN.md section 8.1 adds 320px to the audit widths. All four defects
  existed only at or below 375px, which was previously the narrowest width
  checked.
- DESIGN.md section 8.2's flex `min-width: auto` entry now records that
  this exact pattern shipped despite being documented there with the
  correct fix, because nothing measured it.
- PRD section 16 adds an "Overflow sweep" subsection, including the
  `width: min-content` probe used to find which element forces an
  overflow rather than only that one exists.
- PRD section 14 records D2 to D5 and their two shared root causes.

**Still open**
- Hover states and screen reader output, unchanged from v0.11.2.
- The sweep measures overflow only. A page that passes it can still be
  ugly at 320px, and five or seven sampled widths are not a continuum:
  `wiki-portal`'s topbar defect in v0.11.1 lived in a band between
  breakpoints and this method would not have caught it.

---

## v0.11.2, 2026-09-06

Interaction verification, the tier v0.11.1 left open. It turned out not to
need Node: Chromium's DevTools Protocol is a websocket, and a websocket
client was already available. One defect found.

**Fixed**
- `waitlist-signup`: `#waitlist-status` carried no `role="status"`, so the
  notice telling the visitor the form does not really submit was announced
  to sighted users only. The other four demo notices in the library
  (`sb-form-status`, `rsvp-status`, `donate-status`, `cart-status`) all
  had it. Added, which makes the five consistent. This matters more than a
  usual live-region miss: section 18 requires the page to admit it is not
  functional, and a notice a screen reader never reads does not meet that
  requirement for the person most likely to be misled by a form that
  silently does nothing.

**Verified**
- `wiki-portal` interaction, driven by real key and mouse events: the
  tablist roves `tabindex` and moves `aria-selected` on arrow keys and
  wraps at the ends; the More menu opens on click, closes on Escape, and
  returns focus to its button; the rail filter narrows 31 links to 3 and
  hides the 6 groups it empties; the drawer opens below 760px, closes on
  Escape, and returns focus to the toggle; the width toggle sets
  `is-wide` and `aria-pressed`.
- All five non-functional demo notices fire on a real click of their real
  control and write the disclaimer section 18 requires.
- Every `elementHooks`, `selectorHooks`, and `nonFunctionalTargets` entry
  in `assets/js/templates-index.js` resolves against the live DOM, across
  all 21 templates, 0 unresolved. The index is now confirmed against the
  rendered pages, not only derived from the source.
- Every button, tab, summary, checkbox, radio, and `aria-expanded` or
  `aria-pressed` control on all 46 pages was clicked: 251 controls, zero
  errors thrown.

**Changed**
- `docs/PRD.md` section 16 gained an "Interaction verification"
  subsection and a correction. The previous text said driving interaction
  "needs a runtime this project does not assume", which was wrong. It now
  documents the three required flags, and the two traps that make an
  interaction test lie rather than fail: dispatching mouse events at a
  control below the fold, which silently clicks nothing and still reports
  success, and synthesising events instead of driving the real control,
  which bypasses native validation and misses button-driven templates.

**Still open**
- Hover states, which have no reliable protocol equivalent, and screen
  reader output beyond confirming the attributes are present.

---

## v0.11.1, 2026-09-06

The browser verification that milestones M9 and M11 had left open is now
done, and it found two defects.

**Fixed**
- `admin-dashboard`: the sidebar navigation links rendered as inline text
  on two run-together lines instead of stacking. The rule was written as
  `.dashboard-sidebar nav a`, but `.dashboard-sidebar` is itself the
  `<nav>`, so the selector required a `<nav>` inside a `<nav>` and matched
  nothing: the links kept their default inline display, padding, and
  radius, and the active item had no highlight. Corrected to
  `.dashboard-sidebar a`.
- `wiki-portal`: between 761px and roughly 1080px the sister-wiki chips
  overflowed their group and were painted on top of the page action
  links. `.wiki-topbar-left` carried `min-width: 0`, which let it compress
  below the width of its own contents; the chips are a fixed 30px each and
  so spilled out of the box rather than shrinking with it. The topbar and
  both of its groups now wrap instead of compressing, the chips are
  `flex: 0 0 auto`, and the redundant `flex-wrap` in the 760px step was
  removed. The full-width layout is unchanged.

**Verified**
- All 21 templates, both section landing pages, the root page, and all 21
  education pages were loaded in headless Edge over `file://` and produce
  zero page-level console errors.
- `wiki-portal` was checked at 1400, 1100, 1000, 900, 800, 740, and 500px.
  The D1 masthead fix holds: the band is continuous across the rail
  boundary with no scrollbar seam, and the rail becomes a drawer below
  760px as intended. `script.js` runs, confirmed by the live UTC clock in
  the utility row.
- A scan of every template's stylesheet for selectors that cannot match
  its markup found only the `admin-dashboard` case above.

**Added**
- `docs/PRD.md` section 16 gained a "Verification sweep" subsection: the
  headless Chrome and Edge invocation used above, the four details that
  separate a real check from a false pass (scratch profile, log filtering,
  virtual time budget, several widths), and an explicit statement of what
  the sweep does not cover. It is a verification aid invoked from outside
  the project, not a dependency of it, so the no-build-step constraint in
  section 9 is unaffected.

**Still open**
- Interaction states are not covered by this pass. Screenshots verify
  first paint, not hover, focus, keyboard traversal of the tablist, the
  More menu, or the drawer's open state.

---

## v0.11.0, 2026-09-06

A documentation release. No template's markup, styles, or behavior
changed. What changed is that the library now states, as a contract, that
it is meant to be read by models as well as people, and carries the
records that make that true.

**Added**
- A third goal in `docs/PRD.md` section 3, co-equal with teaching and with
  the template library: every template is documented well enough to be
  rebuilt as a live site by a person or a model that has never seen the
  project.
- `docs/PRD.md` section 13.6, the template composition and recreation
  contract, mirroring the Education layer's queryability contract in
  section 12.3. It fixes the README section list and order, requires the
  two indexes below, requires composition facts to be derived from the
  files rather than recalled, requires non-functional demo elements to be
  named by id, and states five acceptance criteria.
- `assets/js/templates-index.js`, `window.WIREFRAME_TEMPLATE_INDEX`: one
  record per template giving its entry point, pages, shared and own
  stylesheets and scripts, region outline, layout grids, breakpoints,
  bound events, element and selector hooks, non-functional targets, and
  concepts demonstrated. It is a single global assignment, so it can be
  read as plain text without being executed.
- `templates/INDEX.md`, the markdown mirror of that index: an
  all-templates table, the shared dependency map, and a region outline per
  template, for a reader working only in markdown.
- `## Composition` and `## Recreating this as a live site` sections in all
  21 template READMEs. Composition is the mechanical record of the files;
  Recreating is three lists, Replace, Wire up, and Keep, the last naming
  the structural decisions a rebuild should not quietly discard, with the
  reason.
- `## Purpose` and `## Reading this project as a model` in the root
  `README.md`: the three purposes of the project, and a routing table
  from a question to the file that answers it.

**Changed**
- `templates/TEMPLATE_CONTRACT.md` gained a README contract listing the
  six required sections in order and defining what Composition and
  Recreating must contain, a four step process for adding a template, and
  deterministic derivation rules for every index field, so two readers
  re-deriving an index from the same folder get the same answer. No tool
  ships to do that derivation, and none should: section 9 of the PRD rules
  out a build step and the README promises no runtime is needed.
- The root `README.md` directory tree now lists `templates-index.js`,
  `templates/INDEX.md`, and `wiki-portal/`, and the "adding a template"
  note names all four steps rather than three.

**Still open**
- Live browser verification of `wiki-portal` and the 15 templates from
  milestone M9. None of this release's changes touch runtime code, but
  that verification has not been done and is not claimed.

---

## v0.10.0, 2026-09-06

A twenty-first template: a community wiki front page, the reference-site
counterpart to the existing `documentation-site` and `help-center`
templates.

**Added**
- `templates/wiki-portal/`, with `index.html`, `manifest.js`,
  `styles.css`, `script.js`, and `README.md`, satisfying the folder
  contract. It demonstrates a directory-style home page: a fixed
  168px navigation rail with its own scroll, a sticky chrome strip of
  page tabs, page actions, and search, and a main column of a welcome
  block with statistics, a featured banner, three update cards, six
  portal tiles, a three-column link grid beside a promo rail, and three
  dated link panels. No new concept was required; it demonstrates six
  existing Phase 1 concepts.
- One manifest entry appended to `assets/js/templates-registry.js`,
  taking the registry from 20 to 21 entries with no existing entry
  modified.
- One preview layout added to `templates/index.html` for the
  `wiki-portal` id, following the existing rail-and-content pattern used
  by `documentation-site` and `admin-dashboard`.

**Fixed**
- `wiki-portal`, defect D1 (PRD section 14): the masthead artwork broke at
  the rail boundary, showing a scrollbar track and a colour mismatch where
  the band should have been continuous. The rail was its own scroll
  container, and the artwork was painted twice into boxes of very
  different widths, so its percentage-based gradient resolved differently
  in each. The layout is now a two-track grid with the rail as a static
  column and the artwork as a single element spanning both tracks. The
  rail keeps a scroll of its own only as the narrow-width drawer.

---

## v0.9.0, 2026-07-27

Milestone M9 complete: the template library expanded from 5 to 20
templates, built directly into the redesigned system from M10, per the
recommended build order (M8, then M10, then M9).

**Added**
- 15 new templates under `/templates/`, each with `index.html`,
  `manifest.js`, `styles.css`, `script.js`, and `README.md`, verified by
  script to satisfy the folder contract in full: `ecommerce-product`,
  `ecommerce-storefront`, `pricing-page`, `event-site`, `nonprofit-site`,
  `restaurant-site`, `real-estate-listing`, `course-landing`,
  `resume-site`, `community-forum`, `waitlist-signup`,
  `onboarding-flow`, `admin-dashboard`, `careers-page`, and
  `help-center`. Each demonstrates a distinct set of existing Phase 1
  concepts; no new concept was required.
- 15 new manifest entries appended to `assets/js/templates-registry.js`,
  taking the registry from 5 to 20 entries with no existing entry
  modified.
- 15 new CSS and inline SVG preview layouts added to
  `templates/index.html`'s preview system, one per new template id.

**Changed**
- All 14 Education concept pages and their markdown mirrors: "Used In
  Templates" sections updated to link whichever of the 15 new templates
  demonstrate that concept, alongside the original 5. Several concepts
  (`navigation-and-information-architecture`, `content-design-and-microcopy`,
  `forms-and-inputs`, `interaction-states-and-feedback`) now link 9 or
  10 templates each.
- `docs/PRD.md` section 13.5: the 15-template candidate list is now a
  built list; the "why 20, why now" and rescheduling rationale left
  in place as the historical record of the decision, with a new status
  note on what is and is not yet verified.
- `docs/PRD.md` roadmap: M9 marked built, with the same category of open
  item M4 and M7 had before the maintainer verified them in an actual
  browser.

**Fixed**
- A real writing style violation introduced while building the Nonprofit
  and Charity Site template: a testimonial attribution used the
  `&mdash;` entity. Caught by the project's own em dash and double dash
  sweep before this version shipped, and fixed.
- A real missing-CSS bug: the Nonprofit and Charity Site template's HTML
  referenced an `.option-button` class that only existed in a different
  template's stylesheet. Templates do not share stylesheets with each
  other; the class definition was added to this template's own
  `styles.css`.
- A real missing-CSS bug: the Real Estate Listing Site template used
  `<select>` elements with no styling anywhere in the shared component
  set (no template had used a `<select>` before this one); styled
  directly in this template's own `styles.css` to match existing input
  styling.
- A real color-inheritance bug: the E-commerce Storefront template
  wrapped product tiles in `<a>` elements with no color override, which
  would have rendered every product title in the accent teal color
  instead of the intended primary text color. Fixed before it shipped.

**Removed**
- Nothing.

**Status**
- Phase 1 (Education) and Phase 2 (Templates, original 5-template
  scope): unchanged, complete and verified in Chrome.
- The 15 new templates: built and statically verified (folder contract,
  links, JavaScript element references, writing style). Live browser
  verification has not been run yet.
- M8 and M10: unchanged, complete.
- Roadmap is now fully built end to end: M0 through M10 all have code or
  documentation in place. The only remaining open item across the whole
  project is live browser verification of the 15 new templates.

---

## v0.8.0, 2026-07-26

Milestones M8 and M10 complete: a real, computed accessibility audit of
every color token, and a full presentation and marketing redesign across
the root landing page, both section overviews, all 14 concept pages, and
4 of the 5 templates.

**Added**
- `assets/js/motion-utils.js`: a shared `observeFadeIn(selector)` helper
  using `IntersectionObserver`, with a graceful fallback for browsers
  without it.
- `.fade-in-up` component in `assets/css/components.css`, generalized
  from the Landing Page template's own duplicated entrance-motion CSS.
- A rebuilt root `index.html`: a real hero (headline, subhead, primary
  and secondary calls to action), a two-step section connecting Education
  and Templates with links both directions, and a three-module curriculum
  preview, replacing the previous single-paragraph placeholder page.

**Changed**
- `assets/css/theme.css`: `--color-text-tertiary` changed from `#6e7681`
  to `#7c8487`. The original value scored 4.12:1 against
  `--color-canvas` and 3.77:1 against `--color-surface`, both under the
  4.5:1 WCAG AA minimum, computed rather than estimated, using the same
  relative-luminance formula the site's own contrast checker demo already
  implements. This token is used for real content (post dates, footer
  text, sidebar section labels), not exempt placeholder or disabled text,
  so the failure was real, not theoretical. The new value passes against
  all three backgrounds it is actually paired with (4.96:1, 4.54:1,
  5.39:1).
- `docs/DESIGN.md` section 2.1: removed a stale warning against pairing
  `--color-text-tertiary` with `--color-surface-inset`, written before
  any ratio had actually been computed. The real audit found that
  pairing was the closest to passing of the three (4.47:1 with the old
  value); `--color-surface` was the actual worst case and had not been
  mentioned at all.
- `education/index.html`: fixed a real stale-copy bug found by the M10
  self-audit. A callout claimed concept pages "are being written next,"
  left over from before milestone M3 shipped all 14 of them. Rewritten
  to describe the site's actual, current structure, and a new sentence
  added bridging to the template library.
- `templates/index.html`: added a bridging sentence back to Education for
  visitors who land there first.
- Landing Page template: its duplicated `IntersectionObserver` fade-in
  logic in `script.js` replaced with a call to the new shared
  `motion-utils.js`, removing the now-redundant CSS from its own
  `styles.css`.
- Portfolio Site, Blog and Article Site, and Small Business templates:
  entrance motion added to project cards, post list items, and service
  cards respectively, each wired through the same shared utility.

**Fixed**
- The one real accessibility defect and the one real stale-copy defect
  described above; both found by the audits this version's milestones
  required, not introduced and then fixed within this version.

**Removed**
- Nothing.

**Status**
- M8 (theme revisitation) and M10 (presentation and marketing redesign):
  both complete. Full records in DESIGN.md sections 10.1 and 11
  respectively, including two M8 findings reviewed and deliberately left
  unchanged (body text line height, border non-text contrast) and one
  M10 scope boundary held deliberately (no motion added to the
  Documentation Site template, since it has no scroll-reveal content).
- M9 (template library expansion to 20): still planned, now scheduled to
  build directly inside the redesigned system from M10.

---

## v0.7.4, 2026-07-26

Reordered the roadmap milestone table's rows to match recommended
execution order (M8, M10, M9) instead of ID order, per the maintainer's
request, since v0.7.3 had explained the reordering in prose but left the
table itself in numeric ID order.

**Changed**
- PRD.md section 14's milestone table: M10's row now appears before M9's
  row, with a one-line note that this is intentional, not a mistake,
  immediately above the existing "Recommended build order" writeup that
  explains why.

**Status**
- Unchanged from v0.7.3: M8, M9, and M10 all planned, none started.
  Recommended and now visually reflected execution order is M8, M10, M9.

---

## v0.7.3, 2026-07-26

Expanded M10's scope to everything (at the maintainer's explicit request)
and reordered the roadmap accordingly. Documentation only; nothing was
rebuilt in this version.

**Changed**
- DESIGN.md section 11 (M10): scope expanded from "root landing page plus
  section intros" to genuinely everything, the root landing page, all 14
  Education pages, and the full template library. The previous
  "explicitly out of scope" list (Education concept pages, template
  internal design) was removed; the only remaining boundary is the hard
  constraint floor in PRD.md section 9.
- DESIGN.md section 11 and PRD.md section 13.5: sequencing updated. M9
  (template library expansion to 20) moved from "scheduled after M7,
  independent of M10" to "scheduled after M10," since M10 now covers the
  template library's own presentation; building the 15 new templates
  directly in the redesigned system avoids redesigning the whole library
  twice.
- PRD.md section 14: added a "Recommended build order" writeup answering
  the maintainer's direct question about sequencing, since the milestone
  IDs (M8, M9, M10) no longer run in numeric execution order. Recommended
  order: M8 (token revisit) first, then M10 (full redesign) once tokens
  are finalized, then M9 (15 new templates, built directly in the
  redesigned system) last.
- PRD.md's roadmap milestone table and feature breakdown: M9 and M10's
  rows and descriptions updated to reflect the new dependency and scope.

**Status**
- Phase 1 (Education) and Phase 2 (Templates, 5-template scope):
  unchanged, complete.
- M8, M9, and M10: all planned, none started. Recommended execution
  order is now M8, M10, M9.

---

## v0.7.2, 2026-07-26

Added a new roadmap milestone, M10, for a presentation and marketing
redesign of Wireframe itself. Documentation only; nothing was rebuilt in
this version, per explicit instruction to add this to the roadmap without
starting it now.

**Added**
- DESIGN.md section 11, "Presentation and marketing redesign (milestone
  M10)": a design brief distinct from section 10's token-only theme
  revisit. In scope: a real landing page treatment for root `index.html`,
  a clearer narrative connecting Education and Templates, purposeful
  motion, and a copywriting pass on the site's own marketing-facing
  pages, all explicitly framed as applying Wireframe's own curriculum to
  Wireframe itself, including a `common-design-mistakes` self-audit
  before sign-off. Explicitly out of scope: the Education concept pages'
  own demos, the templates' internal design, and anything that would
  violate the hard constraints in PRD.md section 9.
- M10 added to PRD.md's roadmap milestone table and feature breakdown,
  scheduled after M8 (build on finalized tokens, don't redesign twice)
  and explicitly independent of M9 (a marketing redesign and a template
  count increase don't depend on each other).

**Status**
- Phase 1 (Education) and Phase 2 (Templates, 5-template scope):
  unchanged, complete.
- M8 (theme revisitation), M9 (template expansion to 20), and M10
  (presentation and marketing redesign): all planned, none started.

---

## v0.7.1, 2026-07-26

Added a new roadmap milestone, M9, planning the template library's
expansion from 5 to 20 templates. Documentation only; no template code
was built in this version.

**Added**
- PRD.md section 13.5, "Template library expansion (milestone M9)": the
  rationale for going from 5 to 20 templates now rather than later, a
  15-template candidate list (each mapped to existing Phase 1 concepts,
  no new concept required), the additive build process (identical to the
  existing folder and registry contract in section 13.3), and M9's own
  acceptance criteria, including confirming the showcase page's
  `auto-fill` grid holds at 20 entries, not just the 1-to-8 range tested
  in M6.
- M9 added to the roadmap milestone table and feature breakdown in
  section 14, scheduled after M7 (proven correct at small scale first)
  and explicitly not blocked on M8 (a theme revision and a template count
  expansion are independent changes).

**Changed**
- PRD.md section 8's Future feature list and section 14's "Explicitly
  deferred items": the previously open-ended "templates beyond the five
  starter templates" deferral is now a scheduled milestone (M9) with a
  concrete target of 20; anything past 20 remains genuinely deferred.

**Status**
- Phase 1 (Education) and Phase 2 (Templates, initial 5-template scope):
  unchanged, complete.
- M9 (template library expansion to 20): planned, not started.
- M8 (theme revisitation): unchanged, planned, not started.

---

## v0.7.0, 2026-07-26

M4 and M7 complete: the maintainer opened the site in an actual browser
and confirmed it works correctly, closing the one verification gap this
session could not close directly (no headless browser tool was available
in this environment). No code changed in this version; this is a status
update only.

**Changed**
- `docs/PRD.md`'s roadmap milestone table: M4 and M7 marked Complete. The
  "Current phase" summary and the M4/M7 feature-breakdown entries updated
  to reflect that both phases are now built and verified, not just built.

**Status**
- Phase 1 (Education): complete. M0 through M4 all done.
- Phase 2 (Templates): complete. M5 through M7 all done.
- Remaining, not blocking either phase: M8 (theme revisitation, DESIGN.md
  section 10) and the candidate backlog (PRD.md section 12.5.4).

---

## v0.6.2, 2026-07-26

Removed the skip-to-content link, at the maintainer's explicit request,
after confirming they meant full removal rather than a visibility bug (it
was built to stay off-screen until keyboard-focused, per the original
intent in DESIGN.md).

**Removed**
- The `<a class="skip-link" href="#main-content">Skip to content</a>`
  element from all 23 pages that had it: all 22 Education pages and the
  Documentation Site template.
- The `.skip-link` and `.skip-link:focus` rules from `assets/css/base.css`.
- The skip-link requirement from `docs/DESIGN.md` section 4.1 (sidebar
  spec) and section 6.2 (accessibility requirements), and the skip-link
  mention from `docs/PRD.md`'s M1 feature breakdown.

**Changed**
- `docs/DESIGN.md` section 6.2 now documents this as a known, deliberate
  exception to WCAG 2.4.1 (Bypass Blocks): the site targets WCAG AA
  overall, but a keyboard-only sighted user now has no way to bypass the
  sidebar's links without a screen reader's landmark navigation. This is
  recorded as an intentional gap, not a silently dropped requirement.

**Status**
- Phase 1 (Education) and Phase 2 (Templates): unchanged otherwise from
  v0.6.1. M4 and M7's live browser verification remain the only other
  open items, and should now also re-check keyboard navigation without
  assuming a skip link exists.

---

## v0.6.1, 2026-07-26

Fixed a real navigation dead end in the Education section's sidebar.

**Fixed**
- The "Wireframe" wordmark link at the top of the sidebar, present on all
  22 Education pages (the section overview, all 7 module index pages, and
  all 14 concept pages), pointed to `education/index.html`. Since the
  root `index.html` (the page that lets a visitor choose between Education
  and Templates) was only reachable from that root page itself, there was
  no link back to it anywhere inside the Education section once a visitor
  went past the section overview. The wordmark link now points to the
  root `index.html` on every one of those 22 pages, verified to resolve
  correctly by depth (`../index.html` from `education/index.html`,
  `../../index.html` from every module and concept page).

**Status**
- Phase 1 (Education) and Phase 2 (Templates): unchanged from v0.6.0,
  M4 and M7's live browser verification remain the only open items.

---

## v0.6.0, 2026-07-26

Milestones M5 and M6 complete: Phase 2 (Templates) is now built. All five
starter templates exist, the registry and showcase page render them, and
every Education concept page's "Used In Templates" section now links to
its real, demonstrating templates instead of the Phase 2 placeholder note
used throughout M3.

**Added**
- Five starter templates under `/templates/`: `landing-page`,
  `portfolio-site`, `blog-article` (with a second page, `article.html`),
  `documentation-site`, and `small-business`, each with `index.html`,
  `manifest.js`, `styles.css`, `script.js`, and `README.md` per the
  folder contract in PRD.md section 13.3.
- `assets/js/templates-registry.js`: `window.WIREFRAME_TEMPLATES`, one
  manifest object per template.
- `assets/css/portfolio-layout.css`: the portfolio grid and showcase card
  styles deferred since M1, implemented now that Phase 2 needs them.
- `templates/index.html`: the portfolio style showcase page, rendering
  one card per registry entry with a CSS and inline SVG generated
  preview keyed by template id, verified to render correctly regardless
  of registry length.
- `templates/TEMPLATE_CONTRACT.md`: a quick reference copy of the folder
  and registry contract, kept alongside the templates themselves.
- The Small Business template's contact form demonstrates the security
  requirement in PRD.md section 18 directly: it intercepts its own
  submit event and displays a visible notice that it is a non-functional
  demo, rather than silently pretending to submit anywhere.
- The Small Business template's README includes the explicit
  before-and-after `common-design-mistakes` example required by PRD.md
  section 13.2 (a vague "Learn more" button and ambiguous "Open weekdays"
  hours, corrected to a direct `tel:` call action and fully spelled out
  hours).

**Changed**
- All 14 Education concept pages and their markdown mirrors: the "Used In
  Templates" section, previously a placeholder note that Phase 2 had not
  been built, now links directly to each concept's demonstrating
  templates using real relative links.
- Root `index.html`: the disabled "Templates (Phase 2, not yet built)"
  label replaced with a working link to `templates/index.html`.
- PRD.md's roadmap milestone table: M5 and M6 marked Complete. M4 and M7
  marked Partial, both blocked on the same open item (see Fixed, below,
  for what is and is not resolved).

**Fixed**
- A real writing style violation introduced while building the Small
  Business template: a testimonial attribution used the `&mdash;` entity
  ("&mdash; Dana R., repeat customer"). Caught by the same project-wide
  em dash and double dash sweep required by section 6, and replaced with
  plain text before this version shipped.

**Removed**
- Nothing.

**Status**
- Phase 1 (Education): built, M0 through M3 complete. M4 (live browser
  and responsive verification) remains open.
- Phase 2 (Templates): built, M5 and M6 complete. M7 (the same live
  verification, applied to the five templates) remains open.
- Both open items are the same kind of gap: this session had no headless
  browser tool available to drive an actual Chrome window, so everything
  verified this session was static (links, JS id references, path
  resolution, writing style). A live pass in an actual browser is the
  one thing still needed before either phase can be marked fully
  complete.

---

## v0.5.0, 2026-07-26

Milestone M3 complete: Phase 1 (Education) is now fully built. All 14
concept pages exist, each with a markdown mirror, a populated
`concepts-index.js`, and `education/INDEX.md`.

**Added**
- 14 concept HTML pages across all 7 modules, each following the fixed
  heading hierarchy and anchor convention in PRD.md section 12.3, and each
  with a working interactive demo built in vanilla JavaScript: a hierarchy
  strength slider (`visual-hierarchy`), a grid overlay toggle
  (`layout-and-grid-systems`), a spacing scale toggle
  (`spacing-and-rhythm`), a resizable breakpoint frame
  (`responsive-and-mobile-first-thinking`), a line length and line height
  control (`typography`), a live WCAG contrast ratio calculator
  (`color-and-contrast`), a three-step accessibility checklist
  (`accessibility-and-wcag-basics`), a flat-versus-grouped navigation
  toggle (`navigation-and-information-architecture`), a before-and-after
  microcopy rewrite (`content-design-and-microcopy`), an inline-versus-
  submit-time validation toggle (`forms-and-inputs`), a live button state
  cycle (`interaction-states-and-feedback`), a duration and reduced-motion
  toggle (`motion`), a UI-only-versus-UX-aware toggle (`what-is-ui-ux`),
  and a four-issue flag-and-fix demo (`common-design-mistakes`).
- 14 markdown mirrors under `education/md-mirror/`, one per concept, using
  the same fixed heading order as their HTML counterparts.
- `assets/js/concepts-index.js`: `window.WIREFRAME_CONCEPTS`, one entry
  per concept, matching the shape in PRD.md section 12.3.
- `education/INDEX.md`: the human readable mirror of that index.
- `assets/js/demo-utils.js`: shared helpers (`clamp`, `debounce`,
  `contrastRatio`, `breakpointName`) used across several concept demos.
- New CSS components in `assets/css/components.css`, filling in the specs
  from DESIGN.md section 4 that M1 had deferred: demo container, demo
  controls, tab buttons, range and text inputs, and card.

**Changed**
- PRD.md's roadmap milestone table: M3 marked Complete. The "Current
  phase" summary now describes Phase 1 as fully built.
- README.md's Phase order and current status table, updated to reflect
  Phase 1's completion.
- DESIGN.md section 4.6 (Interactive control): fixed a stale
  cross-reference left over from an earlier renumbering, which pointed to
  "sections 4.9 and 4.10" (table and template showcase card) for button
  and input styling; now correctly points to section 4.8 (button) and
  describes input styling directly, since no separate DESIGN.md
  subsection exists for raw text and range inputs.

**Fixed**
- A curriculum count error present since the original PRD draft, before
  any research or implementation work began: the module tables in section
  12.1 always listed 2, 3, 2, 1, 2, 3, and 1 concepts per module, which
  sums to 14, but the surrounding prose in seven separate places called
  this "thirteen concepts" or "13 concepts." All seven instances are now
  corrected to fourteen. This was caught by counting the actual markdown
  mirror files written for M3 against the prose count and finding a
  mismatch, not by re-deriving the number from scratch.

**Removed**
- Nothing.

**Status**
- Phase 1 (Education): complete. M0 through M3 all done.
- Phase 2 (Templates): not started, blocked by Phase 1 acceptance
  criteria review (PRD.md section 12.4).

---

## v0.4.2, 2026-07-26

Second follow-up to M2.9: used the ongoing intake process built in
v0.4.0 to search for and find sources for the two concepts the research
pass could not validate, `content-design-and-microcopy` and `motion`.

**Changed**
- PRD.md section 12.5.3: `content-design-and-microcopy` upgraded to
  Confirmed, citing NN/G's "3 I's of Microcopy" framework (Inform,
  Influence, Interact) found via a targeted search after the original
  fixed-list mapping turned out to be a mismatch. `motion` upgraded to
  Confirmed, citing NN/G's two-part animation series: motion should
  communicate feedback, state change, or affordance rather than
  decoration, with concrete duration guidance (roughly 100ms for simple
  feedback, 200 to 300ms for modals, a ceiling near 400 to 500ms,
  ease-out for entrances, and a hard requirement to respect
  `prefers-reduced-motion`).
- PRD.md section 12.5.4's candidate backlog: logged both new sources as
  processed, confirming existing concepts rather than becoming new
  backlog candidates.
- PRD.md section 12.5.2 finding 4 (the token cross-validation) is now
  reinforced twice over: DESIGN.md's `--transition-fast` (100ms),
  `--transition-base` (150ms), and `--transition-slow` (250ms) all land
  inside NN/G's recommended ranges, independently confirmed by both the
  `button-states` source in the original pass and this pass's NN/G
  animation-duration source.

**Added**
- None beyond the PRD.md content above.

**Fixed**
- None.

**Removed**
- Nothing.

**Status**
- Phase 1 (Education): M2.9 fully complete, all 13 concepts confirmed.
  M3 (concept pages, markdown mirrors, `concepts-index.js`) next.
- Phase 2 (Templates): not started, blocked by Phase 1.

---

## v0.4.1, 2026-07-26

Follow-up to M2.9: the initial research pass had treated several Figma
resource library category pages as if they were single articles, when they
are actually indexes linking to individual articles. This pass drilled into
those category pages, found their real article links, and fetched the
articles themselves.

**Changed**
- PRD.md section 12.5.2: two new cross-cutting findings (5 and 6).
  Finding 5 gives citable typography mechanics from `typography-in-design`
  (roughly 16px body scaling to 48px H1, 1.125 to 1.2 times line height,
  40 to 60 character line length) and notes DESIGN.md's `--font-size-4xl`
  token already has the 48px value, currently reserved for template hero
  headlines, as an observation for the future theme revisit, not a change
  made now. Finding 6 gives citable color-role guidance from
  `what-is-color-theory` and `color-combinations` (light/muted backgrounds,
  dark text for contrast, bright/saturated accents), independently
  matching DESIGN.md's own token roles. Finding 2 (Nielsen's heuristics)
  was upgraded from a general reference to the exact, citable list of all
  10 heuristics with a precise per-concept mapping.
- PRD.md section 12.5.3: `typography` and `color-and-contrast` upgraded
  from source-limited to Confirmed. `content-design-and-microcopy`'s
  original source mapping was found to be a genuine mismatch (the assigned
  category is about UX research artifacts like journey maps and personas,
  not microcopy) and is now marked "Not validated, mapping corrected"
  rather than left as a soft source-limited note; it and `motion` are
  named as the top two priorities for a manual source check before M3
  writes those two pages.
- The persistent research-sources memory note left unchanged; the
  candidate backlog and relevance filter it describes already accommodate
  this kind of correction.

**Added**
- None beyond the PRD.md content above.

**Fixed**
- The `content-design-and-microcopy` to `ux-and-communication-strategy`
  source mapping from section 12.5.1, corrected in section 12.5.3 rather
  than silently left inaccurate.

**Removed**
- Nothing.

**Status**
- Phase 1 (Education): unchanged, M0 through M2.9 complete, M3 next.
- Phase 2 (Templates): not started, blocked by Phase 1.

---

## v0.4.0, 2026-07-26

Milestone M2.9 complete: the 13-concept curriculum was checked against the
fixed external source list from PRD.md section 12.5.1, before any concept
page is written in M3. A second, broader source list was also reviewed to
establish an ongoing intake process, per explicit request that curriculum
research not be a one-time, closed event.

**Added**
- PRD.md section 12.5.2: four cross-cutting findings from the research
  pass, most notably that Nielsen's 10 Usability Heuristics and Fitts's Law
  are widely cited frameworks with no explicit named citation anywhere in
  the current curriculum, now logged as M3 authoring requirements (name
  them explicitly in the relevant concept pages) rather than new concepts.
- PRD.md section 12.5.3: a per-concept validation table for all 13
  concepts. No concept was reordered, reprioritized, or reassigned a
  different difficulty level; several were confirmed with minor content
  refinements, and a few (`color-and-contrast`, `content-design-and-microcopy`,
  `motion`) are flagged as source-limited and worth a deeper manual check
  before M3 writes those specific pages.
- PRD.md section 12.5.4: an ongoing curriculum research intake process,
  explicitly not re-closed the way section 12.5.1's list was for M2.9
  itself. Defines a relevance filter (visual, interaction, or content
  design principles for building a website, not business strategy, team
  process, AI tooling, or UX research methodology) and three outcomes for
  any future source: confirms/refines an existing concept, becomes a
  candidate-backlog entry for a future concept or module, or is logged as
  out of scope with a one-line reason.
- A candidate backlog (within 12.5.4) seeded from a 24-URL review of
  additional Figma resource library categories. Two strong candidates for
  a future module (tentatively "Systems and Implementation"): design
  tokens and design systems, both directly relevant since Wireframe's own
  theme is a token system. Most of the 24 reviewed URLs were logged out of
  scope (business strategy, team process, AI tooling and workflows, and
  education-sector tooling topics), each with its reason recorded so it is
  not re-litigated on a future pass.
- A new non-goal in PRD.md section 4: Wireframe does not teach UX research
  methodology or business/product strategy, a boundary that came directly
  out of comparing the curriculum against the Interaction Design
  Foundation's beginner UX course, which is research-and-strategy-focused
  where Wireframe is visual-and-interaction-execution-focused.

**Changed**
- PRD.md's roadmap milestone table: M2.9 marked Complete, M3 marked
  "Planned, next up." The "Current phase" summary updated accordingly.

**Fixed**
- None.

**Removed**
- Nothing.

**Status**
- Phase 1 (Education): in progress. M0 through M2.9 complete. M3 (concept
  pages, markdown mirrors, `concepts-index.js`) planned next, informed by
  section 12.5's validation record and the M3 authoring requirements it
  logged.
- Phase 2 (Templates): not started, blocked by Phase 1.

---

## v0.3.1, 2026-07-26

Favicon added, with a deliberate, narrow exception to the inline-SVG-only
icon rule.

**Added**
- `<link rel="icon" type="image/png" href="favicon.png">` (path adjusted
  for folder depth) on all 9 existing pages: root `index.html`,
  `education/index.html`, and all 7 module index pages.
- A named exception in PRD.md section 9 (Constraints) and DESIGN.md section
  7 (Icons): `favicon.png` at the project root is the single raster image
  file permitted in this project. The exception is scoped to the favicon
  only; every other icon, callout, sidebar control, and future template
  preview stays inline SVG, for the reasons already documented (theme color
  inheritance via `currentColor`, plain-text diffability, zero binary
  assets). The favicon does not follow theme revisions automatically and
  must be manually rechecked against the palette if the theme changes.

**Changed**
- `assets/svg/icon-reference.md`'s Favicon section rewritten to point to
  `favicon.png` and the relative-path pattern, replacing an initial
  inline-SVG data URI favicon design that was implemented first, then
  superseded by this exception once the maintainer confirmed the intent
  to use their own supplied artwork instead.

**Fixed**
- None.

**Removed**
- The inline SVG data URI favicon that had briefly been added to 6 pages
  before this version; replaced by the `favicon.png` link on all 9 pages.

**Status**
- Phase 1 (Education): unchanged, in progress at M2 complete.
- Phase 2 (Templates): not started, blocked by Phase 1.

---

## v0.3.0, 2026-07-26

First implementation pass: milestones M0 through M2 from PRD.md's roadmap.
Concept pages (M3) still do not exist; every concept link created in this
version correctly points to a file that has not been written yet, per the
naming contract in PRD.md section 12.3.

**Added**
- `assets/css/theme.css`: the exact design token block from DESIGN.md
  section 3, implemented as written.
- `assets/css/base.css`: resets, base typography, link and heading
  defaults, the shared `:focus-visible` ring, and the skip-link component.
- `assets/css/components.css`: sidebar, sidebar group toggle, mobile nav
  toggle button, content area, code block, callout, button (all three
  variants), table, and difficulty pill, per DESIGN.md section 4. The
  demo container, interactive control, card, and template showcase card
  specs are intentionally not yet implemented, since nothing in Phase 1's
  current build needs them.
- `assets/css/wiki-layout.css`: the two-column wiki grid with
  `minmax(0, 1fr)` on the content track, and the mobile and tablet
  breakpoint override that collapses the sidebar behind the toggle button,
  per DESIGN.md section 5.1 and section 8's grid track guidance.
- `assets/svg/icon-reference.md`: copy-paste inline SVG snippets for the
  menu, chevron, note, and warning icons used by the navigation shell and
  callouts.
- `assets/js/nav-data.js`: `window.WIREFRAME_NAV`, the full 7-module,
  13-concept structure from PRD.md section 12.1, as plain data.
- `assets/js/nav.js`: renders the sidebar from `nav-data.js` into any
  page's `#sidebar-nav` container, marks the active link and auto-expands
  its module group using two page-level globals each page sets before
  loading it (`WIREFRAME_BASE_PATH`, `WIREFRAME_CURRENT_PAGE`), and wires
  up the mobile nav toggle and the collapsible module groups.
- `index.html` (root), `education/index.html`, and one `index.html` per
  module folder (`01-foundations` through `07-critique`), all built on the
  navigation shell above.
- A new roadmap milestone, M2.9, in PRD.md section 14, plus a new PRD.md
  section 12.5 ("Curriculum research and validation") and 12.5.1 (the fixed
  research source list: the Figma resource library, Nielsen Norman Group,
  dailyui.co, ux.stackexchange.com, and the Interaction Design Foundation's
  beginner UX course). M2.9 is scheduled after the navigation shell and
  before the first concept page is written, so the 13-concept curriculum in
  section 12.2 gets checked against external UI/UX educational sources
  once, up front, rather than patched piecemeal while writing M3.

**Changed**
- PRD.md's roadmap milestone table: M1 and M2 marked Complete; the
  "Current phase" summary updated to describe the actual state of the
  build rather than the pre-implementation state.
- README.md's Phase order and current status table and current version,
  updated to reflect the M0 to M2 build.

**Fixed**
- None; this version only adds new files.

**Removed**
- Nothing.

**Status**
- Phase 1 (Education): in progress. M0, M1, and M2 complete. M2.9
  (curriculum research) and M3 (concept pages, markdown mirrors,
  `concepts-index.js`) planned next, in that order.
- Phase 2 (Templates): not started, blocked by Phase 1.

---

## v0.2.0, 2026-07-26

Documentation audit and consolidation pass. No HTML, CSS, or JavaScript has
been written yet; this version only restructures and expands the
documentation itself.

**Added**
- `/docs/` folder, holding `PRD.md`, `DESIGN.md`, and `PATCHNOTES.md`.
  `README.md` now lives exclusively at the project root; this folder
  structure is enforced going forward, per PRD.md section 21.
- A Writing Style section in PRD.md (section 6) documenting the project's
  em dash and double dash prohibition: the literal Unicode em dash
  character, the `&mdash;` HTML entity, and punctuation double dashes are
  all prohibited, searched for independently since a search for one form
  will not catch the others, with CSS custom property syntax (for example
  `--color-accent`) explicitly exempted. Includes the comma, colon,
  semicolon, parentheses, and period replacement methodology and the audit
  cadence for when this check runs.
- A Responsive QA Methodology section in DESIGN.md (section 8): the full
  breakpoint list to test (375px, 700px, 900px, 1023px, 1150px, 1440px,
  1920px), the four common CSS bug patterns to check for (the `overflow`
  shorthand resetting an explicit `overflow-x`/`overflow-y`, implicit
  `min-width: auto` on bare `1fr` grid tracks, default `min-width`/`min-
  height: auto` on flex children, and doubled spacing from `gap` plus
  child `margin`), the `scrollWidth`/`clientWidth` verification method in
  place of relying on screenshots, and the rule that genuine presentation
  tradeoffs are confirmed with the maintainer before implementation while
  pure CSS correctness fixes are not.
- A Design Philosophy section in DESIGN.md (section 1) and an Additional
  Notes for AI Models section in DESIGN.md (section 9).
- Full expansion of PRD.md to the complete required section set: Problem
  statement, Target users, Tenets, User stories, Feature list (MVP and
  Future), Constraints, Assumptions, Success criteria, Roadmap (milestone
  table and deferred items), Metrics, Runbook (including a common errors
  table), Technical Requirements (including the `nav-data.js` data model
  shape, which had not previously been documented), Security, Press
  Release, Frequently Asked Questions, and a Documentation and Audit
  Process section describing how the writing style, responsive QA, and
  documentation accuracy audits recur going forward.

**Changed**
- Rewrote README.md to a developer-facing contract: tech stack table,
  prerequisites, exact installation steps, how to run locally, an explicit
  environment variable reference (none), and build and deploy instructions
  (none), with all marketing language removed.
- Renumbered every section in DESIGN.md (now 1 through 10) to make room for
  the new Design Philosophy, Responsive QA Methodology, and AI Models
  sections, and updated every cross-reference in PRD.md that pointed to a
  DESIGN.md section number to match.
- Reworded the five template entries in PRD.md section 13.2 from an em
  dash separated header (`**Name** — folder: \`slug\``) to a parenthetical
  form (`**Name** (folder: \`slug\`)`) as part of the writing style fix
  below.

**Fixed**
- Audited every markdown file in the project for the literal em dash
  character and the `&mdash;` entity, searched independently. Found five
  instances, all in PRD.md's template list (now section 13.2), all using
  an em dash as a label separator (`**Landing Page** — folder:
  \`landing-page\``). Replaced each with parentheses, since the dash was
  introducing supplementary information rather than a full clause.
  Audited separately for punctuation double dashes; none were found. CSS
  custom property declarations (`--color-accent`, `--space-4`, and similar,
  throughout DESIGN.md) were confirmed as valid CSS syntax and left
  untouched, per the exemption now documented in PRD.md section 6.

**Removed**
- Nothing. No prior content was deleted; this version reorganizes and
  expands existing documentation without dropping any previously
  documented decision.

**Status**
- Phase 1 (Education): not started, documentation only.
- Phase 2 (Templates): not started, blocked by Phase 1.

---

## v0.1.0, 2026-07-26

Documentation scaffold. No HTML, CSS, or JavaScript has been written yet.

**Added**
- README.md: project overview, audience, how to open in Chrome, full
  directory tree, and phase status.
- PRD.md: goals, non goals, target user, the complete Phase 1 concept
  curriculum across seven modules, the AI queryability contract (heading
  hierarchy, anchor convention, machine readable index format, markdown
  mirror requirement), the five starter templates and what each
  demonstrates, the template folder and registry contract, and acceptance
  criteria for both phases.
- DESIGN.md: full design token table (color, type scale, spacing, radius,
  shadow, transition), the exact reusable CSS custom property block,
  component specs for sidebar, content area, code block, callout, demo
  container, interactive control, card, button, table, and template
  showcase card, layout rules for the wiki article and portfolio grid
  layouts, breakpoints, accessibility requirements, and a plan for
  revisiting the theme after Phase 1.
- PATCHNOTES.md: this file.

**Decisions locked in this version**
- Concepts are one HTML file per concept, grouped into numbered module
  folders, with a matching markdown mirror per concept.
- Sidebar navigation renders at runtime from a shared `nav-data.js` global
  object rather than duplicated markup per page.
- Slugs are kebab-case only, reused identically as the concept ID, the file
  name, the anchor ID, and the index key.
- Five starter templates proposed: Landing Page, Portfolio Site, Blog and
  Article Site, Documentation Site, and Small Business and Local Service
  Site.
- Template discovery uses an additive registry file
  (`templates-registry.js`) so the showcase page never hardcodes a template
  count.

**Status**
- Phase 1 (Education): not started, documentation only.
- Phase 2 (Templates): not started, blocked by Phase 1.
