mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
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.
17 lines
619 B
Python
17 lines
619 B
Python
"""
|
|
Facade re-exports for collaborative-edit publishing.
|
|
|
|
Callers that persist notebook edits outside the notebooks views (e.g. agent
|
|
tooling) publish the resulting update to the collab stream through these
|
|
re-exports rather than importing ``backend.markdown_collab`` directly.
|
|
"""
|
|
|
|
from ..markdown_collab import (
|
|
MarkdownDiff as MarkdownDiff,
|
|
apply_utf16_text_changes as apply_utf16_text_changes,
|
|
apublish_notebook_update as apublish_notebook_update,
|
|
build_markdown_update_diff as build_markdown_update_diff,
|
|
markdown_crc as markdown_crc,
|
|
publish_notebook_update as publish_notebook_update,
|
|
)
|