Audion Hub Manager
Portable Windows-first Python/NiceGUI workbench for code, Markdown, Git and filtered project mirrors.
Audion Hub Manager is built around a simple model:
Full Project -> Hub Projection -> Git remotes / bundle
\-> Docs Markdown view
The full project remains the source of truth. Hub Projection is a curated, rebuildable mirror that keeps the parts useful for review, agents, Git history, Docs views and repeatable development workflows.
What It Does
- shows Source, Hub Projection and Docs-oriented structures in one local UI
- runs MIRROR preview/apply through a profile-gated projection engine
- keeps Source untouched during MIRROR
- shows Git actions, status, diffs, commit basket and checkpoint commands
- separates active-project controls from registry-wide Source actions and
selected-tree actions
- reports registry-wide Git health through a compact SOURCE badge
- provides a Markdown/text editor pane with CodeMirror preference and textarea
fallback
- shows RedLine diffs with additions/deletions highlighted
- exposes Auth helpers for GitHub/GitLab/SSH/GCM/external tools without storing
tokens
- connects to any self-hosted Forgejo or Gitea instance with a personal access
token kept in the OS credential store, and can list or create repositories there
- keeps command output visible in an HTML/ANSI terminal dock
- separates portable defaults from local machine overrides
- includes safe registry cleanup for stale
projects.jsonrecords without
deleting project folders
Projection Profile Philosophy
Hub Projection is Dev-Git oriented. It is not a raw copy of a project folder.
Allowed examples:
- source files and scripts
- Markdown/text documentation
- lock files such as
uv.lock,Cargo.lock,yarn.lock - Git metadata files such as
.gitmodulesand.git-blame-ignore-revs - shared project configs such as
.editorconfig, linter configs and
.vscode/tasks.json
Excluded examples:
- runtime payloads and portable Python contents
- generated logs/reports/caches
- build outputs such as
dist,build,out,target,bin,obj - minified bundles and source maps
- binaries, archives, media and wheels
- secrets and machine-local overrides such as
config/apps.local.json
The important edge case is .vscode/: the directory is not excluded as a whole, because shared VS Code tasks/launch settings can be useful project context. Machine-specific values must go into local override files instead.
Git Model
Source may have its own normal .git repository for real development. Hub Projection may also have its own normal .git repository as a reference history for the filtered mirror. Hub Manager does not use sidecar Git directories.
When Hub Manager creates commits, it stages only the same file set allowed by the active Hub projection profile, plus generated marker files such as .gitkeep.
Entry Points
launcher_gui.cmd
or:
runtime\python.exe system_core\main.py
Useful checks:
runtime\python.exe -m pytest -q tests
runtime\python.exe -m compileall -q system_core
runtime\python.exe system_core\main.py --mirror-preview audion_hub_manager --json
Current State
This is an active development workbench. The strategic product frame is in place: the right workbench is arranged as Quick, Branch, Editor, Diff, Storage over Remote, Basket, Reader, History and Details. Safety Scan lives in Storage. Branch owns branch status, switch/tag, merge/revert/cherry-pick, stash and branch-danger templates. The Remote pane now owns remotes, push/pull/fetch and Auth setup; Auth still delegates login to external tools and stores no tokens. The left panel separates Open, MIRROR, SOURCE ACTIONS, PROJECT ACTIONS and SUPPORT commands, while the Structure panel switches PROJECT/GIT COPY/DOCS tree layers. Portable relative paths in projects.json are supported for projects inside the manager tree. The remaining work is mainly hardening, testing, remote edge cases and UI polish.