Skip to content

Decide: load-time fontinfo-remainder validation should degrade, not brick resume #131

Description

@kostyafarber

From the adversarial review of #130. validate_loaded_font (called from FontWorkspace::open_package and ::resume) hard-fails on an invalid fontinfo remainder. Pre-#130 the same corruption meant open-fine/save-fails; now a working draft store holding unsaved edits becomes permanently inaccessible — there is no degrade path.

No non-tampering trigger exists today, but norad version skew across shift builds (a key's value shape changing between norad releases) is a plausible future trigger with no migration story. Also inconsistent: import_font skips validate_loaded_font entirely.

Decision needed: on invalid remainder at open/resume, drop the remainder with a visible warning (preserves access to the user's edits, loses only passthrough data) vs. keep the hard error. Recommendation: degrade with warning at resume (unsaved work must never be held hostage by passthrough bytes); hard error is defensible at open_package only.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions