11 Commits
Author SHA1 Message Date
zeekayandHanzo Dev 483277a9cc Go 1.27.1, and the code it can say more simply
Modules declare go 1.27.1 and the build images follow. go fix applied the
modernizers; omitzero is not applied, since it changes what the JSON says.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 22:56:29 -07:00
zeekayandHanzo Dev 0aad59738b fix: call the pipeline at the address it actually lives
hanzoai/ci keeps the reusable at .github/workflows/build.yml — the one path
both planes resolve, since github.com reads a reusable only from there and the
forge reads it too. The v1 tag moved with it, so a caller still naming
.hanzo/workflows/build.yml asks for a blob that is not in the tree:

  InsertRun: read hanzoai/ci@v1:.hanzo/workflows/build.yml: object does not exist

The caller itself stays at .hanzo/workflows/cicd.yml on purpose: github.com has
no runner for these labels, so a caller placed there could never be scheduled.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 01:14:29 -07:00
zeekayandHanzo Dev a18718e31e chore: symlink AGENTS.md + GEMINI.md + CLAUDE.md -> LLM.md
Co-authored-by: Hanzo Dev <[email protected]>
2026-09-02 01:06:19 -07:00
zeekay 22716c25ed fix(brand): the tab shows our mark, not the framework we built on
These favicons still shipped the upstream artwork of whatever the surface was
scaffolded from, so a customer with a few of our products open read someone
else in every tab. They are @hanzo/logo favicon.{ico,svg,png} now, one source
for the geometry.
2026-08-25 11:49:19 -07:00
zeekayandHanzo Dev d6b720496f the suffix list note says what the tracked copy actually is
Co-authored-by: Hanzo Dev <[email protected]>
2026-08-09 23:59:27 -07:00
zeekayandHanzo Dev 4ab38ad5d1 the vendored suffix list carries only the rules the parser reads
ParseList reads the ICANN section and skips every comment, so the two thirds
of the published document that is per-registry commentary and the private
section it discards wholesale were never anything but 244 KB of tracked
third-party prose. That prose includes registrar contact addresses, one of
which is a site-generator vendor's and trips the structural check.

Filter at fetch time rather than after it, so `go generate` reproduces exactly
what is committed and the next refresh cannot reintroduce the prose. Upstream's
licence and version header stay. Both forms parse to the same List — 1454
top-level include labels, 2 excludes — so lookups are unchanged.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-09 23:39:28 -07:00
zeekay 0280eff666 retire the GitHub Actions workflows
Actions are disabled on this repository, so these files have not run in a long
time and cannot run: they are build definitions no forge executes. Builds go
through the native path -- POST /v1/runner, which schedules a BuildKit job --
and CI lives under .hanzo/workflows. A dead workflow that still looks like a
pipeline is worse than none, because it reads as coverage nobody has.
2026-08-07 09:25:18 -07:00
zeekayandHanzo Dev 2522924de5 ci: canonical pair — hanzo.yml + forge caller
github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-06 02:28:24 -07:00
zeekayandHanzo Dev 75b0c54e1f webmail: bug reports go to our tracker, not upstream's
The webmail 'file a bug' links and the JS error reporter pointed at
github.com/mjl-/mox/issues. Deployed as-is, every Hanzo user hitting a webmail
error would have filed it on Mechiel's tracker — noise for upstream and lost
reports for us.

Rewritten in BOTH webmail.ts and the generated webmail.js (4 occurrences each,
verified equal) so they do not disagree until the frontend toolchain next
regenerates. The error-report title is namespaced to hanzo mail so the
prior-reports search matches our issues.

This does not touch LICENSE, NOTICE, or attribution: the fork stays honestly
Mox's, only the place to report OUR deployment's bugs changes.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-27 23:23:07 -07:00
zeekayandHanzo Dev 39fc3734fe Record the exact inventory of remaining upstream references in LLM.md
Every mjl-/mox reference left in the tree is intentional; list them with counts
and reasons so an accidental one is easy to spot. Note that website/website.go
did change (its source and feedback links now point at this repo), unlike the
website/*.md prose.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-27 23:18:46 -07:00
zeekayandHanzo Dev 15909c7b79 Rename Go module path to github.com/hanzoai/mail
Fork of github.com/mjl-/mox at 5656ca6d1b
(upstream v0.0.15 plus 55 commits).

Rename the module path in go.mod and the import paths in 268 Go files. Also
update the five scripts that "go install" the module (genwebsite.sh,
docker-release.sh, apidiff.sh, test-upgrade.sh, Dockerfile.release), which
would otherwise build upstream rather than this fork.

Add NOTICE recording the upstream project, author, license, and fork point,
and stating which license covers which files: MIT for the mox source and our
changes, MPL-2.0 for publicsuffix/public_suffix_list.txt alone, and the
vendored dependencies' own licenses under licenses/. Embed NOTICE so
"mail licenses" prints the lineage from the running binary. LICENSE.MIT,
LICENSE.MPLv2.0 and the licenses/ tree are preserved verbatim; no code is
relicensed.

The mox command name, config keys, data directory layout and website content
are unchanged. LLM.md records the fork point, the rename, what was left alone,
and the steps to stand the server up.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-27 23:16:19 -07:00