a802f619 reached the forge mirror and started no build: the caller under
.hanzo/workflows has no runner left. GitHub is canonical and its
linux-amd64 jobs run on the JIT runners in AWS (ns hanzo-ci).
Claude-Session: https://claude.ai/code/session_01TUxvfuta1Z44KVNYuAz71F
git.hanzo.ai launches runners for the hanzoai namespace, so the image is
built from the hanzoai/captable mirror; hanzo-apps/captable keeps the same
commits without a build.
hanzo.yml names ghcr.io/hanzoai/captable (docker/Dockerfile, linux/amd64),
which .hanzo/workflows/cicd.yml hands to hanzoai/ci's build.yml on every
push to main. The README says which repository builds it.
sendMail posts to /v1/notify/send/email as the app's own IAM identity
(client credentials), and notify delivers with the email provider and
sender configured for that org. SMTP settings and nodemailer are gone.
notify carries no attachments, so the e-sign completion email links the
signed document with a seven-day presigned URL instead of attaching it.
This repo and hanzo-apps/captable sit on the same commit, both declared
ghcr.io/hanzoai/captable, and both pushed to the same GitHub repo. Two writers
on one tag and one mirror; order decided the winner.
hanzo-apps/captable keeps the build and the mirror — it matches the GitHub home
the module path redirects to. This copy keeps only its reason to exist, which is
serving github.com/hanzoai/captable to the cloud build over insteadOf. The
mirror is already removed, so this commit stays local to the forge.
* feat: getting started with new share class
* feat: adding share class form and schema
* feat: complete share class form
* fix: input grids
* fix: error with type
* fix: update cover image
* fix: update cover with link
* fix: using <picture> instead
* feat: update image and readme
* feat: add read more link
* fix: update dark cover image
zeekay
zooqueen