mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-03 00:52:32 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
1.5 KiB
1.5 KiB
paths
| paths | |
|---|---|
|
Check this product's isolation status before making changes.
Look at the product's package.json: if backend:contract-check is listed under scripts,
this product is isolated.
- Isolated: external code (core, other products) may only import from the
backend/facade/package —api.pyfor data capabilities, and capability submodules (queries.py,tasks.py,temporal.py, …) for wiring that core registers or dispatches on. Do not expose internal modules directly, and do not add raw cross-product imports — go through the target product's facade instead. Wiring submodules may only re-export classes that implement a core-owned base (QueryRunner,MaxTool, Temporal defns,@shared_task) and are defined under the product's wiring locations (backend/insightsql_queries/,backend/max_tools.py,backend/temporal/,backend/tasks/); data and error types belong infacade/contracts.py; Django models never cross the boundary (seeproducts/architecture.md§ Wiring couplings). - Not isolated: boundaries are not yet enforced by CI, but prefer using existing facades when they exist rather than importing internals.
If you need to extend what's reachable across a boundary, add a function to the relevant
facade module (or a re-export to its wiring submodule) — not a depends_on entry in
tach.toml.
Run tach check --dependencies --interfaces to verify import boundaries are clean.