# Hotfix10 Template Migration Audit

## Authoritative storage

The template source of truth remains filesystem-first:

- `texise-templates/free/<slug>/`
- `texise-templates/pro/<slug>/`

Each directory carries its own `template.json`. The parent folder is authoritative for Free/Pro access. Assets Sync reconstructs public catalog data from this filesystem, so operators can still bulk-copy template directories by SSH and rescan them without database registration.

## Current source-corpus limitation

The supplied Hotfix9 source archive contains **8 template directories**: 5 Free and 3 Pro. The earlier live/search audit found a substantially larger legacy `/latex-templates` surface (approximately 60 items). Those absent template source files cannot be reconstructed safely or honestly from metadata/search results.

**Deployment requirement:** recover/supply the historical template corpus before treating the migration as complete. Do not redirect missing legacy templates to unrelated generic pages and do not fabricate their contents.

## URL migration

- Collection: `/latex-templates` -> `301 /templates`
- Same-slug details: `/latex-templates/{slug}` -> `301 /templates/{slug}`
- Renamed slugs: persist explicit old->new mappings in `texise-templates/redirects.json`.
- Canonical individual URL: `/templates/{slug}`.
- Institution/category/country pages are collection views and do not create duplicate template canonicals.

## Filesystem migration acceptance

A valid directory copied into `free/` or `pro/` must appear after Assets Sync. Tier changes from Admin physically move the directory without changing the public canonical slug. Metadata edits write back to `template.json` so the library remains portable.