S009 Success Criteria
| ID | Criterion |
|---|---|
| S009-SC-001 | All VitePress navigation links resolve without dead link warnings during build |
| S009-SC-002 | All code blocks have language identifiers and render syntax highlighting correctly |
| S009-SC-003 | The sidebar displays all 10 guides in the correct four-section grouping |
| S009-SC-004 | The mobile navigation collapses and expands sections correctly |
| S009-SC-005 | Dark mode styling applies the custom green brand colors correctly in both modes |
| S009-SC-006 | The parity init command output shown in getting-started.md matches the actual command output |
| S009-SC-007 | All 9 configuration keys in the settings block of configuration.md match the schema |
| S009-SC-008 | All 5 rule names in rules.md match the rule names registered in the Parity rule registry |
| S009-SC-009 | The GitHub Actions workflow example in ci-integration.md uses correct --coverage-clover syntax |
| S009-SC-010 | The RuleInterface method table in plugins.md lists all 7 methods with correct signatures |
| S009-SC-011 | Every guide file begins with valid YAML frontmatter (--- delimiters, title, description) |
| S009-SC-012 | VitePress build completes with exit code 0 and produces a dist/ directory containing all guide HTML files |