Canonical GGUF naming and redirect migration

Defines GGUF as the only project identifier, corrects managed database content and menu URLs, and preserves two retired public routes with permanent redirects.

Research
Last verified
Not verified
Updated
Reading time
1 minutes

Defines GGUF as the only project identifier, corrects managed database content and menu URLs, and preserves two retired public routes with permanent redirects.

Canonical identifier

GGUF is the only accepted spelling for the project, domain, content, metadata, package memory, and public routes.

Upgrade behavior

MiRust Core 1.5.0 corrects the retired misspelling in starter-managed titles, slugs, excerpts, content, and custom menu URLs. The migration is version-gated and preserves owner-authored content outside the managed records.

Route continuity

Two previously generated public routes are migrated to canonical slugs. Requests to the retired routes receive permanent redirects so bookmarks and indexed links retain continuity without keeping duplicate content.

Verification

Release validation scans source, generated starter data, WXR, UAI exports, project documentation, and archives to ensure the retired literal spelling is absent.

Scope

This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.

Engineering considerations

  • Identify the source, version, target environment, and owner.
  • Separate observed values from estimates and externally reported values.
  • Record trade-offs, unsupported cases, and fallback behavior.
  • Link performance statements to a compatible benchmark methodology.

Verification questions

  • What exact artifact, revision, backend, and environment were reviewed?
  • Which assumptions could change the result?
  • Which data should be retained so another engineer can reproduce the conclusion?