feat(pro): generalize pro tier to multi-surface extension points
Move the pro mount decnet/services/pro/ -> decnet/pro/ so the Professional tier
can contribute to more than honeypots. The core wires each surface only when
decnet/pro/ is present (absence stays the entitlement gate):
* services — registry scans decnet/pro/services/ (was decnet/services/pro/)
* API routes — decnet/pro/routes.py exposes ROUTERS, mounted under /api/v1
* web pages — Vite aliases @pro to the pro frontend (community -> empty stub),
App.tsx maps proRoutes into <Route>s, Layout renders a
PROFESSIONAL nav group; both tree-shake out of the community build
Frontend gate mirrors the existing VITE_DECNET_DEVELOPER tree-shake pattern.
Tests: registry + router seams (backend), empty-stub contract (frontend).
This commit is contained in:
7
.gitignore
vendored
7
.gitignore
vendored
@@ -76,5 +76,8 @@ testfail
|
||||
.phaseloop/
|
||||
|
||||
# Professional tier: proprietary, lives in a separate private repo
|
||||
# (github.com/DECNET-Foundation/decnet-professional). Must NEVER be tracked by the open-core repo.
|
||||
/decnet/services/pro/
|
||||
# (github.com/DECNET-Foundation/decnet-professional), mounted at decnet/pro/.
|
||||
# Must NEVER be tracked by the open-core repo. src/pro-impl/ is where the pro
|
||||
# build copies the pro frontend so the JS toolchain resolves it.
|
||||
/decnet/pro/
|
||||
/decnet_web/src/pro-impl/
|
||||
|
||||
Reference in New Issue
Block a user