Skip to content

Deferred work referenced by TODO markers in src/ #1576

Description

@murdore

A home for the sixteen TODO markers in src/, so they cite something real.

Why this exists

They currently read TODO(#1179). #1179 is an auto-generated Pattern Analysis finding titled "todo-with-issue-reference: 1 finding(s)" — the report that complained TODOs lacked issue references. It is closed.

The timeline is exact:

#1179 created 2026-07-16T16:00:33Z
commit 80fd6ef9 "add issue references to TODO/FIXME comments" 2026-07-28T02:27:49Z
#1179 closed 2026-07-28T02:27:51Z

Two seconds. The citation points at the report that the citation itself closed. Anyone following #1179 to find the plan finds a lint result about formatting.

Deleting the references is not a fix either: the analysis is external to this repo and recurring — it filed the same rule again as #1318 on 2026-08-11 — so untagging would simply produce a fresh report and another round of meaningless numbers.

The sixteen

file:line deferred work
src/lib/core/baseProvider.ts:180, :2230 global-level middlewares
src/lib/evaluation/scorers/rule/formatScorer.ts:511 full JSON Schema validation
src/lib/mcp/mcpRegistryClient.ts:322 fetch from remote registry
src/lib/mcp/toolRegistry.ts:1034 FlexibleToolValidator class
src/lib/middleware/utils/guardrailsUtils.ts:420 block overly complex/long patterns
src/lib/neurolink.ts:12435, :12595 ToolExecutionEvent utilities, getToolExecutionEvents()
src/lib/rag/ChunkerFactory.ts:240 dedicated SemanticChunker with LLM support
src/lib/server/websocket/WebSocketHandler.ts:469, :478, :487 generate / streaming / tool-call via neurolink
src/lib/workflow/config.ts:453 provider-specific pricing
src/lib/workflow/core/workflowRegistry.ts:25 persistent storage
src/lib/workflow/core/workflowRunner.ts:247 per-model cost breakdown
src/lib/workflow/utils/workflowMetrics.ts:201 semantic similarity

What this issue is and isn't

It is a register, not a commitment — it says these markers exist and what they mean, so the reference resolves to something true.

Anything here that is genuinely planned deserves its own issue; anything that is not should have its marker deleted rather than tracked. Both are better than the status quo, and neither needs this issue to stay open forever.

Opened while working a backlog item (G5) that flagged the citation as fictitious.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions