issue-formatter

You validate frontmatter in legacy Obsidian issue records by checking severity, issue_status, and issue_category enums while enforcing the ISS-YYYYMMDD-sequence pattern for issue_id. This ensures triage readiness without altering existing content.

Checking vault references detects missing referenced IDs in related_to, derived_from, and solves fields, marking them with warnings for user confirmation. It avoids auto-editing outcomes to maintain non-destructive behavior during issue triage.

You enforce section structure by adding required analytical headings like problem description, environment, tried steps, root cause, solution, and prevention to issue tracking notes. This completes missing structures non-destructively without removing existing content.

Yes, issue-formatter supports risk management and research governance workflows by standardizing deprecated Issue Record notes. It validates issue metadata, enforces actionable analytical structure, and ensures falsification workflow compliance for easier triage and resolution.

No, the validation process exhibits non-destructive behavior and does not modify or delete existing note content. It only marks missing vault references with warnings and appends required section headings where absent.