5 Commits

Include renames

Author	SHA1	Message	Date
john-okeefe	65d3525d80	feat: Add documentation completeness validation ... Check 16: Documentation Completeness Validation - Detect orphaned documentation (files without proper markdown structure) - Check for inconsistent file naming patterns in docs/api/ - Validate markdown formatting compliance - Ensure documentation maintains structural integrity This final check completes the comprehensive documentation validation suite, ensuring all documentation files follow proper formatting and naming conventions per PROJECT_GUIDELINES.md standards.	2026-02-02 11:34:51 -05:00
john-okeefe	8d31298861	feat: Add Bruno API tests and recent changes validation ... Check 14: Bruno API Tests Validation - Count and verify Bruno .bru test files presence - Compare API documentation vs Bruno test coverage - Flag insufficient test coverage for human review Check 15: Recent Documentation Changes Analysis - Analyze recent commits for documentation compliance - Flag code commits without corresponding documentation updates - Verify proper commit message format (docs: prefix) - Ensure documentation stays synchronized with code changes These checks provide comprehensive validation of API testing coverage and ensure documentation follows proper git commit conventions per PROJECT_GUIDELINES.md requirements.	2026-02-02 11:32:21 -05:00
john-okeefe	5deef46ef5	feat: Add high-recall documentation content and structure validation ... Check 12: Documentation Content Placement - Detect API patterns in README.md when docs/api/ exists - Flag device setup content outside docs/devices/ - Identify development content outside docs/contributing/ - Monitor README.md length (>300 lines triggers warning) Check 13: Documentation Structure Validation - Verify required directories exist (docs/api, docs/devices, docs/contributing) - Count and report API documentation files - Validate device setup guides presence These checks implement high-recall pattern detection to catch potential documentation guideline violations for human review, ensuring content is properly routed according to PROJECT_GUIDELINES.md decision table.	2026-02-02 11:30:55 -05:00
john-okeefe	3af4f3ea91	feat: Add AI behavior protocol to verification script ... - Add comprehensive AI instructions at script start and end - Enhance error/warning functions with AI reminders - Multi-layered safeguards prevent automatic fixing - Clear protocol: explain -> propose -> ask permission -> await response - Instructions apply to ALL file modifications, not just verification issues These safeguards ensure AI always asks permission before fixing any issues found by the verification script, preventing automatic corrections of potential false positives.	2026-02-02 11:30:00 -05:00
john-okeefe	e0b95ba297	Add project guidelines verification script ... Created comprehensive verification script to check codebase against PROJECT_GUIDELINES.md Features: - Checks for custom CSS (TailwindCSS requirement) - Detects JavaScript files that should be TypeScript - Verifies no secrets committed (.env, credentials.json) - Validates code compiles (go build) - Finds local binaries (should use container builds) - Quick checks with clear pass/fail/warning output Usage: make verify-guidelines ./scripts/verify-quick.sh Current codebase status: - 12 templates with custom CSS (need Tailwind conversion) - 2 .js files in web/static/ (need TypeScript conversion) - 1 binary file (./bookhoard) This addresses the trust issue: AI now has a tool to prove guideline compliance	2026-02-02 09:55:39 -05:00