Administrators can see the base layer, decide package requests, rebuild the base, reclaim unused layers, and upload a wheel.
Why: approval and operations need a surface that uses the existing admin controls.
Evidence: the panel typechecks with the frontend sources. CI on this head is the authority.
Impact: one new admin section.
Refs: Agent-System-Dev feature/layered-python-env
Administrators can see the base layer, decide package requests, rebuild the base, reclaim unused layers, and upload a wheel.
Why: approval and operations need a surface that uses the existing admin controls.
Evidence: the panel typechecks with the frontend sources. CI on this head is the authority.
Impact: one new admin section.
Refs: Agent-System-Dev feature/layered-python-env
Why: Approving an extra package, rebuilding the base layer, reclaiming unused layers, and uploading a wheel need an admin surface that uses the existing admin controls.
Evidence: SELF tsc of the new panel reported no errors in frontend sources. UI package type errors come from missing node_modules in this worktree, not from this panel.
Impact: Administrators get a Python 环境 section. Other admin sections are unchanged.
Refs: .task/feature-layered-python-env.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Administrators can see the base layer, decide package requests, rebuild the base, reclaim unused layers, and upload a wheel.
Why: approval and operations need a surface that uses the existing admin controls.
Evidence: the panel typechecks with the frontend sources. CI on this head is the authority.
Impact: one new admin section.
Refs: Agent-System-Dev feature/layered-python-env