Hyu 6ee9c0a9a3 fix(operation-trace): bind the workspace scope on every off-request write ...

Cloud runtime refuses unscoped database access and workspace_operation_logs is row-level-secured on the bound Workspace. The background writer, the retention pass and the metadata reads all run outside a request lifetime, so each of them failed and the failure was swallowed by the best-effort handler: enabling tracing recorded nothing at all.

The route wrapper also traces after the handler released its scope, so level resolution has to carry the Workspace itself. Without it the level read back as 0 and the request was dropped before it was even queued.

The startup gate now enumerates the Workspaces through this instance's execution bindings, because a cross-Workspace metadata scan cannot see them under RLS, and it runs after the Workspace service exists. The writer starts with a clean context so it cannot inherit the scope of the request that first enqueued a trace, and a dropped write is reported instead of being logged only at debug.

2026-09-28 22:38:35 +08:00

..

__init__.py

refactor(operation-trace): isolate subsystem, fix install identity, merge migrations

2026-09-27 00:11:57 +08:00

routes.py

refactor(operation-trace): isolate subsystem, fix install identity, merge migrations

2026-09-27 00:11:57 +08:00

service.py

fix(operation-trace): bind the workspace scope on every off-request write

2026-09-28 22:38:35 +08:00