Repository navigation
Description
Goal
After this phase the "Compute instructions" dialog on dataset pages tells the truth: how to request compute access, how to run a job on this dataset with the nemar compute commands, and where to see it afterwards.
It no longer points at an s3://nemar/... prefix or at the Neuroscience Gateway for a one-click flow that never shipped, and website#6 no longer carries the NSG connector as a pending deliverable.
Routing
- Readiness: expand. The planner reads Phase D3: User job submission and nemar compute submit nemar-cli#2024's merged CLI (
nemar compute submit --help-all, the flag names,--dataset <id>@<version>form, the access-request command) and the merged Phase E1: Compute access card #494 to Phase E3: Job page #496 pages, and quotes the real commands. The plan must decide: the new button label, whether the NSG route is dropped (default: drop it, because NEMAR compute replaces the dead S3-prefix instructions and the about page keeps describing the partnership) or kept as one neutral sentence, what the dialog shows for a dataset with no published version or no public data-plane copy (compute reads public datasets only), and how the install step is worded. - Implementer: Sonnet
- Opus checkpoint: none
- Depends on: Phase E3: Job page #496, Phase D3: User job submission and nemar compute submit nemar-cli#2024; Unblocks: the epic check
- Repository and base branch: nemarOrg/website, epic branch
feature/issue-#493-epic-compute-web
Scope
In: the compute dialog and its button in src/components/ActionBar.astro, a pure instruction builder with tests, the dialog's script hook, the website#6 retarget.
Out: the Download dialog (it already lists the local and file routes; do not copy them into the compute dialog); the about page's description of the SDSC and NSG partnership (a separate wording decision for the owner once compute is live); submitting jobs from the page.
Design references
Design section 7 (CLI forms: nemar compute request-access, nemar compute submit ... --dataset nm000104, status|logs|results|cancel, the specification and inline header), section 1 (compute access is requested once; limits are the owner's).
Closest code: src/components/ActionBar.astro (the Download dialog's dl-cmd rows with data-copy-text and installUrl; the current compute dialog and its data-compute-stub script at the foot), src/lib/host.ts (appUrl for a link from the marketing host to the app host), src/lib/use-this-data.ts (a tested builder of command strings from dataset facts), src/lib/data-base.ts.
Changes
src/lib/compute-instructions.ts(pure): from{ datasetId, version }build the command rows (request access; submit a script against<id>@<version>; a folder with an entry file; list and status), each as a label, a command and a one-line explanation; with no version it returns anot_availableresult that names why. Quote nothing that is not in the merged CLI's help. Tested with the shapesActionBaris given.src/components/ActionBar.astro: replace thedata-compute-dialogbody. Contents: one sentence on what NEMAR compute is (jobs run on a supercomputer under NEMAR's allocation; access is requested once and an admin grants it; the first step is a link to Settings viaappUrl("/settings#compute-access", host)); the command rows with the Download dialog's copy buttons and styles; a link to the person's compute page (appUrl("/compute", host)) and to the CLI install page (installUrl); a link to the compute terms page once published, and the same link text only then; limits and balance live innemar compute limitsandnemar compute balance, not as numbers in the dialog (they are the owner's policy and change without a deploy). Remove thes3://nemar/{datasetId}prefix text, thenpm install -g nemar-cliblock, the "coming soon" note and thewebsite#6link. Renamedata-compute-stubto a name that is not a stub and update the script that opens the dialog.- Do not repeat the Download dialog's local and file routes; link to it if the planner wants a pointer.
- Anonymous deposits and datasets with no reachable data-plane copy: show the not-available text from the builder rather than commands that would fail.
- Retarget website#6 ("Phase 5: Live-features architecture + cutover") with
ghat implementation time: edit its body so the NSG connector deliverable and the.context/nsg_connector_architecture.mdreference are struck as superseded by Epic: Website compute surfaces #493 (website) and Epic: Third-party compute: access, user API, nemar compute, partner contract nemar-cli#2021 (nemar-cli), leave the viewer, accessibility, performance and cutover deliverables untouched, and add a comment naming this pull request. Do not close the issue unless every remaining deliverable is verified done; say in the PR what was checked. The dialog's old link to Phase 5: Live-features architecture + cutover #6 disappears with the "coming soon" note. - Capture a screenshot of the new dialog in light and dark for the PR description.
Tests (write these first)
compute-instructions.test.ts: a dataset with a version yields the rows with the id and version in the submit command; no version yieldsnot_available; ids of each band (nm,ds,on,xx) pass through unchanged; no row containss3://,npmornsgportal. Fails if the old S3 prefix returns.- A parity test (pure) that the command names in the builder appear in a captured
nemar compute --help-allfixture from the merged CLI, so a renamed flag is caught: the fixture is real CLI output with the capture command in the test file. bun run buildsucceeds and a grep of the built dataset page forwebsite/issues/6ands3://nemarfinds nothing.- Browser check on a dataset page with a version and one without: the dialog opens from the button, copy buttons work, the Settings and compute links go to the app host from the marketing host and stay relative on the app host, both themes, phone width, Escape closes, focus returns to the button.
Acceptance criteria
- No instruction in the dialog works only by accident of an old backend: each command exists in the merged CLI.
- No numbers from the owner's policy are hard-coded.
- The dialog is not shown with commands for a dataset the data plane cannot serve.
- website#6 is retargeted and its remaining deliverables untouched.
Gates
bun run typecheck && bun run lint && bun run test && bun run build; then the browser check.
Rules that bite here
- The data-plane rule: never send a person to a storage URL or an S3 prefix; the stable routes are the data plane and the CLI.
- Scoped Astro styles do not cross components: the Download and compute dialogs share class names only because both live in
ActionBar.astro. - Do not state limits, prices or allocation sizes: they are the owner's and may change.
- Anonymous deposits must not gain a route that discloses their repository (the ActionBar's
ghCloneUrlrule). - Close issues by hand;
Closes #Ndoes nothing onstaging.
Escalate to the owner if
- The owner wants NSG kept as an option, or wants the about page's partnership text changed now.
- The compute terms page is still unpublished at release time and the dialog's terms link would 404.
When merged
Update the epic issue and AGENTS.md's architecture map; confirm in the epic issue that website#6 was retargeted and what remains open on it.
Activity
neuromechanist commentedon Nov 7, 2026
Plan: Phase E5, replace the dataset page Compute dialog and retarget website#6
Planner output for the Sonnet implementer. Everything below was read from the merged code: the website epic branch
feature/issue-#493-epic-compute-web(E1 and E2 merged, up to442be8b) and the nemar-cli Epic D branch ate0685a25(D1 to D4). Where this plan and the issue text disagree, the merged code is the fact and the difference is called out.0. Findings that change the issue's assumptions
src/pages/dataset/[id].astrois a marketing-host page withCache-Control: public, s-maxage=300, and the session cookie is scoped to the app host (ADR 0006). So the dialog is one state-agnostic dialog; the five states are handled by sending the person to the surfaces that do know (Settings,/compute, the CLI), not by branching the markup. A client-side probe is impossible (no cookie on that host) and a per-visitor server render would break the edge cache.nemar compute jobs. The merged command isnemar compute list. The full set isbalance, cancel, limits, list, logs, queue, request-access, results, status, submit(fromnemar compute --help-all). Design section 7 and this issue's wording ("list and status") are right; anyjobsin older text is not.--dataset.nemar compute submitrefuses a versionless dataset: "A dataset needs its version, like nm000104@1.0.2, so the job can be run again on the same data." The page's selected version therefore goes into the command.POST /compute/jobsruns the same gate the pipelines use (resolveRun): the dataset must be active, public, not anonymous, first published, not withdrawn or tombstoned, have a version tag, and be a realnm(below the reserved fixture band) orondataset. Sandbox, exemplar anddsids are refused. The backend answers with onedataset_not_eligible("A dataset the job names is not available to compute.") and does not say which term failed. There is no public read that exposes eligibility (see section 9, issue A2)./compute/*route needs a credential. The only way for a marketing-host page to know "compute is open" is the existing build-time rule from ADR 0030 (computeRequestsOpen(COMPUTE_REQUESTS_ENABLED, apiBase())). Reuse it; do not invent a second switch (section 5)..context/nsg_connector_architecture.mddoes not exist in the repo; it is only text in Phase 5: Live-features architecture + cutover #6's body.s3://nemar) would fail for the wrong reason.src/lib/use-this-data.ts:526legitimately renderss3://nemar/<id>/zarr/{store.zarr}in the Use this data section of the same page. Scope the grep to the compute dialog element only. Also the site builds withoutput: "server", so there is no built HTML to grep; the check is a source scan plus acurlagainst the dev server (section 7)./settings#compute-access,/compute). They are navigation only and render nothing from compute on the marketing host. The ADR 0030 addendum for E5 must say so (section 6).1. What the CLI actually offers (quoted, so the dialog invents nothing)
From
bun run src/index.ts compute <cmd> --help-allate0685a25:nemar loginnemar compute request-access [--purpose <text>] [--accept-terms]nemar compute balancenemar compute limitsnemar compute queuenemar compute submit [path] [args...]--dataset <id@version>"A dataset the job reads (repeatable), like nm000104@1.0.2". Help examples:nemar compute submit analysis.py --wait;nemar compute submit ./study --entry run.py --dataset nm000104@1.0.2 --cores 8 --mem 16G --time 2h;nemar compute submit analysis.py --dry-run. "--dry-run packs and scans and prints what would be sent, and sends nothing about the job (it needs no sign-in)." "Running submit again makes a SECOND job and a second hold." "--wait follows the job until it ends. Ctrl-C stops waiting and does NOT cancel the job." Resource flags (--partition --nodes --cores --mem --gpus --time) exist and have defaults.nemar compute list [--state --limit --all],status <job>,logs <job> [--tail n]nemar compute results <job> [--download <dir>] [--renew]nemar compute cancel <job> [--yes]Access states (website
COMPUTE_ACCESS_STATES, mirrored from nemar-cli):none, requested, active, suspended, denied, revoked. The CLI's refusals at submit areno_compute_access("Your account does not have compute access.") andsuspended("Compute is paused for your account."),insufficient_balance,over_concurrency,dataset_not_eligible,version_not_found,version_untagged,too_many_files.How a job reads a dataset: the job names
id@version; the platform stages that version from the data plane before the entry runs. The CLI help says nothing about where the files appear inside the job or where outputs go, so the dialog does not say. That is a gap in the CLI's help, filed as nemar-cli issue A3 (section 9), not filled in here.2. Decision: the dialog, per access state
One dialog, same markup for every visitor. It never claims the visitor has access. The per-state behavior lives where the state is known:
nemar login; the Settings and compute links go to the app host, which sends them to sign-in/computeredirects to/login?next=/compute; the CLI says "not signed in"none)/settings#compute-accessand the commandnemar compute request-accesssubmitis refused with "Your account does not have compute access."requested/computeshow "An admin is reviewing your request." (compute_access.requested.*); asking again does nothingactive/computeshows balances and the jobs list;nemar compute balancesuspended/computeand Settings showcompute_access.suspended.body;submitsays "Compute is paused for your account."deniedorrevokedcompute_access.closed.body: answered, cannot be asked againA single sentence in the dialog points at this: "Where your access stands is on your compute page" with the
/computelink (label from the existing keycompute_access.granted.link, "Open your compute page"). The CLI half isnemar compute balance("works in every access state").3. Decision: dialog content and layout
Button: keep the label "Compute instructions". It stays true (this is instructions, the one-click flow never shipped), it does not suggest a launcher, and it needs no copy churn. Only the hook changes:
data-compute-stubbecomesdata-compute-open; the CSS class.compute-dialogis shared with the Download dialog and the cite dialog comments and is not renamed.Dialog (
<dialog class="compute-dialog" data-compute-dialog aria-labelledby="compute-dialog-heading">,<h2 id="compute-dialog-heading">Compute on this dataset</h2>),readystate:compute_access.section.lede("A separate grant from upload access. An admin reviews each request against export-control and local-jurisdiction rules and the purpose you state, and a grant lets you use compute within the limits an administrator sets."). No other sentence about what access means.dl-cmdrow (<pre><code>plus.dl-cmd__copywithdata-copy-text, so the existing delegated copy handler is reused unchanged):installUrl(the existing constant; no install command is repeated, which also drops the oldnpm install -g, against the project's Bun rule and a second copy to drift). Row:nemar login.compute_access.request.cta("Request compute access") toappUrl("/settings#compute-access", host). Row:nemar compute request-access. One local sentence: "You ask once, and the request tells you what your account is still missing."nemar compute submit analysis.py --dataset {id}@{version} --dry-run. "A dry run packs and checks your job and prints it. It sends nothing about the job and needs no sign-in."nemar compute submit analysis.py --dataset {id}@{version} --waitand, for a folder,nemar compute submit ./study --entry run.py --dataset {id}@{version}. Local sentences: "Name the dataset with its version so the job can be run again on the same data." "--wait follows the job; Ctrl-C stops waiting and does not cancel it." "What one job may ask for is innemar compute limits; what is left of your balance is innemar compute balance." No flag values or numbers.nemar compute list/nemar compute status <job>/nemar compute logs <job>/nemar compute results <job> --download ./results/nemar compute cancel <job>. Local sentence: "<job>is the idsubmitprints. Your jobs also appear on your compute page." (true: E2's jobs list is merged). Thennemar compute queuewith the shared keycompute_page.queue_note("It describes the queue of the whole platform, not yours, and it is a recent average, not a promise."), which is the only statement about speed.appUrl("/compute", host), labelcompute_access.granted.link) and "Install the NEMAR CLI".How the dataset id is used:
--dataset <id>@<version>with the page'sdatasetIdandversion(the selected version, so a visitor on?v=gets that pin). The id passes through unchanged for every band; the version is validated against^v?\d+\.\d+\.\d+$and passed through as the page holds it (the CLI and Worker accept bare,v-prefixed andlatest; the help example is bare).Honesty rules (all enforced by tests, section 7): the dialog never says compute is free, available, fast or that an allocation will be granted; it states no limit, price, balance or allocation size (they are the owner's and change without a deploy); "an admin reviews" comes from the shared key; every command is in the captured CLI help; it never mentions S3, a storage URL, rclone or the Neuroscience Gateway.
States other than
ready(decided by a pure builder, section 4):closed(compute not open in this build): same dialog shell, no commands. Body is the shared keycompute_access.terms_unpublished.body("Compute access is not open yet: the compute terms are not published. Please check back later.") plus one local sentence: "To work with this data now, use one of the routes in Download." No link to the old routes; no copy of them.not_available(anonymous deposit, unpublished or no version, id outsidenm/on, malformed version): no commands, one sentence: "NEMAR compute cannot read this dataset." and the same Download pointer. One user-facing sentence for every reason, matching the backend, which also does not say why. The reason word exists only in the builder's result for tests. Anonymous deposits get no route that discloses a repository: the dialog never readsgithubUrl.4. Files and the pure builder
New / changed (Sonnet implementer; atomic commits, tests first):
scripts/capture-compute-cli-help.mjs:NEMAR_CLI_DIR=<Epic D checkout> bun scripts/capture-compute-cli-help.mjsrunsbun run src/index.ts --no-color <cmd> --help-allforloginandcomputeplus each of the ten subcommands, writestest/fixtures/compute/cli-help/<name>.txt, and records the nemar-cli commit in a header comment in anindex.json. Same style ascapture-compute-read-fixtures.mjs. Real output, never hand-written.src/lib/compute-instructions.ts(pure, no imports from Astro):buildComputeInstructions(input: { datasetId: string; version: string | null; anonymous: boolean; unpublished: boolean; open: boolean }): ComputeInstructions, a discriminated union:{ kind: "closed" },{ kind: "not_available"; reason: "anonymous" | "unpublished" | "no_version" | "id_band" | "version_shape" },{ kind: "ready"; datasetId; version; steps: Step[] }. Order of precedence:closed, then thenot_availablereasons, thenready.{ id, heading, rows: { label, command, explanation }[] }.commandis the exact copyable string. A small exportedcommandWords(command)returns{ sub: string[]; flags: string[] }for the parity test.id_bandrule:^(nm|on)\d{6}$only. This is a UI pre-filter on facts the page already holds, not a copy of the backend rule; the backend stays the authority (dataset_not_eligible, which the CLI prints). The reserved-band ceiling is deliberately not reimplemented (A2 asks the backend to expose eligibility).src/lib/compute-labels.ts: add adatasetDialoggroup for the local labels (title, step headings, row labels, the short explanations, link labels, the two fallback sentences). Update the file header (it says "of the /compute page"). No sentence about access or limits is typed here.src/components/ActionBar.astro: new propsanonymous: booleanandunpublished: boolean(the page already holdsanonymousDepositandunpublished;githubUrl === nullis no longer used as a proxy). Frontmatter computesopen = computeRequestsOpen(COMPUTE_REQUESTS_ENABLED, apiBase())and the builder result, plusappUrl(path, Astro.url.hostname)for the two links. Replace the compute dialog body; delete.compute-dialog__soon*CSS; rename the button hook and the script selector; addaria-labelledby; give each new<pre>tabindex="0"(scrollable region on a phone). No other dialog is touched.src/pages/dataset/[id].astro: passanonymous={anonymousDeposit}andunpublished={unpublished}toActionBar.AGENTS.mdarchitecture map getscompute-instructions.tsand thecli-helpfixtures; ADR 0030 gets an addendum (section 6).No new
account-copy.tskey is needed (section 6), so nemar-cli'sshared/contract/account-copy.tsand the drift test are untouched.5. Decision: degradation when compute is off or the release gate is not met
Reuse the one switch ADR 0030 already owns:
computeRequestsOpen(COMPUTE_REQUESTS_ENABLED, apiBase()). In the production build it isfalseuntil the owner publishes the terms and flipsCOMPUTE_REQUESTS_ENABLEDin a reviewed change; against any non-production backend (staging, local) it istrue. The consequences are the ones we want:/computeshows thecloseddialog, never commands that fail. This is the ADR 0026-style gate, expressed as the existing flag instead of a request; the epic's "check with a request first" step before promotion stays.A probe (like ADR 0026's) was rejected: no public compute route exists, the marketing host has no session, and a per-render upstream call would hit the cached page's hot path. If nemar-cli adds a public availability read (A1), a later change can replace the constant for both Settings and this dialog; ADR 0030's hand-off already describes that for Settings.
6. Copy: shared keys vs local labels
Rule (ADR 0030, nemar-cli ADR 0045): a sentence about what access is, what a state means, or what a limit is comes from
account-copy.ts; a label or a description of this surface's own layout is local.compute_access.section.lede(what access is),compute_access.request.cta(link label),compute_access.granted.link(compute page link label),compute_access.terms_unpublished.body(closed state),compute_page.queue_note(queue is not a promise).COMPUTE_LABELS.datasetDialog): the intro sentence, step headings, row captions, the explanations that paraphrase the quoted CLI help, the install link label, the two fallback sentences. Each explanation maps to a quoted help line in section 1.compute-instructions.tsand the compute dialog block ofActionBar.astrofor long sentences outside the labels file and the copy table.computeRequestsOpenas its gate; (3) the Neuroscience Gateway route is dropped from the dialog and the s3 prefix instructions are removed for good (data-plane rule); (4) amends the sentence "the marketing host links to docs, not to a compute surface": from this phase the dataset dialog links to the app host's/settings#compute-accessand/compute, navigation only; (5) the id-band pre-filter is interim and the backend'sdataset_not_eligibleis the authority. Receipts: website#498, Epic: Website compute surfaces #493; nemar-cli#2021, #2024.7. Tests (written first, Vitest, no mocks)
src/lib/compute-instructions.test.ts(pure, real-shaped inputs, the exact shapesActionBarpasses): a publishednmdataset with version yields the exact command strings with id and version; ids of each bandnm,onpass through unchanged andds,xxgivenot_available/id_band; null version, an unpublished flag, an anonymous flag, and a malformed version (abc,1.0) each give their own reason;v1.0.2and1.0.2both pass;open: falsegivesclosedeven for a good dataset; and no string in any result (commands, labels, explanations) containss3://,npm,nsgportal,rclone,aws,http, a digit-bearing limit (--cores,--mem,--time,--partition,--gpus) or the words free, fast, guaranteed, unlimited. Mutation check: reintroduces3://in a label and the test must fail.test/compute-instructions-cli-parity.test.ts: readstest/fixtures/compute/cli-help/*.txt(capture command named in the file header) and asserts, for every command in everyreadyrow, that each subcommand is listed incompute.txtand each long flag appears in that subcommand's help text, and that theid@versionexample form appears incompute-submit.txt. Mutation check: change--datasetto--dataorlisttojobsand the test fails. Also asserts the ten subcommand names the dialog may use are a subset of the fixture's command list.test/compute-dialog-ui.test.ts(source scan, likecompute-dashboard-ui.test.ts):ActionBar.astrohas nodata-compute-stub,s3://,nsgportal,npm install,website/issues/6,compute-dialog__soon, "coming soon"; it containsdata-compute-open,aria-labelledby="compute-dialog-heading", theappUrl("/settings#compute-access"andappUrl("/compute"calls,computeRequestsOpen(COMPUTE_REQUESTS_ENABLED, and does not readgithubUrlinside the compute block; everyACCOUNT_COPY[...]key it uses exists;dataset/[id].astropassesanonymousandunpublished.flags.test.tsalready pins the production-closed default; add one assertion that the dialog's gate is that function (covered by test 3).bun run typecheck && bun run lint && bun run test && bun run build.curl -s localhost:4321/dataset/<id> | sed -n '/data-compute-dialog/,/<\/dialog>/p'contains none ofs3://,nsgportal,website/issues/6,npm install; the same with the production default shows only theclosedtext.Browser check (real browser, both themes, desktop and phone width ~390 px):
nmversion, non-production backend: button opens the dialog; steps show the page's id and version; copy buttons copy exactly the row text (including the multi-line row) and show "Copied"; the clipboard text has no placeholder other than<job>.nm099998on staging, never published under a name), and anxxexemplar: thenot_availablesentence, no commands, no repository link.PUBLIC_API_BASE_URL):closedtext, no commands.#compute-accesshash survives the sign-in redirect and record the result (do not fix here).<pre>scrolls inside itself and is keyboard-focusable; copy buttons are at least 44 px tall on touch; 16 px gutter.readydialog in light and dark for the PR description.8. Removal of the old content and the retarget of website#6
Remove from
ActionBar.astro: the NSG step and itsnsgportal.orglink, thes3://nemar/{datasetId}text, thenpm install -g nemar-cliblock, "Just the files" (duplicates the Download dialog's direct route), the.compute-dialog__soon"coming soon" note and the link to website#6, the CSS for.compute-dialog__soon*. Nothing else in the repo referenced these (grepfordata-compute-stub,nsgportal,issues/6finds onlyActionBar.astro;s3://nemarelsewhere belongs to Zarr/Use this data and stays). No dead test exists for the old dialog..context/website-bible.mdline about NSG describes the partnership for the about page and stays (the issue puts the about page out of scope).website#6 (
Phase 5: Live-features architecture + cutover), exact edit, done by the implementer withghafter the PR is open:> **Retargeted (website#498):** the NSG connector deliverable is superseded by NEMAR compute, tracked in nemarOrg/website#493 (web) and nemarOrg/nemar-cli#2021 (backend and CLI). The other deliverables were closed out or overtaken on 2026-08-03, see the comments. The dataset page Compute dialog no longer links here.Design doc .context/nsg_connector_architecture.md: ...in~~ ~~and appendSuperseded by nemarOrg/website#493 and nemarOrg/nemar-cli#2021.Wire Vis / ~~Compute~~ placeholder UI ...strike only the word Compute and append(Compute: superseded, see above).or NSG connector.nemar computeand no longer links here. This issue stays open until that dialog reaches production."stagingtomainrelease. The driver closes it by hand after the release, oncecurlof a production dataset page shows nowebsite/issues/6and the owner agrees (open question 3). Record in the PR what was verified: the other deliverables are already recorded as done or superseded in Phase 5: Live-features architecture + cutover #6's comments; no Lighthouse run against the original thresholds was ever made and the owner's comment says that belongs in its own issue if it still matters.9. What the backend and CLI do not offer (issues to file in nemarOrg/nemar-cli, not synthesized)
requests_open,terms_published,terms_version) so marketing-host pages and Settings can drop the bakedCOMPUTE_REQUESTS_ENABLEDconstant and the terms-version transcription.resolveRun, so the website never copies the band and flag rules. Interim: thenm/onpre-filter above.nemar compute submit --help-alldoes not say where a job finds the staged dataset, where it writes outputs, or what the working directory is, and docs.nemar.org has no compute command page yet (the Epic D notes list it as not shipped). The dialog cannot teach a script author how to read the data until this is documented. Ask for the help text and a docs page; once the docs page exists, add a "How jobs work" link to the dialog.includeglob list per dataset, but--datasetand the inline header expose onlyid@version. The dialog does not mention subsets.10. Risks
nmreserved fixtures, withdrawn, tombstoned). The CLI prints the backend's honest sentence; fixed properly by A2.COMPUTE_REQUESTS_ENABLEDbut the production API is not serving/compute, the dialog opens with commands that fail. Same risk as the Settings form and the same pre-promotion request check.<job>placeholders are copied literally. Accepted and labeled.#compute-accessanchor may be lost across the sign-in redirect for signed-out visitors; the browser check records it.appUrl(already tested) plus reading the production HTML after release.11. Open questions for the owner
nmandonids acceptable until A2, or should the dialog show commands for every published dataset and let the CLI refuse? Default: pre-filter.12. Routing note
Implementer: Sonnet. No Opus checkpoint (nothing here touches authorization or money; the dialog only prints commands). Review: one Sonnet pass over the diff, with the parity and honesty tests as the focus. Depends on: nothing in code from #496 (the dialog links only to
/compute, whose jobs list is merged in E2); the CLI's command names are merged. When merged: update the epic issue,AGENTS.md's map and ADR 0030, and confirm in the epic what the #6 edit was.neuromechanist commentedon Nov 7, 2026
Merged in #506 (ea21483). website#6 body retargeted and left open until the production release.