Align PM skills, schemas, templates, and examples

[simaba]

Problem

The second sweep found a concrete contract failure:

• the repository contained two incompatible RAID schema definitions;
• pmkit validated one contract while the RAID skill and older tests used another;
• the rewritten RAID examples used field names accepted by neither validator contract;
• the decision-memo skill, template, examples, and legacy tests used incompatible frontmatter names;
• JSON Schema date formats were declared but not enforced because the validator had no FormatChecker.

Changes

• establishes schemas/raid-row.schema.json as the canonical RAID contract
• retains schemas/raid-row.json as an identical legacy-path compatibility copy instead of a second model
• adds conditional fields for risks, assumptions, issues, dependencies, and closed/transferred records
• checks score == probability × impact for risk records
• aligns RAID and decision-memo skills, templates, examples, and all old/new tests
• adds decision-state rules for draft, in-review, decided, deferred, and superseded memos
• enables JSON Schema date-format validation
• supports CRLF frontmatter files
• publishes short-lived JUnit reports from the CI matrix for diagnosable failures

Verification

The final branch passed CI on Python 3.10, 3.11, and 3.12. Schema validity still confirms only shape and selected cross-field semantics; it does not prove that the underlying PM judgment or evidence is sound.

[simaba]

Problem

The second sweep found a concrete contract failure:

• the repository contained two incompatible RAID schema definitions;
• pmkit validated one contract while the RAID skill and older tests used another;
• the rewritten RAID examples used field names accepted by neither validator contract;
• the decision-memo skill, template, examples, and legacy tests used incompatible frontmatter names;
• JSON Schema date formats were declared but not enforced because the validator had no FormatChecker.

Changes

• establishes schemas/raid-row.schema.json as the canonical RAID contract
• retains schemas/raid-row.json as an identical legacy-path compatibility copy instead of a second model
• adds conditional fields for risks, assumptions, issues, dependencies, and closed/transferred records
• checks score == probability × impact for risk records
• aligns RAID and decision-memo skills, templates, examples, and all old/new tests
• adds decision-state rules for draft, in-review, decided, deferred, and superseded memos
• enables JSON Schema date-format validation
• supports CRLF frontmatter files
• publishes short-lived JUnit reports from the CI matrix for diagnosable failures

Verification

The final branch passed CI on Python 3.10, 3.11, and 3.12. Schema validity still confirms only shape and selected cross-field semantics; it does not prove that the underlying PM judgment or evidence is sound.

[simaba]

Problem

The second sweep found a concrete contract failure:

• the repository contained two incompatible RAID schema definitions;
• pmkit validated one contract while the RAID skill and older tests used another;
• the rewritten RAID examples used field names accepted by neither validator contract;
• the decision-memo skill, template, examples, and legacy tests used incompatible frontmatter names;
• JSON Schema date formats were declared but not enforced because the validator had no FormatChecker.

Changes

• establishes schemas/raid-row.schema.json as the canonical RAID contract
• retains schemas/raid-row.json as an identical legacy-path compatibility copy instead of a second model
• adds conditional fields for risks, assumptions, issues, dependencies, and closed/transferred records
• checks score == probability × impact for risk records
• aligns RAID and decision-memo skills, templates, examples, and all old/new tests
• adds decision-state rules for draft, in-review, decided, deferred, and superseded memos
• enables JSON Schema date-format validation
• supports CRLF frontmatter files
• publishes short-lived JUnit reports from the CI matrix for diagnosable failures

Verification

The final branch passed CI on Python 3.10, 3.11, and 3.12. Schema validity still confirms only shape and selected cross-field semantics; it does not prove that the underlying PM judgment or evidence is sound.

[simaba]

Problem

The second sweep found a concrete contract failure:

• the repository contained two incompatible RAID schema definitions;
• pmkit validated one contract while the RAID skill and older tests used another;
• the rewritten RAID examples used field names accepted by neither validator contract;
• the decision-memo skill, template, examples, and legacy tests used incompatible frontmatter names;
• JSON Schema date formats were declared but not enforced because the validator had no FormatChecker.

Changes

• establishes schemas/raid-row.schema.json as the canonical RAID contract
• retains schemas/raid-row.json as an identical legacy-path compatibility copy instead of a second model
• adds conditional fields for risks, assumptions, issues, dependencies, and closed/transferred records
• checks score == probability × impact for risk records
• aligns RAID and decision-memo skills, templates, examples, and all old/new tests
• adds decision-state rules for draft, in-review, decided, deferred, and superseded memos
• enables JSON Schema date-format validation
• supports CRLF frontmatter files
• publishes short-lived JUnit reports from the CI matrix for diagnosable failures

Verification

The final branch passed CI on Python 3.10, 3.11, and 3.12. Schema validity still confirms only shape and selected cross-field semantics; it does not prove that the underlying PM judgment or evidence is sound.

[simaba]

Problem

The second sweep found a concrete contract failure:

• the repository contained two incompatible RAID schema definitions;
• pmkit validated one contract while the RAID skill and older tests used another;
• the rewritten RAID examples used field names accepted by neither validator contract;
• the decision-memo skill, template, examples, and legacy tests used incompatible frontmatter names;
• JSON Schema date formats were declared but not enforced because the validator had no FormatChecker.

Changes

• establishes schemas/raid-row.schema.json as the canonical RAID contract
• retains schemas/raid-row.json as an identical legacy-path compatibility copy instead of a second model
• adds conditional fields for risks, assumptions, issues, dependencies, and closed/transferred records
• checks score == probability × impact for risk records
• aligns RAID and decision-memo skills, templates, examples, and all old/new tests
• adds decision-state rules for draft, in-review, decided, deferred, and superseded memos
• enables JSON Schema date-format validation
• supports CRLF frontmatter files
• publishes short-lived JUnit reports from the CI matrix for diagnosable failures

Verification

The final branch passed CI on Python 3.10, 3.11, and 3.12. Schema validity still confirms only shape and selected cross-field semantics; it does not prove that the underlying PM judgment or evidence is sound.

[simaba]

Problem

The second sweep found a concrete contract failure:

• the repository contained two incompatible RAID schema definitions;
• pmkit validated one contract while the RAID skill and older tests used another;
• the rewritten RAID examples used field names accepted by neither validator contract;
• the decision-memo skill, template, examples, and legacy tests used incompatible frontmatter names;
• JSON Schema date formats were declared but not enforced because the validator had no FormatChecker.

Changes

• establishes schemas/raid-row.schema.json as the canonical RAID contract
• retains schemas/raid-row.json as an identical legacy-path compatibility copy instead of a second model
• adds conditional fields for risks, assumptions, issues, dependencies, and closed/transferred records
• checks score == probability × impact for risk records
• aligns RAID and decision-memo skills, templates, examples, and all old/new tests
• adds decision-state rules for draft, in-review, decided, deferred, and superseded memos
• enables JSON Schema date-format validation
• supports CRLF frontmatter files
• publishes short-lived JUnit reports from the CI matrix for diagnosable failures

Verification

The final branch passed CI on Python 3.10, 3.11, and 3.12. Schema validity still confirms only shape and selected cross-field semantics; it does not prove that the underlying PM judgment or evidence is sound.

[simaba]

Problem

The second sweep found a concrete contract failure:

• the repository contained two incompatible RAID schema definitions;
• pmkit validated one contract while the RAID skill and older tests used another;
• the rewritten RAID examples used field names accepted by neither validator contract;
• the decision-memo skill, template, examples, and legacy tests used incompatible frontmatter names;
• JSON Schema date formats were declared but not enforced because the validator had no FormatChecker.

Changes

• establishes schemas/raid-row.schema.json as the canonical RAID contract
• retains schemas/raid-row.json as an identical legacy-path compatibility copy instead of a second model
• adds conditional fields for risks, assumptions, issues, dependencies, and closed/transferred records
• checks score == probability × impact for risk records
• aligns RAID and decision-memo skills, templates, examples, and all old/new tests
• adds decision-state rules for draft, in-review, decided, deferred, and superseded memos
• enables JSON Schema date-format validation
• supports CRLF frontmatter files
• publishes short-lived JUnit reports from the CI matrix for diagnosable failures

Verification

The final branch passed CI on Python 3.10, 3.11, and 3.12. Schema validity still confirms only shape and selected cross-field semantics; it does not prove that the underlying PM judgment or evidence is sound.

[simaba]

Problem

The second sweep found a concrete contract failure:

• the repository contained two incompatible RAID schema definitions;
• pmkit validated one contract while the RAID skill and older tests used another;
• the rewritten RAID examples used field names accepted by neither validator contract;
• the decision-memo skill, template, examples, and legacy tests used incompatible frontmatter names;
• JSON Schema date formats were declared but not enforced because the validator had no FormatChecker.

Changes

• establishes schemas/raid-row.schema.json as the canonical RAID contract
• retains schemas/raid-row.json as an identical legacy-path compatibility copy instead of a second model
• adds conditional fields for risks, assumptions, issues, dependencies, and closed/transferred records
• checks score == probability × impact for risk records
• aligns RAID and decision-memo skills, templates, examples, and all old/new tests
• adds decision-state rules for draft, in-review, decided, deferred, and superseded memos
• enables JSON Schema date-format validation
• supports CRLF frontmatter files
• publishes short-lived JUnit reports from the CI matrix for diagnosable failures

Verification

The final branch passed CI on Python 3.10, 3.11, and 3.12. Schema validity still confirms only shape and selected cross-field semantics; it does not prove that the underlying PM judgment or evidence is sound.