test(kb): add valid test file for workflow validation
All checks were successful
KB Lint / validate (push) Successful in 3s

- Create kb/01_projects/test/2025-11-11--runner-test--note.md
- Include all 18 required frontmatter fields
- Proper filename pattern, date, and type matching
- routing_confidence: 0.95 (valid, not in review queue)
- Test workflow fix for git revision error
- Verify KB lint workflow executes correctly
This commit is contained in:
Gitea Actions
2025-11-11 14:54:47 -07:00
parent 1423ee1f04
commit 98575c186c

View File

@@ -0,0 +1,77 @@
---
title: "Runner Test - KB Workflow Validation"
date: "2025-11-11"
captured_at: "2025-11-11"
author: ["Test User"]
source: { kind: chat, ref: "runner-test-workflow-validation" }
source_type: chat
project: ["tendril"]
related_projects: ["tendril"]
topics: ["testing", "workflows", "kb-system", "gitea-actions"]
tags: ["test", "workflow", "validation", "runner", "gitea-actions"]
type: note
status: draft
phase_relevance: ["phase-05"]
routing_hint: "Test file for Gitea Actions runner and workflow validation - will be deleted after testing"
proposed_path: "kb/01_projects/test/"
routing_confidence: 0.95
related: []
summary: "Test KB file created to validate Gitea Actions runner setup and KB lint workflow functionality. This file will be deleted after successful workflow validation."
key_takeaways: []
action_candidates: []
---
# Runner Test - KB Workflow Validation
This is a test file created to validate that the Gitea Actions runner setup and KB lint workflow (`kb-lint.yml`) are working correctly on the current branch.
## Purpose
- Test KB file naming validation
- Test frontmatter validation with all required fields
- Test workflow triggers on push events
- Verify workflow provides clear validation results
- Test that the git revision error fix is working
## Expected Behavior
When this file is committed and pushed to the current branch:
1. KB lint workflow should trigger (because `kb/**/*.md` changed)
2. Workflow should validate the file without git revision errors
3. Workflow should pass (file follows all rules)
4. No `fatal: bad revision 'HEAD~1...HEAD'` error should appear
## File Details
- **Filename**: `2025-11-11--runner-test--note.md`
- **Type**: note
- **Date**: 2025-11-11
- **Location**: `kb/01_projects/test/`
- **Routing Confidence**: 0.95 (high confidence, not in review queue)
## Validation Rules Tested
✅ Filename pattern: `YYYY-MM-DD--slug--type.md`
✅ Frontmatter exists and is valid YAML
✅ All 18 required fields present:
- title, date, captured_at, author, source, source_type
- project, related_projects, topics, tags
- type, status, phase_relevance
- routing_hint, proposed_path, routing_confidence
- related, summary, key_takeaways, action_candidates
✅ Date in frontmatter matches filename date (2025-11-11)
✅ Type in frontmatter matches filename type (note)
✅ routing_confidence is numeric 0.00-1.00 (0.95)
✅ routing_confidence >= 0.60 (not in _review_queue/)
## Workflow Fix Validation
This file also tests that the workflow fix for the git revision error is working:
- Uses `github.event.before` and `github.event.after` instead of `HEAD~1...HEAD`
- Should work correctly with shallow clones
- Should not produce `fatal: bad revision` errors
---
**Note**: This file will be deleted after workflow validation is confirmed successful.