During authorized publication of all pending main commits, Planning Docs validation failed on pushed commit 975b7c6c514fe036c5796071d35669e64f68d6ea.
Run: https://github.com/DataTalksClub/dataops/actions/runs/34060237649
On-Call findings: the Node SOP lint step exits 2 with 90 violations across 15 SOPs. Each reports six missing required sections: summary, prerequisites, procedure, validation, troubleshooting, references. The private knowledge checkout and content-validation workflow itself succeeded; this is a document/schema validation failure, not an established credential problem. Similar failure existed on earlier main.
Diagnose whether the validator misreads canonical structured documents or the private knowledge lacks required material. Preserve actual checks; do not suppress errors or invent operational content. Keep operational document names, contents, links, and artifacts out of the public issue. Application/runtime fixes belong here; any private knowledge change requires an explicit, separately scoped authorization decision if not already covered.
The current app deployment and full browser CI are monitored separately. This issue does not claim those jobs failed or completed.
During authorized publication of all pending main commits, Planning Docs validation failed on pushed commit
975b7c6c514fe036c5796071d35669e64f68d6ea.Run: https://github.com/DataTalksClub/dataops/actions/runs/34060237649
On-Call findings: the Node SOP lint step exits 2 with 90 violations across 15 SOPs. Each reports six missing required sections: summary, prerequisites, procedure, validation, troubleshooting, references. The private knowledge checkout and content-validation workflow itself succeeded; this is a document/schema validation failure, not an established credential problem. Similar failure existed on earlier main.
Diagnose whether the validator misreads canonical structured documents or the private knowledge lacks required material. Preserve actual checks; do not suppress errors or invent operational content. Keep operational document names, contents, links, and artifacts out of the public issue. Application/runtime fixes belong here; any private knowledge change requires an explicit, separately scoped authorization decision if not already covered.
The current app deployment and full browser CI are monitored separately. This issue does not claim those jobs failed or completed.