@ai-coders/context 0.3.0 → 0.4.0

package/dist/generators/documentation/templates/onboardingTemplate.js

@@ -0,0 +1,431 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.renderOnboarding = renderOnboarding;
+function renderOnboarding() {
+    return `
+<!-- agent-update:start:onboarding-guide -->
+# Onboarding Guide
+
+Welcome to the team! This guide will help you get set up and productive quickly.
+
+## Onboarding Checklist
+
+### Day 1: Access & Accounts
+- [ ] **Email account** - Verify access to team email
+- [ ] **Chat/Communication**
+  - [ ] Slack/Teams workspace invitation
+  - [ ] Join relevant channels: #engineering, #team-name, #general
+- [ ] **Code repository access**
+  - [ ] GitHub/GitLab account added to organization
+  - [ ] SSH key configured for git operations
+  - [ ] Clone main repository
+- [ ] **Issue tracking**
+  - [ ] Jira/GitHub Issues access
+  - [ ] Assigned to team project/board
+- [ ] **Documentation access**
+  - [ ] Wiki/Confluence access
+  - [ ] Shared drive access (Google Drive, Notion, etc.)
+- [ ] **Meeting invites**
+  - [ ] Added to recurring team meetings
+  - [ ] Calendar access configured
+
+### Day 1-2: Development Environment
+- [ ] **Install required software**
+  - [ ] Node.js (version: TODO: specify version)
+  - [ ] npm/yarn package manager
+  - [ ] Git (latest stable version)
+  - [ ] Code editor/IDE (VS Code, WebStorm, etc.)
+  - [ ] Docker Desktop (if applicable)
+  - [ ] Database client (if applicable)
+- [ ] **Configure development environment**
+  \`\`\`bash
+  # Clone repository
+  git clone git@github.com:org/repo.git
+  cd repo
+
+  # Copy environment configuration
+  cp .env.example .env
+  # Edit .env with local settings
+
+  # Install dependencies
+  npm install
+
+  # Run database migrations (if applicable)
+  npm run migrate
+
+  # Start development server
+  npm run dev
+  \`\`\`
+- [ ] **Verify environment setup**
+  - [ ] Application runs locally
+  - [ ] Tests pass: \`npm test\`
+  - [ ] Linting works: \`npm run lint\`
+  - [ ] Can access local application in browser
+- [ ] **Editor configuration**
+  - [ ] Install recommended VS Code extensions (see .vscode/extensions.json)
+  - [ ] Configure code formatting (Prettier, ESLint)
+  - [ ] Set up debugger configuration
+
+### Day 2-3: Project Understanding
+- [ ] **Read core documentation**
+  - [ ] [Project Overview](./project-overview.md)
+  - [ ] [Architecture Notes](./architecture.md)
+  - [ ] [Development Workflow](./development-workflow.md)
+  - [ ] [Testing Strategy](./testing.md)
+- [ ] **Understand the codebase**
+  - [ ] Explore project structure
+  - [ ] Review main application entry points
+  - [ ] Understand key modules and their responsibilities
+  - [ ] Read recent pull requests to see code review standards
+- [ ] **Meet the team**
+  - [ ] 1:1 with manager
+  - [ ] Meet team members
+  - [ ] Meet cross-functional partners (Product, Design, QA)
+  - [ ] Understand team roles and responsibilities
+
+### Week 1: First Contributions
+- [ ] **Start with good first issues**
+  - [ ] Find issues tagged "good-first-issue" or similar
+  - [ ] Complete 1-2 small bug fixes or documentation updates
+  - [ ] Go through code review process
+  - [ ] Get first PR merged
+- [ ] **Learn the workflow**
+  - [ ] Create feature branch
+  - [ ] Make changes and write tests
+  - [ ] Submit pull request
+  - [ ] Address review feedback
+  - [ ] Merge and deploy (or see deployment process)
+- [ ] **Set up productivity tools**
+  - [ ] Configure git aliases
+  - [ ] Set up any team-specific CLI tools
+  - [ ] Bookmark important dashboards/tools
+  - [ ] Join pair programming sessions
+
+### Week 2-4: Ramp Up
+- [ ] **Take on larger tasks**
+  - [ ] Pick up medium complexity issues
+  - [ ] Work on feature development
+  - [ ] Participate in design discussions
+- [ ] **Deepen knowledge**
+  - [ ] Understand deployment process
+  - [ ] Learn monitoring and debugging tools
+  - [ ] Review production architecture
+  - [ ] Shadow on-call engineer (if applicable)
+- [ ] **Contribute to team processes**
+  - [ ] Attend sprint planning/standup
+  - [ ] Participate in retrospectives
+  - [ ] Update documentation as you learn
+
+### Month 2-3: Full Productivity
+- [ ] **Own features end-to-end**
+  - [ ] Design, implement, test, and deploy features
+  - [ ] Participate in on-call rotation (if applicable)
+  - [ ] Help onboard newer team members
+- [ ] **Identify improvements**
+  - [ ] Suggest process improvements
+  - [ ] Improve documentation
+  - [ ] Refactor problem areas
+
+---
+
+## Development Environment Setup
+
+### Prerequisites
+**Operating System:**
+- macOS 10.15+ or Linux (Ubuntu 20.04+)
+- Windows 10/11 with WSL2 (Windows Subsystem for Linux)
+
+**Required Tools:**
+- **Node.js:** v18.0.0 or higher ([Download](https://nodejs.org/))
+- **npm:** v9.0.0 or higher (comes with Node.js)
+- **Git:** v2.30.0 or higher ([Download](https://git-scm.com/))
+- **Docker:** (Optional) For running services locally
+
+### Step-by-Step Setup
+
+#### 1. Install Node.js
+\`\`\`bash
+# macOS (using Homebrew)
+brew install node@18
+
+# Linux (using nvm)
+curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash
+nvm install 18
+nvm use 18
+
+# Verify installation
+node --version  # Should show v18.x.x
+npm --version   # Should show v9.x.x
+\`\`\`
+
+#### 2. Configure Git
+\`\`\`bash
+# Set your identity
+git config --global user.name "Your Name"
+git config --global user.email "your.email@company.com"
+
+# Set up SSH key for GitHub
+ssh-keygen -t ed25519 -C "your.email@company.com"
+# Follow prompts, then add key to GitHub:
+# https://github.com/settings/keys
+
+# Test SSH connection
+ssh -T git@github.com
+\`\`\`
+
+#### 3. Clone and Setup Project
+\`\`\`bash
+# Clone repository
+git clone git@github.com:org/repo.git
+cd repo
+
+# Install dependencies
+npm install
+
+# Copy environment template
+cp .env.example .env
+
+# Edit .env with your local settings
+# Required variables:
+# - DATABASE_URL (if using database)
+# - API_KEY (if applicable)
+# - Any other project-specific variables
+\`\`\`
+
+#### 4. Database Setup (if applicable)
+\`\`\`bash
+# Option 1: Docker (recommended)
+docker-compose up -d db
+
+# Option 2: Local installation
+# Install PostgreSQL/MySQL/MongoDB locally
+# Create database
+createdb project_dev
+
+# Run migrations
+npm run migrate
+
+# Seed database with sample data (optional)
+npm run seed
+\`\`\`
+
+#### 5. Verify Setup
+\`\`\`bash
+# Run tests
+npm test
+
+# Start development server
+npm run dev
+
+# In another terminal, verify it's running
+curl http://localhost:3000/health
+# Or open http://localhost:3000 in browser
+\`\`\`
+
+### Common Setup Issues
+
+#### Port Already in Use
+\`\`\`bash
+# Find process using port 3000
+lsof -ti:3000
+
+# Kill the process
+kill -9 $(lsof -ti:3000)
+
+# Or use a different port
+PORT=3001 npm run dev
+\`\`\`
+
+#### Database Connection Errors
+- Verify database is running: \`docker ps\` or service status
+- Check DATABASE_URL in .env file
+- Ensure database exists: \`createdb project_dev\`
+- Verify migrations ran: \`npm run migrate:status\`
+
+#### Module Not Found Errors
+\`\`\`bash
+# Clear cache and reinstall
+rm -rf node_modules package-lock.json
+npm install
+\`\`\`
+
+---
+
+## Required Access & Permissions
+
+### Accounts to Request
+1. **GitHub Organization** - Request from: TODO: Add contact
+2. **AWS/Cloud Access** - Request from: TODO: Add DevOps contact
+3. **Database Access** - Request from: TODO: Add DBA contact
+4. **Monitoring/APM Tools** - Request from: TODO: Add contact
+5. **CI/CD Pipeline** - Request from: TODO: Add DevOps contact
+6. **Issue Tracker (Jira/etc.)** - Request from: TODO: Add PM contact
+
+### Team Permissions
+- **Repository:** Write access to main repo
+- **Deployments:** Staging access (production access granted after 1-2 months)
+- **Databases:** Read access to staging, read-only to production
+- **Cloud Resources:** Developer role in non-production environments
+
+---
+
+## Team Communication
+
+### Chat Channels
+- **#engineering** - General engineering discussions
+- **#team-[name]** - Your team's channel
+- **#deployments** - Deployment notifications
+- **#incidents** - Production issues and incidents
+- **#random** - Non-work related chat
+
+### Meetings
+- **Daily Standup** - Every day at TODO: time
+- **Sprint Planning** - TODO: frequency and day
+- **Sprint Retrospective** - TODO: frequency and day
+- **Team Sync** - TODO: frequency and day
+- **1:1 with Manager** - Weekly (scheduled individually)
+
+### Communication Guidelines
+- Use threads in Slack to keep conversations organized
+- @mention people directly when you need their attention
+- Use @here sparingly (only for time-sensitive team updates)
+- Update your status when away or in focus time
+- Default to public channels over DMs when possible
+
+---
+
+## Learning Resources
+
+### Project-Specific
+- **Architecture Documentation** - [Link to architecture docs](./architecture.md)
+- **API Documentation** - [Link to API docs](./api-reference.md)
+- **Deployment Guide** - [Link to deployment docs](./deployment.md)
+- **Troubleshooting** - [Link to troubleshooting guide](./troubleshooting.md)
+
+### Technical Skills
+- **Node.js Best Practices** - [Link to guide or external resource]
+- **TypeScript Handbook** - [TypeScript docs](https://www.typescriptlang.org/docs/)
+- **Testing Guide** - [Link to testing strategy](./testing.md)
+- **Security Guidelines** - [Link to security docs](./security.md)
+
+### Company/Team
+- **Engineering Handbook** - TODO: Add link
+- **Company Values** - TODO: Add link
+- **Team Charter** - TODO: Add link
+
+### External Resources
+- **JavaScript/TypeScript** - MDN Web Docs, TypeScript handbook
+- **React** - Official React documentation (if applicable)
+- **Database** - PostgreSQL/MySQL/MongoDB documentation
+- **DevOps** - Docker, Kubernetes documentation (if applicable)
+
+---
+
+## First Tasks
+
+### Suggested First Issues
+Look for issues tagged with:
+- \`good-first-issue\` - Easy issues for newcomers
+- \`documentation\` - Documentation improvements
+- \`bug\` with low priority - Simple bug fixes
+- \`refactoring\` - Code cleanup tasks
+
+### Starter Tasks Ideas
+1. **Fix a typo** in documentation or comments
+2. **Add tests** to increase coverage for existing code
+3. **Improve error messages** to be more helpful
+4. **Update dependencies** that have security patches
+5. **Add logging** to better understand system behavior
+
+---
+
+## Getting Help
+
+### When You're Stuck
+1. **Try to debug yourself** (15-30 minutes) - Check logs, search documentation
+2. **Search existing resources** - Check Slack history, documentation, issues
+3. **Ask your onboarding buddy** - Your assigned mentor for the first few weeks
+4. **Ask in team channel** - #team-[name] for team-specific questions
+5. **Ask in #engineering** - For broader technical questions
+
+### No Stupid Questions
+- We were all new once - ask questions freely!
+- Questions often uncover documentation gaps or process issues
+- If you're confused, others probably are too
+- Asking helps us improve onboarding for future team members
+
+### Escalation
+- **Technical questions** - Ask in #engineering or tech leads
+- **Access issues** - Ask IT or DevOps team
+- **Process questions** - Ask your manager or team lead
+- **Urgent production issues** - Follow incident response process
+
+---
+
+## Team Culture & Expectations
+
+### Work Hours
+- **Core hours:** TODO: e.g., 10am-4pm (team's local timezone)
+- **Flexibility:** Work when you're most productive
+- **Availability:** Be responsive during core hours
+- **Overtime:** Not expected regularly, communicate if overwhelmed
+
+### Code Review
+- **Response time:** Aim to review within 24 hours
+- **Constructive feedback:** Focus on code, not person
+- **Questions welcome:** Ask questions in PR comments
+- **Learn from reviews:** Reviews are learning opportunities both ways
+
+### Development Principles
+- **Test your code:** Write tests for new functionality
+- **Small PRs:** Keep changes focused and reviewable
+- **Documentation:** Update docs when changing behavior
+- **Security:** Think about security implications
+- **Performance:** Consider performance impact of changes
+
+### Growth & Development
+- **Learning time:** Dedicate time each week to learning
+- **Pair programming:** Great way to learn and teach
+- **Conference talks:** Share knowledge through internal or external talks
+- **Side projects:** Explore new technologies and ideas
+- **Career development:** Regular discussions with manager about growth
+
+---
+
+## Feedback & Questions
+
+### Onboarding Feedback
+We're always improving! Please provide feedback on:
+- What was confusing or missing?
+- What was particularly helpful?
+- Suggestions for improvement?
+
+**Submit feedback:** TODO: Add link to feedback form or channel
+
+### Questions About This Guide
+- Update this guide as you find gaps
+- Ask in #engineering if something is unclear
+- Your feedback helps future team members!
+
+<!-- agent-readonly:guidance -->
+## AI Update Checklist
+1. Verify all tool versions and installation instructions are current
+2. Update access request contacts with current team members
+3. Ensure all documentation links are valid
+4. Add new accounts or tools that team members need
+5. Update team communication channels and meeting schedules
+6. Refresh learning resources with current recommendations
+7. Verify suggested first issues are still appropriate
+
+<!-- agent-readonly:sources -->
+## Acceptable Sources
+- Development environment setup scripts and documentation
+- Team wiki or handbook
+- IT/DevOps onboarding documentation
+- Feedback from recent new hires
+- Repository README and CONTRIBUTING files
+
+<!-- agent-update:end -->
+`;
+}
+//# sourceMappingURL=onboardingTemplate.js.map

package/dist/generators/documentation/templates/onboardingTemplate.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"onboardingTemplate.js","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/onboardingTemplate.ts"],"names":[],"mappings":";;AACA,4CA2aC;AA3aD,SAAgB,gBAAgB;IAE9B,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwaR,CAAC;AACF,CAAC"}

package/dist/generators/documentation/templates/projectOverviewTemplate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"projectOverviewTemplate.d.ts","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/projectOverviewTemplate.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,4BAA4B,EAAE,MAAM,SAAS,CAAC;AAGvD,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,4BAA4B,GAAG,MAAM,CA+DnF"}
+{"version":3,"file":"projectOverviewTemplate.d.ts","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/projectOverviewTemplate.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,4BAA4B,EAAE,MAAM,SAAS,CAAC;AAGvD,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,4BAA4B,GAAG,MAAM,CA6DnF"}

package/dist/generators/documentation/templates/projectOverviewTemplate.js

@@ -1,30 +1,14 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.renderProjectOverview = renderProjectOverview;
-const frontMatter_1 = require("./frontMatter");
 const common_1 = require("./common");
 function renderProjectOverview(context) {
-    const frontMatter = (0, frontMatter_1.createFrontMatter)({
-        id: 'project-overview',
-        goal: 'Explain why the project exists, who it serves, and how to get productive quickly.',
-        requiredInputs: [
-            'Latest product or roadmap brief',
-            'Repository metadata (README highlights, package manifests)',
-            'List of stakeholders or domain experts for verification'
-        ],
-        successCriteria: [
-            'Quick Facts mirror current tooling, stack, and entry points',
-            'Directory map explains where primary capabilities live',
-            'Next steps point to authoritative specs or dashboards'
-        ],
-        relatedAgents: ['documentation-writer', 'architect-specialist']
-    });
     const directoryList = (0, common_1.formatDirectoryList)(context, true);
     const languageSummary = context.primaryLanguages.length > 0
         ? context.primaryLanguages.map(lang => `- ${lang.extension} (${lang.count} files)`).join('\n')
         : '- Language mix pending analysis.';
-    return `${frontMatter}
-<!-- ai-task:project-overview -->
+    return `
+<!-- agent-update:start:project-overview -->
 # Project Overview
 
 > TODO: Summarize the problem this project solves and who benefits from it.
@@ -34,13 +18,24 @@ function renderProjectOverview(context) {
 - Primary languages detected:
 ${languageSummary}
 
-## Directory Map
+## File Structure & Code Organization
 ${directoryList || '*Add a short description for each relevant directory.*'}
 
-## Technology Signals
-- Highlight frameworks, runtimes, state management patterns, data layers, and cross-service communication patterns detected in the repository.
-- Note build tooling, linting, and formatting infrastructure they should be aware of.
-- Call out external services (APIs, queues, cloud resources) and their integration points.
+## Technology Stack Summary
+- Outline primary runtimes, languages, and platforms in use.
+- Note build tooling, linting, and formatting infrastructure the team relies on.
+
+## Core Framework Stack
+- Document core frameworks per layer (backend, frontend, data, messaging).
+- Mention architectural patterns enforced by these frameworks.
+
+## UI & Interaction Libraries
+- List UI kits, CLI interaction helpers, or design system dependencies.
+- Note theming, accessibility, or localization considerations contributors must follow.
+
+## Development Tools Overview
+- Highlight essential CLIs, scripts, or developer environments.
+- Link to [Tooling & Productivity Guide](./tooling.md) for deeper setup instructions.
 
 ## Getting Started Checklist
 1. Install dependencies with \`npm install\`.
@@ -50,19 +45,21 @@ ${directoryList || '*Add a short description for each relevant directory.*'}
 ## Next Steps
 Capture product positioning, key stakeholders, and links to external documentation or product specs here.
 
+<!-- agent-readonly:guidance -->
 ## AI Update Checklist
 1. Review roadmap items or issues labelled “release” to confirm current goals.
 2. Cross-check Quick Facts against \`package.json\` and environment docs.
-3. Refresh the Directory Map to reflect new or retired modules; keep guidance actionable.
+3. Refresh the File Structure & Code Organization section to reflect new or retired modules; keep guidance actionable.
 4. Link critical dashboards, specs, or runbooks used by the team.
 5. Flag any details that require human confirmation (e.g., stakeholder ownership).
 
+<!-- agent-readonly:sources -->
 ## Acceptable Sources
 - Recent commits, release notes, or ADRs describing high-level changes.
 - Product requirement documents linked from this repository.
 - Confirmed statements from maintainers or product leads.
 
-<!-- /ai-task -->
+<!-- agent-update:end -->
 `;
 }
 //# sourceMappingURL=projectOverviewTemplate.js.map

package/dist/generators/documentation/templates/projectOverviewTemplate.js.map

@@ -1 +1 @@
-{"version":3,"file":"projectOverviewTemplate.js","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/projectOverviewTemplate.ts"],"names":[],"mappings":";;AAIA,sDA+DC;AAnED,+CAAkD;AAElD,qCAA+C;AAE/C,SAAgB,qBAAqB,CAAC,OAAqC;IACzE,MAAM,WAAW,GAAG,IAAA,+BAAiB,EAAC;QACpC,EAAE,EAAE,kBAAkB;QACtB,IAAI,EAAE,mFAAmF;QACzF,cAAc,EAAE;YACd,iCAAiC;YACjC,4DAA4D;YAC5D,yDAAyD;SAC1D;QACD,eAAe,EAAE;YACf,6DAA6D;YAC7D,wDAAwD;YACxD,uDAAuD;SACxD;QACD,aAAa,EAAE,CAAC,sBAAsB,EAAE,sBAAsB,CAAC;KAChE,CAAC,CAAC;IAEH,MAAM,aAAa,GAAG,IAAA,4BAAmB,EAAC,OAAO,EAAE,IAAI,CAAC,CAAC;IACzD,MAAM,eAAe,GAAG,OAAO,CAAC,gBAAgB,CAAC,MAAM,GAAG,CAAC;QACzD,CAAC,CAAC,OAAO,CAAC,gBAAgB,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,KAAK,IAAI,CAAC,SAAS,KAAK,IAAI,CAAC,KAAK,SAAS,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;QAC9F,CAAC,CAAC,kCAAkC,CAAC;IAEvC,OAAO,GAAG,WAAW;;;;;;;iBAON,OAAO,CAAC,aAAa,CAAC,QAAQ;;EAE7C,eAAe;;;EAGf,aAAa,IAAI,wDAAwD;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4B1E,CAAC;AACF,CAAC"}
+{"version":3,"file":"projectOverviewTemplate.js","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/projectOverviewTemplate.ts"],"names":[],"mappings":";;AAGA,sDA6DC;AA/DD,qCAA+C;AAE/C,SAAgB,qBAAqB,CAAC,OAAqC;IAEzE,MAAM,aAAa,GAAG,IAAA,4BAAmB,EAAC,OAAO,EAAE,IAAI,CAAC,CAAC;IACzD,MAAM,eAAe,GAAG,OAAO,CAAC,gBAAgB,CAAC,MAAM,GAAG,CAAC;QACzD,CAAC,CAAC,OAAO,CAAC,gBAAgB,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC,KAAK,IAAI,CAAC,SAAS,KAAK,IAAI,CAAC,KAAK,SAAS,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;QAC9F,CAAC,CAAC,kCAAkC,CAAC;IAEvC,OAAO;;;;;;;iBAOQ,OAAO,CAAC,aAAa,CAAC,QAAQ;;EAE7C,eAAe;;;EAGf,aAAa,IAAI,wDAAwD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyC1E,CAAC;AACF,CAAC"}

package/dist/generators/documentation/templates/securityTemplate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"securityTemplate.d.ts","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/securityTemplate.ts"],"names":[],"mappings":"AAEA,wBAAgB,cAAc,IAAI,MAAM,CAgDvC"}
+{"version":3,"file":"securityTemplate.d.ts","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/securityTemplate.ts"],"names":[],"mappings":"AACA,wBAAgB,cAAc,IAAI,MAAM,CAmCvC"}

package/dist/generators/documentation/templates/securityTemplate.js

@@ -1,25 +1,9 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.renderSecurity = renderSecurity;
-const frontMatter_1 = require("./frontMatter");
 function renderSecurity() {
-    const frontMatter = (0, frontMatter_1.createFrontMatter)({
-        id: 'security',
-        goal: 'Document authentication, authorization, data protection, and compliance expectations.',
-        requiredInputs: [
-            'AuthN/AuthZ implementation details',
-            'Secrets storage and rotation policies',
-            'Compliance frameworks or audit requirements'
-        ],
-        successCriteria: [
-            'Explains how users and services authenticate',
-            'Lists sensitive data classifications and storage locations',
-            'Provides clear escalation paths for security incidents'
-        ],
-        relatedAgents: ['security-auditor', 'code-reviewer']
-    });
-    return `${frontMatter}
-<!-- ai-task:security -->
+    return `
+<!-- agent-update:start:security -->
 # Security & Compliance Notes
 
 Capture the policies and guardrails that keep this project secure and compliant.
@@ -36,18 +20,20 @@ Capture the policies and guardrails that keep this project secure and compliant.
 ## Incident Response
 - On-call contacts, escalation steps, and tooling for detection, triage, and post-incident analysis.
 
+<!-- agent-readonly:guidance -->
 ## AI Update Checklist
 1. Confirm security libraries and infrastructure match current deployments.
 2. Update secrets management details when storage or naming changes.
 3. Reflect new compliance obligations or audit findings.
 4. Ensure incident response procedures include current contacts and tooling.
 
+<!-- agent-readonly:sources -->
 ## Acceptable Sources
 - Security architecture docs, runbooks, policy handbooks.
 - IAM/authorization configuration (code or infrastructure).
 - Compliance updates from security or legal teams.
 
-<!-- /ai-task -->
+<!-- agent-update:end -->
 `;
 }
 //# sourceMappingURL=securityTemplate.js.map

package/dist/generators/documentation/templates/securityTemplate.js.map

@@ -1 +1 @@
-{"version":3,"file":"securityTemplate.js","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/securityTemplate.ts"],"names":[],"mappings":";;AAEA,wCAgDC;AAlDD,+CAAkD;AAElD,SAAgB,cAAc;IAC5B,MAAM,WAAW,GAAG,IAAA,+BAAiB,EAAC;QACpC,EAAE,EAAE,UAAU;QACd,IAAI,EAAE,uFAAuF;QAC7F,cAAc,EAAE;YACd,oCAAoC;YACpC,uCAAuC;YACvC,6CAA6C;SAC9C;QACD,eAAe,EAAE;YACf,8CAA8C;YAC9C,4DAA4D;YAC5D,wDAAwD;SACzD;QACD,aAAa,EAAE,CAAC,kBAAkB,EAAE,eAAe,CAAC;KACrD,CAAC,CAAC;IAEH,OAAO,GAAG,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8BtB,CAAC;AACF,CAAC"}
+{"version":3,"file":"securityTemplate.js","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/securityTemplate.ts"],"names":[],"mappings":";;AACA,wCAmCC;AAnCD,SAAgB,cAAc;IAE5B,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgCR,CAAC;AACF,CAAC"}

package/dist/generators/documentation/templates/testingTemplate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"testingTemplate.d.ts","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/testingTemplate.ts"],"names":[],"mappings":"AAEA,wBAAgB,qBAAqB,IAAI,MAAM,CAsD9C"}
+{"version":3,"file":"testingTemplate.d.ts","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/testingTemplate.ts"],"names":[],"mappings":"AACA,wBAAgB,qBAAqB,IAAI,MAAM,CAyC9C"}

package/dist/generators/documentation/templates/testingTemplate.js

@@ -1,25 +1,9 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.renderTestingStrategy = renderTestingStrategy;
-const frontMatter_1 = require("./frontMatter");
 function renderTestingStrategy() {
-    const frontMatter = (0, frontMatter_1.createFrontMatter)({
-        id: 'testing-strategy',
-        goal: 'Explain how the project maintains quality, from unit coverage to release gates.',
-        requiredInputs: [
-            'Testing framework configuration (jest.config.js, etc.)',
-            'CI requirements for merges/releases',
-            'Known flaky suites or troubleshooting notes'
-        ],
-        successCriteria: [
-            'Test types list frameworks and ownership at a glance',
-            'Commands match package scripts and CI usage',
-            'Quality gates describe pass/fail expectations with numbers when possible'
-        ],
-        relatedAgents: ['test-writer', 'code-reviewer']
-    });
-    return `${frontMatter}
-<!-- ai-task:testing-strategy -->
+    return `
+<!-- agent-update:start:testing-strategy -->
 # Testing Strategy
 
 Document how quality is maintained across the codebase.
@@ -41,6 +25,7 @@ Document how quality is maintained across the codebase.
 ## Troubleshooting
 - Document flaky suites, long-running tests, or environment quirks.
 
+<!-- agent-readonly:guidance -->
 ## AI Update Checklist
 1. Review test scripts and CI workflows to confirm command accuracy.
 2. Update Quality Gates with current thresholds (coverage %, lint rules, required checks).
@@ -48,12 +33,13 @@ Document how quality is maintained across the codebase.
 4. Record known flaky areas and link to open issues for visibility.
 5. Confirm troubleshooting steps remain valid with current tooling.
 
+<!-- agent-readonly:sources -->
 ## Acceptable Sources
 - \`package.json\` scripts and testing configuration files.
 - CI job definitions (GitHub Actions, CircleCI, etc.).
 - Issue tracker items labelled “testing” or “flaky” with maintainer confirmation.
 
-<!-- /ai-task -->
+<!-- agent-update:end -->
 `;
 }
 //# sourceMappingURL=testingTemplate.js.map

package/dist/generators/documentation/templates/testingTemplate.js.map

@@ -1 +1 @@
-{"version":3,"file":"testingTemplate.js","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/testingTemplate.ts"],"names":[],"mappings":";;AAEA,sDAsDC;AAxDD,+CAAkD;AAElD,SAAgB,qBAAqB;IACnC,MAAM,WAAW,GAAG,IAAA,+BAAiB,EAAC;QACpC,EAAE,EAAE,kBAAkB;QACtB,IAAI,EAAE,iFAAiF;QACvF,cAAc,EAAE;YACd,wDAAwD;YACxD,qCAAqC;YACrC,6CAA6C;SAC9C;QACD,eAAe,EAAE;YACf,sDAAsD;YACtD,6CAA6C;YAC7C,0EAA0E;SAC3E;QACD,aAAa,EAAE,CAAC,aAAa,EAAE,eAAe,CAAC;KAChD,CAAC,CAAC;IAEH,OAAO,GAAG,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoCtB,CAAC;AACF,CAAC"}
+{"version":3,"file":"testingTemplate.js","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/testingTemplate.ts"],"names":[],"mappings":";;AACA,sDAyCC;AAzCD,SAAgB,qBAAqB;IAEnC,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsCR,CAAC;AACF,CAAC"}

package/dist/generators/documentation/templates/toolingTemplate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"toolingTemplate.d.ts","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/toolingTemplate.ts"],"names":[],"mappings":"AAEA,wBAAgB,kBAAkB,IAAI,MAAM,CAmD3C"}
+{"version":3,"file":"toolingTemplate.d.ts","sourceRoot":"","sources":["../../../../src/generators/documentation/templates/toolingTemplate.ts"],"names":[],"mappings":"AACA,wBAAgB,kBAAkB,IAAI,MAAM,CAsC3C"}