v1.6.0: Document Traceability & Orchestrator Refinements 📝
Release v1.6.0: Document Traceability & Orchestrator Refinements 📝
Version 1.6.0 focuses heavily on standardizing the reporting mechanisms for our Quality Gate agents (@ArtifactConsistencyChecker and @ClarificationAnalyst), implementing the robust Orchestrator-Reference architectural pattern, and resolving critical cross-platform synchronization bugs.
🚀 Enhancements & New Features
- Mandatory File Output for Quality Gates: Both
@ArtifactConsistencyCheckerand@ClarificationAnalystare now explicitly empowered (via exception rules) to generate and save their final reports directly as markdown files in thedocs/audit/directory. This ensures critical project alignment data is never lost in chat history. - AGENTS.md Policy Update: The overarching Source of Truth (
AGENTS.md) has been updated. The specific pushback rules for the Quality Gate agents now include official exception clauses permitting file generation for audit reports.
🛠️ Architecture & Under-the-Hood Fixes
- Orchestrator-Reference Pattern Applied:
- The
artifact-consistency-checkerskill has been refactored. Its heavy audit template is now securely isolated inreferences/AUDIT-REPORT-TEMPLATE.md. - The
clarification-analystskill has similarly been refactored to usereferences/CLARIFICATION-REPORT-TEMPLATE.md.
- The
- Markdownlint Compliance: Resolved multiple linting violations (
MD041: first-line-h1andMD001: heading-increment) within the Clarification Report template, ensuring pristine document generation right out of the box. - Global Path Translation Bug Fix: Fixed a critical bug in the synchronization engine. Previously, internal
SKILL.mdpaths incorrectly referenced the.agents/rules/directory when synced to other platforms. Now, paths dynamically translate to the correct{platform}/agents/convention across all IDE integrations. - GitHub Copilot Ecosystem Compliance (
.github): Corrected a synchronization issue where agents deployed to the.githubecosystem were lacking the required.agent.mdfile extension. The deployment engine now enforces strict GitHub Copilot naming standards to prevent duplicate or unrecognized agents.
Upgrade Guide:
As always, you can pull the latest changes or run the interactive installation scripts to sync these refinements across your preferred IDE platforms.