test/prompts-etag.test.ts proves the prompts etag moves with its sources and is never shared across viewers #9250

This adds tests for the prompts etag in test/prompts-etag.test.ts. It doesn't cover one of the issue's cases, because the listing never reads repository files. src/http/api/prompts.ts is unchanged and src/http/api.ts is untouched. bun x tsc --noEmit is clean and the file's 5 tests pass. I did not run scripts/gate.ts or any other test file.

What the tests cover

• Add, edit, remove: the test from #9221 already proved that adding, editing and removing a source each move the tag, so I left it.
• Default-branch pushes: new test. Several commits to the default branch, including prompts/today.md and README.md, leave the tag unchanged and a repeat still gets 304.
• Two admins: new test. Bob is admin of bob/box and Ada of ada/box, and their bodies differ. Their tags differ, with Bob's repo both empty and with a source of its own. Ada's tag sent to Bob's route gets 200, not 304.

The prompt-file case is not tested GET …/prompts builds its body from prompt_source rows only, so a push to the default branch cannot change it. The issue asked that a push changing a prompt file move the tag, and that cannot happen here. I tested the opposite: pushes leave the tag steady. That is the right behaviour for this endpoint.

Constant-etag check I temporarily changed weakEtag(text) to weakEtag("x") in src/http/api/prompts.ts, ran the file, then restored it with git checkout.

• Failed: the add/edit/remove test and the two-admins test.
• Still passed: the push test and the 200/304/headers test. A constant tag also holds steady, so a "tag stays the same" case cannot fail under it. The push test's "unchanged" half is a regression guard, not a mutation-killer.

Tests for Bob's repo Bob has no make_it_yours ability, so the actions-level createRepo refuses him with not_member. The test creates his repo through the core createRepo, and FORGE_CELLS=off is set for the file.

Closes #9241

This adds tests for the prompts etag in test/prompts-etag.test.ts. It doesn't cover one of the issue's cases, because the listing never reads repository files. src/http/api/prompts.ts is unchanged and src/http/api.ts is untouched. bun x tsc --noEmit is clean and the file's 5 tests pass. I did not run scripts/gate.ts or any other test file.

What the tests cover

• Add, edit, remove: the test from #9221 already proved that adding, editing and removing a source each move the tag, so I left it.
• Default-branch pushes: new test. Several commits to the default branch, including prompts/today.md and README.md, leave the tag unchanged and a repeat still gets 304.
• Two admins: new test. Bob is admin of bob/box and Ada of ada/box, and their bodies differ. Their tags differ, with Bob's repo both empty and with a source of its own. Ada's tag sent to Bob's route gets 200, not 304.

The prompt-file case is not tested GET …/prompts builds its body from prompt_source rows only, so a push to the default branch cannot change it. The issue asked that a push changing a prompt file move the tag, and that cannot happen here. I tested the opposite: pushes leave the tag steady. That is the right behaviour for this endpoint.

Constant-etag check I temporarily changed weakEtag(text) to weakEtag("x") in src/http/api/prompts.ts, ran the file, then restored it with git checkout.

• Failed: the add/edit/remove test and the two-admins test.
• Still passed: the push test and the 200/304/headers test. A constant tag also holds steady, so a "tag stays the same" case cannot fail under it. The push test's "unchanged" half is a regression guard, not a mutation-killer.

Tests for Bob's repo Bob has no make_it_yours ability, so the actions-level createRepo refuses him with not_member. The test creates his repo through the core createRepo, and FORGE_CELLS=off is set for the file.

This pull adds tests that the prompts etag moves with its sources and is never shared between differing bodies. It changes only test/prompts-etag.test.ts. src/http/api/prompts.ts and src/http/api.ts are untouched. bun x tsc --noEmit is clean and the file's 5 tests pass. I did not run scripts/gate.ts or any other test file.

Cases

• Add, edit, remove (the test from #9221): each moves the tag.
• Default-branch pushes: several commits, including prompts/today.md and README.md, leave the tag unchanged and a repeat gets 304. In response to review, the same test now adds a source after the pushes and asserts the tag differs from the earlier one. That line makes the case fail under a constant tag.
• Two admins: Ada on ada/box and Bob on bob/box see different bodies and get different tags. Ada's tag sent to Bob's route gets 200, not 304.

Not applicable The issue's case that a push changing a prompt file moves the tag does not apply. GET …/prompts is built from prompt_source rows only and never reads repository files, so no push can move the tag. The push test covers the opposite: pushes leave it unchanged.

Constant-etag check I temporarily changed weakEtag(text) to weakEtag("x") in src/http/api/prompts.ts and ran the file. I restored it afterwards with git checkout.

• Fail: add/edit/remove, pushes-leave-the-tag-alone, and two-admins.
• Still pass: the 200/304/headers test, which was not one of the issue's cases, and the access-refusal test, which checks that no tag is sent.

Bob has no make_it_yours ability, so the test creates bob/box through the core createRepo. FORGE_CELLS=off is set for the file.