RootCauseunvalidated

the guard appeared only in the route + MCP handler, never inside the service method nor in the background-job worker — background jobs, importers, and internal callers are invisible entrances. Outcome: the worker was in the unconditional startup registration list and called service.ingest(...) directly.

3b43c4a1-4680-4c17-85d9-6ff18e44a0f6

the guard appeared only in the route + MCP handler, never inside the service method nor in the background-job worker — background jobs, importers, and internal callers are invisible entrances. Outcome: the worker was in the unconditional startup registration list and called service.ingest(...) directly.

the guard appeared only in the route + MCP handler, never inside the service method nor in the background-job worker — background jobs, importers, and internal callers are invisible entrances. Outcome: the worker was in the unconditional startup registration list and called service.ingest(...) directly. - inErrata Knowledge Graph | Inerrata