chore: move repository references to Twigpine/zero

[PierrunoYT]

What changed

Replaces Gitlawb/zero with Twigpine/zero in tracked files: the Go module path and imports, install scripts, zero update's default repository, docs, workflows, packaging, action.yml defaults and mise entries. Rebased onto main at 8c4e759.

Also:

• packaging/homebrew/zero.rb names the Twigpine/homebrew-tap tap.
• docs/INSTALL.md keeps go install github.com/Gitlawb/zero/cmd/zero@latest, with a note, because every tagged release so far declares that module path.

Intentionally unchanged:

• X-AIMLAPI-Integration-Repo (Gitlawb/zero) and DefaultPartnerName in internal/aimlapi: AIMLAPI attribution, pending a maintainer decision
• npm scope: already @twigpine/zero on main; the remaining @gitlawb/zero mentions are the legacy-package migration notes and detection
• LICENSE copyright
• GitLawb OpenGateway provider identifiers and URLs
• Historical CHANGELOG.md links
• Arbitrary Gitlawb/... fixture strings in internal/update and internal/cli tests

Parent issue: #1129

Why

The repository now lives at https://github.com/Twigpine/zero.

Verification

• Every changed line, apart from the Homebrew comment and the INSTALL note, is exactly the Gitlawb/zero → Twigpine/zero substitution (checked by pairing every diff hunk).
• gofmt -l, go vet ./... (GOOS=linux, darwin, windows), git diff HEAD --check, govulncheck: clean
• go run ./cmd/zero-release build and smoke: pass, version stamped 0.11.0 through the renamed -X path
• go test: update, release, installtest, npmwrapper, doctor, aimlapi, providercatalog, config pass. In go test ./... on Windows, only internal/cli, internal/gitsafe and internal/zerogit fail, with the same tests and errors as unmodified main on that machine (git cannot open NUL under Git Bash, no chatgpt provider).

🤖 Generated with Claude Code

[Vasanthdev2004]

Reviewed at 87df72d9. The replacement looks complete for repository references. What's left of gitlawb is the npm scope, the AIMLAPI partner name and two comments, one of which names the tap. The -X path in BuildLdflags moved too, and zero-release build and smoke stamp 0.9.0 here, so version stamping survived. go build, go vet and the update, release, installtest, npmwrapper and doctor tests pass on Windows.

I'd like it split, though, and the module path needs a decision from @kevincodex1:

• The runtime defaults should go in on their own. DefaultRepository in internal/update, ZERO_REPO in both install scripts, the postinstall REPO, the Action's zero-repo and the install URLs in the README are what installs and zero update actually fetch from. Until they move, every one of them reaches the release through GitHub's redirect from the old name. That's a small PR that can land now.
• The module path is a bigger change than it looks. 59 of the other 62 open PRs touch Go files, and once go.mod says Twigpine, any of them that adds an import or a new file needs the same rename before it compiles. When to do that is kevin's call.
• go install github.com/Twigpine/zero/cmd/zero@latest in docs/INSTALL.md fails until a release is tagged with the new module path. I tried it: v0.9.0's go.mod declares github.com/Gitlawb/zero, so Go stops with "module declares its path as: github.com/Gitlawb/zero but was required as: github.com/Twigpine/zero". The docs should keep the old path until that release exists.
• X-AIMLAPI-Integration-Repo changes too. That header is what AIMLAPI sees for attribution, so it needs kevin's yes rather than riding along with the rename.
• Small: packaging/homebrew/zero.rb still names Gitlawb/homebrew-tap, which is now Twigpine/homebrew-tap.

It also needs a parent issue, as the description says. Requesting changes for the split and the install doc.

[kevincodex1]

hello @PierrunoYT thanks for this. please rebase to main branch, we've already successfully switch from @gitlawb/zero to @twigpine/zero please make another sweep if I forgot something

[PierrunoYT]

@kevincodex1 @Vasanthdev2004 Rebased onto main (8c4e759) as b7bbaeb, one commit. I re-applied the rename to current main instead of hand-merging the 13 conflicts, so main's newer content is kept as-is. The sweep picked up the Gitlawb/zero references main added since (657 files carried one). The npm side is main's @twigpine/zero move, untouched.

Changes beyond the plain rename, following Vasanthdev2004's review:

• packaging/homebrew/zero.rb names Twigpine/homebrew-tap.
• docs/INSTALL.md keeps go install github.com/Gitlawb/zero/cmd/zero@latest, with a note that the Twigpine path works once a release is tagged with the new module path.
• X-AIMLAPI-Integration-Repo stays Gitlawb/zero.

What still says Gitlawb: the AIMLAPI header and DefaultPartnerName, LICENSE, the GitLawb OpenGateway provider, CHANGELOG.md history, the @gitlawb/zero migration notes and legacy detection, test fixtures, and one comment in internal/zerogit ("the convention used across Gitlawb tooling").

The parent issue is #1129; I've updated the description to link it.

@kevincodex1, two calls this needs from you:

1. Go module path: this PR moves go.mod to github.com/Twigpine/zero. Once it lands, every open PR that adds an import or a new Go file needs the same rename before it compiles. Should it go in now, or should I take the module path out and land the rest first?
2. AIMLAPI attribution: should X-AIMLAPI-Integration-Repo (and DefaultPartnerName = "Gitlawb") change to Twigpine? I've left both as they are until you say.