Goose 遷至 AAIF，新 Flisk 安裝路徑仍有名稱差異

Two projects renamed their front door in the same year, and an agent will follow the old URL of both. Goose's announcement is public and finished. Flisk's is a name split you can see in the install path, the site, and older DEV posts. Treat them as two checklists. Do not merge them into one "migration."

Goose: the announcement with a date

On 7 April 2026 Michael Neale wrote that Block had donated goose to the Agentic AI Foundation, alongside MCP and AGENTS.md. The operational changes in that post are small:

Docs: goose-docs.ai. Old doc links redirect. Bookmarks still need an update.
Code: github.com/aaif-goose/goose, including related repos in the aaif-goose org. block/goose redirects, which hides the break until a script clones the old org and fails in CI.
Remote: git remote set-url origin git@github.com:aaif-goose/goose.git
Everything else in that post: same project, same community, same mission. Still open source. Still the same agent.

The foundation itself was announced on 9 December 2025. April is when the repo and docs actually moved. Today's AAIF note (four new projects, 10 total) does not move Goose again.

If your Flisk repo has a Goose recipe, the failure looks like this: the recipe curls a block/goose release asset, or a skill links to the old docs path, and the redirect works in a browser but not in the script. Point the recipe at aaif-goose/goose and at goose-docs.ai. Then stop. You do not need a new Flisk stack to finish that rename.

flisk.sh: the rename you can see without a press release

A Rebranding discussion was opened on 21 October 2026 by odykyi in the flisk-sh announcements category (discussion 1790). I am not going to invent the body of that thread. The public surface is enough to write the cutover, and it disagrees with itself in places.

What is consistent:

Site and install host: flisk.sh. The headline is flisk up, not a deploy, not a Compose file you maintain.
Package people are told to install: @flisk-sh/flisk.
Repo people are sent to: github.com/flisk-sh/flisk.
Older posts and some README lines still say tdk, tdk up, and tdk-landscape/tdk-cli-core.
A 22 October DEV post from the project says the binary on the site today is flisk, and that older posts say tdk.
Bind address, if you override it, is still TDK_BIND_ADDRESS. The env name did not get the new brand.

What you should verify on the machine, not in a blog:

npm install -g @flisk-sh/flisk
flisk --version
command -v flisk
command -v tdk
flisk --help | head

If npm install -g @flisk-sh/flisk puts tdk on your PATH and not flisk, believe the binary, not this post. A 21 October DEV note already flagged that the README and the site do not say the same thing about the command name. An agent that "fixes" that by rewriting .autogenerated/ will lose the fix on the next generate.

The cutover order

Do Goose first. It does not touch containers.

Update clones, recipes, and doc links to aaif-goose/goose and goose-docs.ai.
Confirm goose configure still talks to the provider you pay. The April post did not change providers.
Add .gooseignore for .autogenerated/ and .env before you let that agent into a Flisk repo.

Then Flisk, on one stack, not the monorepo.

flisk doctor
flisk up shop --dry-run
flisk config verify

doctor is the machine. dry-run is the URL list with no containers. config verify is the drift check: generated files must match what the CLI would write. If verify fails, the fix is to regenerate from service.json, not to patch the Dockerfile so the names tdk and flisk both appear.

Node.js 22.12 or newer. Docker. Tilt. macOS and Linux start the stack directly. Native Windows can inspect. Starting the stack there needs Ubuntu on WSL2. Those requirements did not change because the banner changed.

What an agent should be told, in four lines

Goose lives at github.com/aaif-goose/goose. Docs at [https://goose-docs.ai/](https://goose-docs.ai/).
Flisk lives at [https://flisk.sh/](https://flisk.sh/) and github.com/flisk-sh/flisk. Package @flisk-sh/flisk.
Run `flisk --help` and use the binary that exists. Do not assume `tdk` and `flisk` are aliases.
Never edit `.autogenerated/`. Languages: python, go, rust, node. There is no goose language id.

Put that in .goosehints. It is the announcement, compressed into the only behavior that matters on a laptop.

What not to announce

Do not write that Flisk joined AAIF. No such announcement exists.
Do not write that tdk is deleted. Old docs, the bind-address variable, and at least one README sentence still use it.
Do not write a migration guide for discussion 1790 until you have read the thread. The link is above. The public install path is the part you can ship today.

Goose source: goose has a new home, 7 April 2026. Flisk surface: flisk.sh, one service.json, discussion 1790.