Adding runner token usage to observability

Split the question into claims.

1. Locate the code that reads runner usage.
2. Find its reviewed subsystem membership.
3. Trace production callers and static test candidates.
4. Read the surviving-line history and look for rationale.
5. State gaps before handing the result back.

Establish what writes the field.

The exact-commit AST inspection identifies an established SQL write and a static test reference. Its selected-file flow was truncated and never claims a complete writer inventory; the database connection's global identity also remains unestablished.

Locate the implementation.

MATCH (f:Function {
  repository_id: $repository, module_name: $module, qualified_name: $target
})
MATCH (f)-[:SUPPORTED_BY]->(span:SourceSpan)
OPTIONAL MATCH (sub:Subsystem)-[:CONTAINS]->(m:Module {
  repository_id: $repository, module_name: $module
})
RETURN f.qualified_name AS function, f.path AS path,
       f.start_line AS start_line, f.end_line AS end_line,
       collect(DISTINCT sub.name) AS subsystems,
       collect(DISTINCT span.locator) AS evidence,
       f.id AS source_node

This establishes static location and reviewed taxonomy membership. It does not establish the complete observability data path.

Ask when those surviving lines entered the code.

MATCH (f:Function {
  repository_id: $repository, module_name: $module, qualified_name: $target
})
MATCH (commit:Commit)-[touch:TOUCHES]->(f)
WHERE touch.join = 'git-blame-current-line'
OPTIONAL MATCH (commit)-[:TOUCHES]->(note:Note)
RETURN commit.object_id AS commit, commit.committed_at AS committed_at,
       note.natural_key AS note_id, note.title AS note_title,
       note.status AS recorded_status, touch.surviving_line_count AS surviving_lines,
       commit.evidence_json AS commit_evidence, note.evidence_json AS note_evidence
ORDER BY committed_at DESC, commit, note_id LIMIT $limit

No note was directly linked to this function's contributing commit. The date describes surviving blamed lines, not every later edit or a deployment.

Trace callers, tests and adjacent history.

MATCH (f:Function {
  repository_id: $repository, module_name: $module, qualified_name: $target
})
MATCH (caller)-[call:CALLS]->(f)
RETURN caller.module_name AS module, caller.qualified_name AS caller,
       caller.path AS path, caller.start_line AS line,
       call.evidence_json AS evidence
ORDER BY module, caller LIMIT $limit

MATCH (f:Function {
  repository_id: $repository, module_name: $module, qualified_name: $target
})
MATCH (caller)-[:CALLS]->(f)
WHERE caller.path STARTS WITH 'yesod/src/'
MATCH (commit:Commit)-[touch:TOUCHES]->(caller)
WHERE touch.join = 'git-blame-current-line'
MATCH (commit)-[:TOUCHES]->(note:Note)
RETURN caller.qualified_name AS caller, commit.object_id AS commit,
       commit.committed_at AS committed_at, note.natural_key AS note_id,
       note.title AS note_title, note.evidence_json AS evidence
ORDER BY committed_at DESC, commit, caller, note_id LIMIT $limit

The follow-up found adjacent planning context but no direct rationale. Its private note metadata is omitted, and the graph agent does not promote it into an explanation of the parser.