[Auto-QA] 25 uses of 'any' type reduce type safety

[clubanderson]

Auto-QA [Feature Recommendations]: Type Safety

Detected: 2026-06-14T14:07:40.586Z | Focus: Feature Recommendations | Commit: fed9343 | Run: View

Findings

Excessive 'any' type usage (25 occurrences) reduces type safety:

src/lib/acmm/tests/computeLevel.test.ts:62: // L2 "Instructed" uses a relaxed gate: any single criterion suffices
src/components/enterprise/tests/EnterpriseSidebar.test.tsx:8: SidebarShell: ({ navSections, branding, onAddCard, onAddMore }: any) => (
src/components/enterprise/tests/EnterpriseSidebar.test.tsx:12: {navSections.flatMap((section: any) => section.items).map((item: any) => (
src/components/enterprise/tests/EnterpriseLayout.test.tsx:49: DashboardCustomizer: ({ existingCardTypes, onAddCards, isOpen }: any) => (
src/components/mission-control/tests/ui-data-components.test.tsx:226: } as unknown as any}
src/components/mission-control/tests/ui-data-components.test.tsx:247: } as unknown as any}
src/components/mission-control/tests/ui-data-components.test.tsx:395: planningMission={{ status: 'running', messages: [] } as unknown as any}
src/components/settings/sections/VClusterActionBanner.tsx:16: : String(t(${keyBase}Fallback as any, { name: feedback.name, namespace: feedback.namespace }))
src/components/settings/sections/VClusterActionBanner.tsx:20: return String(t(keyBase as any, { name: feedback.name, namespace: feedback.namespace }))
src/components/dashboard/tests/CreateDashboardModal.test.tsx:52: <button onClick={onClose} data-testid="close-button" disabled={(rest as any).disabled}>Close
src/components/dashboard/tests/CreateDashboardModal.test.tsx:59: <div data-testid="modal-footer" data-disabled={(rest as any).disabled} data-loading={(rest as any).loading}>{children}
src/components/workloads/tests/Workloads.navigation.test.tsx:30:let mockPodIssues: any[] = []
src/components/workloads/tests/Workloads.navigation.test.tsx:31:let mockDeploymentIssues: any[] = []
src/components/workloads/tests/Workloads.navigation.test.tsx:32:let mockDeployments: any[] = []
src/components/workloads/tests/Workloads.navigation.test.tsx:33:let mockClusters: any[] = []
src/components/workloads/tests/Workloads.navigation.test.tsx:76: filterByCluster: (items: any[]) => items,
src/components/workloads/tests/Workloads.navigation.test.tsx:170: filterByCluster: (items: any[]) => items,
src/components/workloads/tests/Workloads.navigation.test.tsx:171: } as any)
src/components/workloads/tests/Workloads.test.tsx:44:let mockPodIssues: any[] = []
src/components/workloads/tests/Workloads.test.tsx:45:let mockDeploymentIssues: any[] = []
src/components/workloads/tests/Workloads.test.tsx:46:let mockDeployments: any[] = []
src/components/workloads/tests/Workloads.test.tsx:47:let mockClusters: any[] = []
src/components/workloads/tests/Workloads.test.tsx:66: filterByCluster: (items: any[]) => items,
src/components/workloads/tests/Workloads.test.tsx:184: filterByCluster: (items: any[]) => items,
src/components/workloads/tests/Workloads.test.tsx:185: } as any)

Suggested Improvements

• Replace any with specific types or unknown
• Create interfaces for API response types
• Use generics for flexible but type-safe code
• Add // eslint-disable-next-line only when truly necessary

PR Guidance: Keep changes under 50 lines (size S) for best acceptance rate. Split larger fixes into multiple PRs.

---

This issue was automatically created by the Auto-QA workflow during Feature Recommendations focus day.

[github-actions]

🐝 Hi @clubanderson! I'm kubestellar-hive[bot], an automation bot for this repo.

Trusted users — org members and contributors with write access — can mention @kubestellar-hive in a comment to trigger repo automation.
On issues, that mention queues an automated fix attempt. On pull requests, it records extra context for existing automation.
This is not an interactive Q&A bot, so mentions should be treated as requests for automation rather than a conversation.

Automation may take a moment to start, and follow-up happens through workflow activity rather than chat replies.

[github-actions]

Requires Human Intervention

Item: Issue #18402
Stuck since: ~2026-06-14T14:07Z (~2.5 hours ago)
Current state: ai-processing + ai-fix-requested + triage/accepted, no linked PR

Findings

• Issue entered ai-processing ~2.5 hours ago with no subsequent progress
• Only comment is the hive bot greeting (automated, not a fix attempt)
• No pull request has been opened to address this issue
• ai-needs-human label has now been applied

Recommended Next Steps

• A human maintainer should review the workflow history to determine whether an AI fix attempt was triggered and what happened
• If the fix pipeline stalled, consider manually queuing another attempt or assigning to a human contributor
• If this issue is no longer actionable, consider removing ai-fix-requested or closing it

Generated by Stuck Detection Workflow · 102.7 AIC · ⌖ 12.4 AIC · ⊞ 35.9K · ◷

[github-actions]

Status Check — Still Stuck (~5.5 hours, 2nd escalation)

Business hours check (19:38 UTC)

No progress since the initial escalation at 16:43 UTC (~3 hours ago). This issue remains stuck with no PR created.

Current state:

• Labels: ai-processing + ai-fix-requested + triage/accepted + ai-needs-human
• No linked PR found
• Entered ai-processing at ~2026-06-14T14:07 UTC — stuck for ~5.5 hours
• 1 prior escalation comment (16:43 UTC) went unaddressed

Summary: Only the hive bot greeting comment exists; no fix attempt has been made.

Recommended next steps for a human maintainer:

1. Remove ai-processing if no active agent is working on this
2. Manually queue a fix attempt, assign to a human contributor, or close if no longer actionable
3. The fix is scoped: address 25 occurrences of any type in src/lib/acmm/__tests__/computeLevel.test.ts and related files

Generated by Stuck Detection Workflow · 177.8 AIC · ⌖ 13.2 AIC · ⊞ 35.9K · ◷

[github-actions]

Status Check — Still Stuck (~8.9 hours, outside business hours)

This issue has been in ai-processing since 2026-06-14 ~14:07 UTC — approximately 8.9 hours with no PR created and no human response.

Current state:

• Labels: ai-processing + ai-fix-requested + triage/accepted + ai-needs-human
• No linked PR found
• 2 prior escalation comments have gone unaddressed

Outside business hours (22:59 UTC). This note is for awareness — no immediate action expected until business hours resume.

Recommended action at start of next business day:

1. Remove ai-processing — no agent appears to be actively working
2. Re-queue the fix or assign to a human contributor
3. The fix is scoped: address 25 uses of any type (mainly in src/lib/acmm/__tests__/computeLevel.test.ts and related files)

Generated by Stuck Detection Workflow · 95 AIC · ⌖ 13.4 AIC · ⊞ 35.9K · ◷

[github-actions]

Status Check — Off-Hours Update (~24.2 hours stuck, 10th escalation)

Off-hours check (02:26 UTC) — brief update.

This issue has been in ai-processing for approximately 24.2 hours (since 2026-06-14T02:14Z) with no linked PR or human response.

Last escalation: 2026-06-14T23:03Z (~3h23m ago)
ai-needs-human label: already applied (10th escalation, no response received)

Remaining stuck issues (#18393, #18389, #18388, #18397, #18400, #18402) are in the same state — all labeled ai-needs-human, all awaiting human review next business day.

Recommended next step: a human maintainer should review all stuck ai-processing issues during the next business day and decide whether to manually trigger fix attempts, reassign, or close them.

Generated by Stuck Detection Workflow · 280 AIC · ⌖ 12.6 AIC · ⊞ 35.9K · ◷