Project profile: answer the remaining TODO(ask) items #1042

New issue

Closed

opened 2026-10-03 13:54:22 +00:00 by claude-bot · 1 comment

claude-bot commented

2026-10-03 13:54:22 +00:00

Collaborator

Follow-up to #1037 / PR #1038. The ## Project profile in CLAUDE.md still has eight TODO(ask) lines. Each has a recommendation below and needs the owner's answer; once answered, one small PR fills them in.

#	Item	Recommendation	Basis
1	`Repo.required checks`	`CI / *` (every CI job)	The rule set on 2026-06-24 used that glob. `claude-bot` cannot read branch protection, so confirm it in the UI.
2	`Release.prerelease changelog`	"Prereleases are not used." If one is ever cut, it gets its own `## [X.Y.Z-rcN]` heading, or `release.yml` publishes "No changelog entry found".	No tag containing `-` has ever been made.
3	`Release.prod deploy`: source build or images?	Record source build only, which is true today (`git pull --ff-only && docker compose up -d --build` in the prod deploy dir). Moving prod to the published images is a separate decision.	The 4.4.0 / 4.4.1 deploys.
4	`Release.verify`: version without shell access	`GET /api/meta` returns `{"version":"4.4.1"}`, unauthenticated by design (`main.py`).	Checked on dev directly and through `questboard-dev.rhoving.com`.
5	`Preflight.generated artifacts`: list `evals.synthetic_session verify`?	No. Keep "none", noting that CI's synthetic-session job checks the clips.	It needs the harness image. Preflight on a machine without Docker would mark it NOT CHECKED, the verdict would be INCOMPLETE, and `/qb-verify` (which needs READY) could never go green.
6	`UI.base URL`: a long-lived dev URL?	No. Keep the seeded journeys stack only.	The dev URL needs a real OIDC login and has real users' data; the seeded identities only exist on the journeys stack.
7	`UI.viewports`: a tablet size?	Add 820×1180 (tablet portrait) for render checks only, not as a CI project.	The in-person table (#542) is the likeliest tablet use, and tablet width was the gap noted after the mockup rounds.
8	`UI.key pages`: default app routes	Home `/`, a campaign home, a session page, the table, a wiki article, a character sheet, and `/design`, with ids taken from the seeded demo data.	These are the surfaces the v4.5.0 lanes change most.

Follow-up to #1037 / PR #1038. The `## Project profile` in `CLAUDE.md` still has eight `TODO(ask)` lines. Each has a recommendation below and needs the owner's answer; once answered, one small PR fills them in. | # | Item | Recommendation | Basis | |---|---|---|---| | 1 | `Repo.required checks` | `CI / *` (every CI job) | The rule set on 2026-06-24 used that glob. `claude-bot` cannot read branch protection, so confirm it in the UI. | | 2 | `Release.prerelease changelog` | "Prereleases are not used." If one is ever cut, it gets its own `## [X.Y.Z-rcN]` heading, or `release.yml` publishes "No changelog entry found". | No tag containing `-` has ever been made. | | 3 | `Release.prod deploy`: source build or images? | Record **source build only**, which is true today (`git pull --ff-only && docker compose up -d --build` in the prod deploy dir). Moving prod to the published images is a separate decision. | The 4.4.0 / 4.4.1 deploys. | | 4 | `Release.verify`: version without shell access | `GET /api/meta` returns `{"version":"4.4.1"}`, unauthenticated by design (`main.py`). | Checked on dev directly and through `questboard-dev.rhoving.com`. | | 5 | `Preflight.generated artifacts`: list `evals.synthetic_session verify`? | **No.** Keep "none", noting that CI's synthetic-session job checks the clips. | It needs the harness image. Preflight on a machine without Docker would mark it NOT CHECKED, the verdict would be INCOMPLETE, and `/qb-verify` (which needs READY) could never go green. | | 6 | `UI.base URL`: a long-lived dev URL? | **No.** Keep the seeded journeys stack only. | The dev URL needs a real OIDC login and has real users' data; the seeded identities only exist on the journeys stack. | | 7 | `UI.viewports`: a tablet size? | Add 820×1180 (tablet portrait) for render checks only, not as a CI project. | The in-person table (#542) is the likeliest tablet use, and tablet width was the gap noted after the mockup rounds. | | 8 | `UI.key pages`: default app routes | Home `/`, a campaign home, a session page, the table, a wiki article, a character sheet, and `/design`, with ids taken from the seeded demo data. | These are the surfaces the v4.5.0 lanes change most. |

claude-bot referenced this issue

2026-10-03 14:05:58 +00:00

Prereleases for testing on dev, and both hosts run the published images #1043

claude-bot commented

2026-10-03 14:06:02 +00:00

Author

Collaborator

Owner's answers (2026-10-03): as recommended for items 1 and 4 to 8. Items 2 and 3 are answered the other way:

2. Prereleases will be cut for testing on the dev server.
3. Production switches to the published images.

Both are tracked in #1043, and the profile is filled in by the same PR.

**Owner's answers (2026-10-03):** as recommended for items 1 and 4 to 8. Items 2 and 3 are answered the other way: - **2.** Prereleases will be cut for testing on the dev server. - **3.** Production switches to the published images. Both are tracked in #1043, and the profile is filled in by the same PR.

claude-bot referenced this issue from a pull request that will close it,

2026-10-03 14:13:19 +00:00

Prereleases for the dev server, and the hosts run the published images (#1043) #1044

claude-bot closed this issue

2026-10-03 15:02:34 +00:00