Files
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

75 lines
2.2 KiB
JSON
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
[
{
"name": "keeps allow-listed words, redacts the rest length-preserving",
"allow": { "text": ["hello"], "url": [] },
"input": "hello world",
"expected": "hello *****"
},
{
"name": "numeric tokens become #",
"allow": { "text": [], "url": [] },
"input": "order 12345",
"expected": "***** #####"
},
{
"name": "redacts a whole email before tokenizing",
"allow": { "text": ["contact", "me", "at", "now"], "url": [] },
"input": "contact me at [email protected] now",
"expected": "contact me at ******************** now"
},
{
"name": "keeps a possessive whose base is allow-listed",
"allow": { "text": ["insights", "dashboard"], "url": [] },
"input": "Insights's dashboard",
"expected": "Insights's dashboard"
},
{
"name": "typographic apostrophe possessive resolves to allow-listed base",
"allow": { "text": ["it", "fine"], "url": [] },
"input": "it’s fine",
"expected": "it’s fine"
},
{
"name": "unicode word kept when allow-listed",
"allow": { "text": ["café"], "url": [] },
"input": "café",
"expected": "café"
},
{
"name": "unicode word redacted per code point",
"allow": { "text": [], "url": [] },
"input": "café",
"expected": "****"
},
{
"name": "decimal number splits on the dot (tokenizer boundary), each digit run masked",
"allow": { "text": [], "url": [] },
"input": "3.14",
"expected": "#.##"
},
{
"name": "alphanumeric token is not numeric",
"allow": { "text": ["build"], "url": [] },
"input": "v2 build",
"expected": "** build"
},
{
"name": "at-sign without a valid TLD is not treated as an email",
"allow": { "text": ["foo", "bar"], "url": [] },
"input": "foo@bar",
"expected": "foo@bar"
},
{
"name": "multiple emails in one string are each redacted",
"allow": { "text": ["email", "or", "please"], "url": [] },
"input": "email [email protected] or [email protected] please",
"expected": "email ******* or ******* please"
},
{
"name": "email with a multi-label domain redacts through the whole domain",
"allow": { "text": ["mail", "end"], "url": [] },
"input": "mail [email protected] end",
"expected": "mail *********** end"
}
]