Skip to content

Fail fast in validate-content-rules for missing files and malformed month/year headings #64

@VatsalSy

Description

@VatsalSy

Why

Content validation has been strengthened, but review feedback shows remaining failure modes should be explicit and deterministic.

Evidence

Scope

  • Add a reusable file-existence guard for all files referenced by scripts/validate-content-rules.sh.
  • In history parsing, treat unknown month names as validation failures.
  • Reject month headings that appear before any year context.
  • Improve error messages to include offending heading/context.

Acceptance Criteria

  • Missing required files produce clear "file not found" messages and non-zero exit.
  • Invalid month names and out-of-context month headings fail validation.
  • Existing valid history.md ordering passes unchanged.
  • Script output is specific enough to fix failures without manual debugging.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions