1423ee1f04b7f386dc70045d13e3374754b89154
7
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 Gitea Actions
|
1423ee1f04 |
fix(workflows): resolve git revision error in KB lint workflow
- Fix HEAD~1...HEAD error for shallow clones by using github.event.before/after - Add proper error suppression with 2>/dev/null - Add fallback logic for edge cases (initial commits, force pushes) - Archive resolved runner setup issue to docs/issues/archive/resolved/ - Add archive documentation and next steps guide Fixes workflow execution on test/runner-validation branch. Resolves issue with 'fatal: bad revision' error in logs. |
||
|
Gitea Actions
|
72d74f86ad |
test(phase-5): implement Phase 5 validation and testing
KB Lint / validate (push) Successful in 3s
Completed comprehensive validation and testing of all system components as part of Phase 5: Validation and Testing. ## What Was Tested ### Test 1: Cursor Rules ✅ - Verified rules file exists and is properly structured - Confirmed all required sections present - Validated phase documentation synchronization rules ### Test 2: KB System ✅ - Verified KB directory structure complete - Confirmed all three templates exist with complete frontmatter - Tested index generation script (works correctly) - Created test KB file and verified indexing - Tested changelog update process ### Test 3: Phase Documentation ✅ - Verified phase structure - Tested blueprint modification synchronization - Confirmed changelog updates automatically per Cursor rules ### Test 4: Gitea Actions Workflows ⏸️ - Verified workflow files exist and syntax is valid - Validated workflow configuration (triggers, paths, permissions) - Workflow execution pending runner configuration - Runner setup request documented in docs/issues/ ### Test 5: LLM Prompts ✅ - Verified prompt files exist - Confirmed prompt structure follows documentation - Validated prompt content is complete ## Test Results **Total Tests**: 18 **Passed**: 17 **Pending**: 1 (requires runners) **Pass Rate**: 94.4% ## Files Created ### Phase 5 Documentation - - Phase blueprint - - Task tracking - - Change history - - ADRs - - Detailed test results - - Final validation report ### Test Artifacts - - Test KB file for validation ## Files Modified - - Added Phase 5 test file entry - - Regenerated with test file (9 files indexed) - - Version updated (1.0 → 1.1) for sync test - - Updated per synchronization rules ## Key Findings ✅ **All tested components working correctly**: - Cursor rules structure and content - KB system file creation and indexing - Phase documentation synchronization - Index generation script - KB changelog updates - LLM prompt file structure ⏸️ **Pending Runner Configuration**: - Gitea Actions workflow execution (requires runners) - KB lint workflow validation - KB index auto-update workflow ## Phase Status **Phase 5 Status**: ✅ Complete (with runner requirement noted) All components that can be tested without runners have been validated and are working correctly. Workflow execution tests will be completed once Gitea Actions runners are configured. ## Next Steps 1. Configure Gitea Actions runners (when available) 2. Complete workflow execution tests 3. Proceed to Phase 6: Customization and Final Verification |
||
|
Gitea Actions
|
5b8bf62130 |
docs(kb): migrate Gitea documentation to KB system
KB Lint / validate (push) Successful in 24s
Migrated all Gitea documentation from docs/GITEA/ folder into the Knowledge Base system, following KB naming conventions and frontmatter requirements. ## What Was Migrated ### Gitea Documentation Guides (6 KB entries) 1. **Gitea Basics Guide** () - Core concepts and features of Gitea - Key differences from GitHub - Terminology and common workflows - System requirements 2. **Gitea Actions Guide** () - Gitea Actions CI/CD system - Compatibility with GitHub Actions - Workflow creation and patterns - Troubleshooting guide 3. **LLM Guidelines for Gitea** () - Terminology guidelines for LLMs - Documentation standards - Common scenarios and checklist - Quick reference 4. **Gitea Workflows Guide** () - Common workflows (repository setup, branches, PRs, issues) - Best practices (branch naming, commits, PR process) - Integration with documentation systems - Troubleshooting 5. **Gitea API Reference** () - API authentication and endpoints - Differences from GitHub API - Common use cases - MCP server integration 6. **Gitea Documentation Overview** () - Overview and index of all Gitea documentation - Quick reference guide - Links to all Gitea KB entries ## KB System Compliance ✅ All files follow KB naming convention (YYYY-MM-DD--slug--type.md) ✅ All files have complete frontmatter (all 18 required fields) ✅ All files categorized in 02_systems/ (infrastructure/tooling) ✅ All files reference original documentation location ✅ KB changelog updated with migration entry ✅ KB index regenerated via script (8 files, 23 topics, 31 tags) ## Category Decision All Gitea documentation entries were placed in **02_systems/** category because: - Gitea is infrastructure/tooling (not project-specific) - Documentation covers platform usage and integration - Guides are system-level references - Fits KB category definition: "Infrastructure, DevOps, tooling" ## Original Documentation Original documentation remains in folder: - docs/GITEA/Gitea-Basics.md - docs/GITEA/Gitea-Actions-Guide.md - docs/GITEA/LLM-Gitea-Guidelines.md - docs/GITEA/Gitea-Workflows.md - docs/GITEA/Gitea-API-Reference.md - docs/GITEA/README.md KB entries reference original locations for full documentation. ## Benefits - Gitea documentation now searchable via KB index - Integrated with KB system for LLM discovery - Consistent with other KB entries - Maintains reference to original documentation - Provides comprehensive Gitea platform reference |
||
|
Gitea Actions
|
197f44b4d3 |
docs: add issues capture system and KB documentation
KB Lint / validate (push) Has been cancelled
This commit adds the issues capture system from PAIRS project and documents it in the KB system, following all KB system rules for changelog and index updates. ## What Was Added ### 1. Issues Capture System (docs/issues/) **docs/issues/README.md** - System documentation: - Purpose and workflow for quick issue capture - File naming convention (YYYY-MM-DD--short-description.md) - Issue types (bug, feature, insight, structural, improvement, question) - Template fields and best practices - Integration with Gitea platform - Future automation possibilities **docs/issues/template.md** - Issue file template: - Minimal required fields (title, type, date, status) - Optional fields (description, impact, notes, related) - Gitea issue tracking section - Simple, quick-capture format **docs/issues/2025-11-11--gitea-runner-setup-request.md** - Moved from .github/: - Gitea Actions runner configuration request - Updated to match issue template format - Includes type, date, status fields - Ready for compilation to Gitea issue ### 2. KB Documentation Entry **kb/02_systems/2025-11-11--issues-capture-system--note.md** - KB entry: - Documents the issues capture system structure and workflow - Explains quick capture process - Describes compilation to Gitea issues - Includes best practices and integration points - Properly categorized in 02_systems/ (infrastructure/tooling) - Complete frontmatter with all 18 required fields ### 3. KB System Updates **kb/CHANGELOG.md** - Updated: - Added entry for issues capture system documentation - Date: 2025-11-11 - Documents KB file addition **kb/_index.md** - Regenerated: - Index updated via generate-index.sh script - New KB file appears in 02_systems category - Topics indexed: documentation, issue-tracking, workflow, gitea - Tags indexed: issues, capture, documentation, gitea, workflow - Summary updated with file count ## Why This Implementation ### Quick Issue Capture The issues capture system provides a lightweight staging area for capturing issues, insights, bugs, and features as you encounter them. This enables quick capture without the overhead of creating formal Gitea issues immediately. ### Markdown-Based Workflow Issues are captured as markdown files, making them easy to edit, version control, and review. This provides flexibility before committing to formal issue tracking. ### Later Compilation Issues can be batch-processed into Gitea issues when ready, allowing for review, prioritization, and grouping before creating formal issues. ### Documentation in KB The issues capture system is documented in the KB system, making it discoverable and providing reference material for the workflow. ## Technical Details ### File Structure ### Issue File Format - **Naming**: - **Template**: Minimal fields for quick capture - **Status**: captured → reviewed → compiled - **Integration**: Links to Gitea issues when compiled ### KB Entry Details - **Category**: 02_systems (infrastructure, DevOps, tooling) - **Type**: note - **Topics**: documentation, issue-tracking, workflow, gitea - **Tags**: issues, capture, documentation, gitea, workflow - **Routing Confidence**: 0.95 (high confidence) ## Files Added/Modified ### Added - docs/issues/README.md - Issues capture system documentation - docs/issues/template.md - Issue file template - docs/issues/2025-11-11--gitea-runner-setup-request.md - Runner setup request (moved from .github/) - kb/02_systems/2025-11-11--issues-capture-system--note.md - KB documentation entry ### Modified - kb/CHANGELOG.md - Added entry for new KB file - kb/_index.md - Regenerated with new KB file indexed ## KB System Compliance ✅ KB file follows naming convention (YYYY-MM-DD--slug--type.md) ✅ KB file has complete frontmatter (all 18 required fields) ✅ KB file date matches filename date ✅ KB file type matches filename type ✅ KB changelog updated with entry ✅ KB index regenerated via script ✅ All changes committed together ## Related - Source: PAIRS-for-the-Individual project (docs/issues/) - KB System: kb/README.md - KB Changelog: kb/CHANGELOG.md - KB Index: kb/_index.md - Gitea Documentation: docs/GITEA/ |
||
|
Gitea Actions
|
6a4683022f |
docs(prompts): implement Phase 4 LLM Usage Guides Setup
This commit implements the complete LLM Usage Guides system for the Tendril project, establishing reusable prompt documents for AI-assisted workflows. ## What Was Implemented ### 1. Core Guide Documents **docs/PROMPTS/LLM-Usage-Guide.md** - Comprehensive LLM execution instructions: - Recognizing prompt documents (naming convention, structure, location) - Step-by-step execution process (5 phases: recognize, gather info, execute, handle errors, validate) - Information gathering requirements and best practices - Error handling procedures and common error patterns - Validation steps (pre-execution, during execution, post-execution) - Providing feedback (progress updates, error reporting, completion summaries) - Best practices for execution, communication, and quality - Special instructions for Tendril-specific context - Troubleshooting guide for common prompt execution issues - Customized for Tendril project structure and Gitea platform **docs/PROMPTS/Prompt-Creation-Guide.md** - Guide for creating effective prompts: - Naming convention (NN-Descriptive-Name-Prompt.md format) - Complete prompt structure template with all required sections - Best practices for writing effective instructions - Information gathering guidelines - Error handling documentation standards - Testing procedures for new prompts - Common patterns (status check, search, sync patterns) - Decision criteria for when to create new prompts - Update procedures for existing prompts - Comprehensive checklist for new prompts - Examples customized for Tendril project - References to Gitea-specific workflows and features ### 2. Initial Prompt Documents **docs/PROMPTS/00-Project-Status-Check-Prompt.md** - Project status overview: - Purpose: Check current status of all project phases - Reads all phase blueprints in tendril/phases/ - Extracts phase status, deliverables, milestones - Organizes by status (Complete, In Progress, Planned) - Provides comprehensive status summary with counts - Highlights issues or blockers - Error handling for missing files, invalid formats - Validation checklist for completion - Customized for Tendril phase structure **docs/PROMPTS/01-KB-Content-Search-Prompt.md** - KB system search: - Purpose: Search KB system for relevant content - Supports multiple search types: topics, tags, phase relevance, keywords - Uses kb/_index.md for efficient searching - Reads matching KB files and extracts metadata - Presents organized search results with summaries - Handles missing index, invalid criteria, empty results - Provides helpful suggestions for refining searches - Customized for Tendril KB structure and categories **docs/PROMPTS/02-Phase-Documentation-Sync-Prompt.md** - Phase documentation synchronization: - Purpose: Ensure phase documentation consistency - Reads all four phase documents (blueprint, tasks, decisions, changelog) - Compares and identifies discrepancies - Syncs tasks.md with blueprint deliverables and Definition of Done - Updates changelog.md with sync entry - Reviews decisions.md for missing ADRs - Verifies consistency across all documents - Follows Cursor rules for phase documentation synchronization - Error handling for missing files, format issues, unresolvable discrepancies - Customized for Tendril phase structure and documentation system ## Why This Implementation ### Standardized AI Workflows LLM Usage Guides enable consistent, repeatable AI-assisted workflows. Instead of explaining the same tasks repeatedly, prompts provide standardized instructions that work reliably every time. ### Reusability and Efficiency Prompt documents can be dragged into Cursor chat sessions and executed immediately. This saves time and ensures tasks are performed consistently across different sessions and users. ### Quality and Reliability Well-structured prompts include validation checklists, error handling, and best practices. This reduces errors and ensures high-quality results. ### Knowledge Preservation Prompts document how to perform complex tasks, preserving institutional knowledge and making it accessible to anyone who needs to perform the task. ### Integration with Project Systems Prompts are designed to work with Tendril's phase documentation system, KB system, and Gitea workflows, providing seamless integration with existing project infrastructure. ## Technical Details ### Prompt Document Structure All prompts follow a consistent structure: 1. **Title and Purpose** - Clear description of what the prompt does 2. **How to Use** - Instructions for using the prompt 3. **CRITICAL: Information Gathering** - Required information section 4. **Step-by-Step Process** - Phased execution instructions 5. **Error Handling** - Common issues and solutions 6. **Validation Checklist** - Completion verification 7. **Important Notes** - Critical instructions for AI assistant ### Naming Convention Prompts follow strict naming: - 00-09: Core system prompts - 10-19: Phase management prompts - 20-29: KB system prompts - 30-39: Workflow and automation prompts - 40-49: Documentation prompts - 50+: Project-specific prompts ### Customization for Tendril All prompts and guides are customized for: - **Project Name**: Tendril (not "pairs" or placeholders) - **Platform**: Gitea (not GitHub) - **Repository**: https://git.parkingmeter.info/Mycelium/tendril - **Directory Structure**: tendril/phases/, kb/ with category directories - **Workflows**: Gitea Actions (with GitHub Actions compatibility notes) ### Integration Points Prompts integrate with: - **Phase Documentation**: tendril/phases/phase-XX-name/ files - **KB System**: kb/ directory with index and category structure - **Workflows**: .github/workflows/ (Gitea Actions) - **Documentation**: docs/ directory structure ## Files Added - docs/PROMPTS/LLM-Usage-Guide.md - LLM execution instructions (~400 lines) - docs/PROMPTS/Prompt-Creation-Guide.md - Prompt creation guide (~600 lines) - docs/PROMPTS/00-Project-Status-Check-Prompt.md - Status check prompt (~180 lines) - docs/PROMPTS/01-KB-Content-Search-Prompt.md - KB search prompt (~240 lines) - docs/PROMPTS/02-Phase-Documentation-Sync-Prompt.md - Documentation sync prompt (~250 lines) **Total**: 5 files, ~1,670 lines of prompt documentation ## Validation All Phase 4 requirements met: - ✅ LLM Usage Guide created and comprehensive - ✅ Prompt Creation Guide created with complete template - ✅ Three initial prompt documents created - ✅ All prompts follow naming convention - ✅ All prompts include required sections - ✅ All files reference "Tendril" (42 references found) - ✅ All files use "Gitea" terminology (10 references, no GitHub) - ✅ Examples relevant to Tendril project structure - ✅ Documentation is clear and actionable ## Next Steps Phase 4 complete. LLM Usage Guides system is ready for use. Prompts can be dragged into Cursor chat sessions to perform standardized tasks. Ready for Phase 5: Validation and Testing. ## Related - Phase 4 Plan: kb/_guides/PROJECT-SETUP-GUIDE/PHASE-4-PLAN.md - Replication Guide: kb/_guides/PROJECT-SETUP-GUIDE/COMPLETE-SYSTEM-REPLICATION-GUIDE.md - Gitea LLM Guidelines: docs/GITEA/LLM-Gitea-Guidelines.md |
||
|
Gitea Actions
|
3ad53162c8 |
test(kb): add temporary test file for workflow validation
KB Lint / validate (push) Has been cancelled
This is a temporary test file to validate the KB lint workflow. The file follows all KB rules and should pass validation. Will be deleted after workflow testing is complete. |
||
|
Gitea Actions
|
830629f105 | chore: update KB index [skip ci] |