mirror of https://github.com/hanzoai/insights.git synced 2026-11-03 00:52:32 +00:00

Files

T

zeekay 1b367e2b62 chore: rebase the tree onto upstream master

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.

2026-08-01 15:44:40 -07:00

1.6 KiB

Raw Permalink Blame History

Route Finding

Find routes by reading the code. Do not depend on a generated helper or a hardcoded route table.

Core App Routes

For files under frontend/src/scenes/<scene>/...:

Inspect frontend/src/scenes/appScenes.ts for the scene import.
Inspect frontend/src/scenes/scenes.ts for the Scene.<Name> route entry.
Prefer the concrete urls.* route expression or literal route string from scenes.ts.

For files under frontend/src/lib/, frontend/src/queries/, frontend/src/types/, or other shared frontend areas, search for imports and choose 1-3 visible scenes that exercise the changed surface.

Product Routes

For files under products/<product>/frontend/scenes/<SceneName>/...:

Inspect products/<product>/manifest.tsx.
Match the changed scene directory to the manifest scenes import.
Use the manifest routes entry for that scene.

If the changed file is under a shared product frontend folder, search for imports inside that product and choose the visible scene routes that use it.

Fallbacks

Use rg to search for:

The changed component, hook, or logic name.
Nearby urls. references.
Literal route strings.
Product manifest routes and treeItems entries.

If route mapping is still unclear after a short search, add a coverage_gap target. Explain which file could not be mapped and what context was checked.

Do not fabricate IDs for dynamic routes. Keep placeholders such as :id, :runId, or :sourceId in the plan, then use an existing object from the UI or create minimal safe local data only when needed.

1.6 KiB Raw Permalink Blame History

Route Finding

Core App Routes

Product Routes

Fallbacks

1.6 KiB

Raw Permalink Blame History