Create 5 priority GitHub issues for v1.0 release with agent assignments

[Copilot]

Created 5 actionable GitHub issues targeting v1.0 release blockers: test coverage gaps, type safety violations, and performance optimization. All issues enhanced with explicit agent assignments and agent-specific implementation guidance.

Issues Created

Critical: Test Coverage (#631) → @testing-agent

• Current: 75.06% statements / 64.9% branches
• Target: 80% statements / 70% branches (ISMS requirement)
• Identifies 6 low-coverage files: componentOptionsData.ts (42%), businessImpactData.ts (41%), ciaContentService.ts (68%), validationService.ts (51%), CostEstimationWidget.tsx (64%)
• Agent guidance: Vitest patterns, React Testing Library examples, verification commands

High: TypeScript Type Safety (#632) → @typescript-react-agent

• 110 any type instances across services, utils, types, widgets
• Target: Zero any types (use proper interfaces or unknown with type guards)
• Violates strict TypeScript policy in repository guidelines
• Agent guidance: Reusability checks, type replacement patterns, existing type references

High: Bundle Size Optimization (#633) → @typescript-react-agent + @code-review-agent

• Current: 188KB JS (gzip)
• Target: <180KB (8KB reduction)
• Strategies: Lazy load widgets, tree shaking, terser optimization, dependency deduplication
• Agent guidance: React.lazy() patterns, Vite config optimization, React.memo() examples

Medium: Constants Branch Coverage (#634) → @testing-agent

• 7 constants files with 0% branch coverage despite containing conditional logic
• Contributes 5.1% to branch coverage gap
• Agent guidance: Vitest patterns for constants, edge case testing strategies

Medium: Widget & Data Coverage (#635) → @testing-agent + @typescript-react-agent

• 8 critical files at 42-73% coverage
• Priority: CostEstimationWidget, componentOptionsData, businessImpactData
• Business-critical components for ROI calculations
• Agent guidance: Data file tests, widget component tests, RTL patterns

Agent-Friendly Enhancements

Each issue now includes:

• ✅ Explicit agent recommendation at top of issue (🤖 header)
• ✅ Agent-specific implementation guidance tailored to agent expertise
• ✅ Reusability reminders for TypeScript agent (mandatory existing code checks)
• ✅ Testing patterns with Vitest/RTL examples for testing agent
• ✅ Verification commands - exact bash commands to validate work
• ✅ Example code - before/after patterns showing expected changes
• ✅ Agent documentation links in Related Resources section

Metrics

All measurements from actual codebase analysis:

npm run coverage  # 75.06% statements, 64.9% branches
grep -r "any" src --include="*.ts" --include="*.tsx" | wc -l  # 110 instances
npm run build && ls -lh dist/assets/*.js  # 188KB

Total effort: 23-30 hours across 5 issues
Agent distribution: @testing-agent (3 issues), @typescript-react-agent (3 issues), @code-review-agent (1 issue)
Impact: Blocks v1.0 production readiness

Custom agent used: hack23-cia-compliance-manager-taskagent
CIA Compliance Manager product specialist creating GitHub issues for compliance dashboard, optimizing code quality, UI/UX, and ensuring ISMS alignment

Original prompt

create top 5 priority issues for next minor release

Custom agent used: hack23-cia-compliance-manager-taskagent
CIA Compliance Manager product specialist creating GitHub issues for compliance dashboard, optimizing code quality, UI/UX, and ensuring ISMS alignment

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pethers]

@copilot Analys is all issues created suitable for agents in repo to work on ? improve/rewrite issues

[Copilot]

@copilot Analys is all issues created suitable for agents in repo to work on ? improve/rewrite issues

All 5 issues have been analyzed and improved for agent suitability:

✅ Agent Assignments Added:

• 🧪 Increase test coverage to meet ISMS policy requirements (80% line, 70% branch) #631: @testing-agent (test coverage)
• 🔧 Replace all 'any' types with proper TypeScript types (110 instances) #632: @typescript-react-agent (type safety)
• ⚡ Optimize bundle size from 188KB to <180KB (8KB reduction) #633: @typescript-react-agent + @code-review-agent (bundle optimization)
• 🧪 Add branch coverage tests for constants files (currently 0% branch coverage) #634: @testing-agent (constants branch coverage)
• 🧪 Improve coverage for low-coverage widgets and data files (42-73% → 80%) #635: @testing-agent + @typescript-react-agent (widget/data coverage)

✅ Agent-Specific Enhancements:

• Explicit agent recommendations at top of each issue (🤖 header)
• Agent-specific implementation guidance and best practices
• Mandatory reusability checks for TypeScript agent
• Vitest/React Testing Library patterns for testing agent
• Verification commands and example code for each agent
• Links to agent documentation in Related Resources

Each issue is now immediately actionable by the recommended agents with clear instructions, example patterns, and verification steps. The agents can work independently on their assigned issues following the project's guidelines for reusability, type safety, and testing standards.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None