6d5f6b01a4
So a scoped compile can resolve the project OWNER's per-user custom libraries (not the requester's) — a shared/embed/anon compile of someone else's project still finds that owner's uploaded libs. - core/hooks.py: new get_project_owner hook; materialize_library_scope gains an opaque owner_id param (no-op default unchanged). - espidf_compiler.compile/_attempt: thread owner_id to the materializer. - compile.py: resolve owner via get_project_owner(project_id), pass to compile. Additive: the OSS image (no overlay) ignores owner_id; index libs still resolve from the cache. Foundation for per-user custom-lib storage (P2.2a write side). |
||
|---|---|---|
| .. | ||
| api | ||
| core | ||
| database | ||
| mcp | ||
| models | ||
| schemas | ||
| services | ||
| utils | ||
| __init__.py | ||
| main.py | ||