@@ -678,26 +474,11 @@ test.describe("ImportXML", () => {
true
);
- await expectCardGridSlotStates(
+ await expectDisplaySheetSlotStates(
page,
- [
- {
- slot: 1,
- name: cardDocument1.name,
- selectedImage: 1,
- totalImages: 1,
- },
- ],
- [
- {
- slot: 1,
- name: cardDocument3.name, // the cardback specified in XML
- selectedImage: 2,
- totalImages: 2,
- },
- ]
+ [{ slot: 1, name: cardDocument1.name }],
+ [{ slot: 1, name: cardDocument3.name }] // the cardback specified in XML
);
- await expectCardbackSlotState(page, cardDocument2.name, 1, 2); // the project cardback should not have changed
});
test("import an XML and use the project cardback", async ({
@@ -713,9 +494,7 @@ test.describe("ImportXML", () => {
);
await loadPageWithDefaultBackend(page);
- await expectCardbackSlotState(page, cardDocument2.name, 1, 2);
-
- await importXML(
+ await importXMLOnEmptyLanding(
page,
`
@@ -737,26 +516,11 @@ test.describe("ImportXML", () => {
false
);
- await expectCardGridSlotStates(
+ await expectDisplaySheetSlotStates(
page,
- [
- {
- slot: 1,
- name: cardDocument1.name,
- selectedImage: 1,
- totalImages: 1,
- },
- ],
- [
- {
- slot: 1,
- name: cardDocument2.name, // the cardback configured for the project
- selectedImage: 1,
- totalImages: 2,
- },
- ]
+ [{ slot: 1, name: cardDocument1.name }],
+ [{ slot: 1, name: cardDocument2.name }] // the cardback configured for the project
);
- await expectCardbackSlotState(page, cardDocument2.name, 1, 2); // cardback should not have changed
});
// Foreign-order resilience Phase 1 follow-up (issue #324, owner-observed 2026-07-23): a BRAND
@@ -770,6 +534,17 @@ test.describe("ImportXML", () => {
// initialised from the import when nothing was selected before it) and its own gate against
// regressing the "should not have changed" tests above (an EXISTING project cardback is never
// touched by a later import).
+ //
+ // The assertion below was rewritten (2026-07-23, following PR #398's PagePreview orphan-badge
+ // parity fix) to check the /editor sheet's own per-slot corner badge instead of the classic
+ // "Common Cardback" panel - DisplayPage has no equivalent persistent tile (only the
+ // CardbackToolbarButton picker, per this file's own header comment), so the fix's underlying
+ // behaviour (a BRAND NEW project's cardback initialises from the import, orphan or not) is now
+ // observed the same way OrphanRendering.spec.ts's own "b:null" case observes it: the sheet's
+ // `page-preview-slot`, toggled to its back face, showing both the resolved orphan image and the
+ // `orphan-badge` corner treatment (PagePreview.tsx's `orphanLabel`, same testid/text as
+ // Card.tsx's classic-editor badge). Same testid convention, same "Your file" text, kept
+ // consistent with OrphanRendering.spec.ts so the two files don't drift.
test("importing an XML into a brand new project with no cardback yet initialises the Common Cardback panel from the file's own - even an orphan", async ({
page,
network,
@@ -780,7 +555,7 @@ test.describe("ImportXML", () => {
const orphanFrontId = "1FItgPw7VK_Tbv6dMiqdy5zd-jAoEC9mn";
const orphanBackId = "1LrVX0pUcye9n_0RtaDNVl2xPrQgn7CYf";
- await importXML(
+ await importXMLOnEmptyLanding(
page,
`
`
);
- const commonCardback = page.getByTestId("common-cardback");
- await expect(commonCardback.getByTestId("orphan-badge")).toBeVisible();
- await expect(commonCardback).not.toContainText("Card Not Found");
+ const slot = page.getByTestId("page-preview-slot").first();
+ const frontImage = slot.locator("img");
+ await expect(frontImage).toHaveCount(1, { timeout: 45_000 });
+ await expect(frontImage).toHaveAttribute(
+ "src",
+ `https://lh4.googleusercontent.com/d/${orphanFrontId}=h800`
+ );
+
+ // The imported (an orphan here) is this test's own point - toggle to the back
+ // face and confirm the project's cardback initialised from it, including the sheet's own
+ // orphan corner badge (see the comment above).
+ await page.getByRole("button", { name: /Showing: Fronts/ }).click();
+ const backImage = slot.locator("img");
+ await expect(backImage).toHaveCount(1, { timeout: 45_000 });
+ await expect(backImage).toHaveAttribute(
+ "src",
+ `https://lh4.googleusercontent.com/d/${orphanBackId}=h800`
+ );
+ await expect(slot.getByTestId("orphan-badge")).toHaveText("Your file");
});
});
diff --git a/frontend/tests/MatureContentToggle.spec.ts b/frontend/tests/MatureContentToggle.spec.ts
index 5917cd460..abea1ac44 100644
--- a/frontend/tests/MatureContentToggle.spec.ts
+++ b/frontend/tests/MatureContentToggle.spec.ts
@@ -12,28 +12,16 @@ import {
import { test } from "../playwright.setup";
import {
- expectCardGridSlotState,
+ expectDisplaySheetSlotState,
importTextOnEditorLanding,
loadPageWithDefaultBackend,
openSearchSettingsModal,
} from "./test-utils";
-// Proposal H switchover (2026-07-23, issues #231/#272) - /editor now serves the unified
-// sheet+rail page (`DisplayPage.tsx`); the classic grid `ProjectEditor` this file's own setup
-// depends on (via testids/interaction patterns like `front-slot`/`back-slot`/`common-cardback`/
-// the "Add Cards" right-panel dropdown/the classic "Print!" tab, or a component with no rendered
-// equivalent on the new page yet - see issue #272's own tracked parity gaps) is fully unrouted,
-// not just delisted from the nav. Skipped here rather than deleted (component files themselves
-// are untouched, per this swap's own scope) or silently left red - porting this coverage to
-// DisplayPage's DOM is real, non-mechanical work tracked against #272, not done as part of the
-// route swap itself (the owner's directive was to proceed with the swap regardless of the
-// checklist's open items).
-test.beforeEach(async ({}, testInfo) => {
- testInfo.skip(
- true,
- "Proposal H switchover (2026-07-23): tests classic /editor-only UI, now unrouted - see issue #272"
- );
-});
+// Proposal H parity port (2026-07-23, issue #272 wave 1): ported onto the unified /editor page -
+// the Search Settings modal (openSearchSettingsModal) is the same self-contained, unforked
+// component DisplayPage.tsx's own toolbar mounts (see DisplayPage.spec.ts's own precedent test),
+// reachable directly with no other DOM changes needed.
// saving search settings only re-triggers a search when the project has queries to re-run,
// so each test imports one card first
@@ -43,7 +31,7 @@ const loadPageWithOneCard = async (page: any) => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await expectCardGridSlotState(page, 1, "front", cardDocument1.name, 1, 1);
+ await expectDisplaySheetSlotState(page, 1, "front", cardDocument1.name);
};
test.describe("show mature content toggle", () => {
diff --git a/frontend/tests/ReportCard.spec.ts b/frontend/tests/ReportCard.spec.ts
index 26638eefe..08cf9844c 100644
--- a/frontend/tests/ReportCard.spec.ts
+++ b/frontend/tests/ReportCard.spec.ts
@@ -14,32 +14,16 @@ import {
import { test } from "../playwright.setup";
import {
- expectCardGridSlotState,
importTextOnEditorLanding,
loadPageWithDefaultBackend,
+ openDetailedView,
} from "./test-utils";
-// Proposal H switchover (2026-07-23, issues #231/#272) - /editor now serves the unified
-// sheet+rail page (`DisplayPage.tsx`); the classic grid `ProjectEditor` this file's own setup
-// depends on (via testids/interaction patterns like `front-slot`/`back-slot`/`common-cardback`/
-// the "Add Cards" right-panel dropdown/the classic "Print!" tab, or a component with no rendered
-// equivalent on the new page yet - see issue #272's own tracked parity gaps) is fully unrouted,
-// not just delisted from the nav. Skipped here rather than deleted (component files themselves
-// are untouched, per this swap's own scope) or silently left red - porting this coverage to
-// DisplayPage's DOM is real, non-mechanical work tracked against #272, not done as part of the
-// route swap itself (the owner's directive was to proceed with the swap regardless of the
-// checklist's open items).
-test.beforeEach(async ({}, testInfo) => {
- testInfo.skip(
- true,
- "Proposal H switchover (2026-07-23): tests classic /editor-only UI, now unrouted - see issue #272"
- );
-});
-
-const openDetailedView = async (page: any, cardName: string) => {
- await page.getByAltText(cardName).click();
- await expect(page.getByText("Card Details")).toBeVisible();
-};
+// Proposal H parity port (2026-07-23, issue #272 wave 1): ported onto the unified /editor page -
+// ReportCardPanel lives inside CardDetailedViewModal's own "Report" region (ReportBlock,
+// CardDetailedViewBody.tsx), reached the same way the rest of this cluster reaches the modal - see
+// openDetailedView's own module comment (test-utils.ts) for the Browse-mode route and the "Card
+// details" text-collision fix.
const setUpCardAndOpenModal = async (page: any) => {
await loadPageWithDefaultBackend(page);
@@ -47,8 +31,7 @@ const setUpCardAndOpenModal = async (page: any) => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await expectCardGridSlotState(page, 1, "front", cardDocument1.name, 1, 1);
- await openDetailedView(page, cardDocument1.name);
+ await openDetailedView(page, "my search query", cardDocument1.identifier);
};
test.describe("report card flow", () => {
diff --git a/frontend/tests/VotePickers.spec.ts b/frontend/tests/VotePickers.spec.ts
index 0be7dc6f5..25d3cca1f 100644
--- a/frontend/tests/VotePickers.spec.ts
+++ b/frontend/tests/VotePickers.spec.ts
@@ -29,39 +29,15 @@ import { test } from "../playwright.setup";
import {
importTextOnEditorLanding,
loadPageWithDefaultBackend,
+ openDetailedView,
} from "./test-utils";
-// Proposal H switchover (2026-07-23, issues #231/#272) - /editor now serves the unified
-// sheet+rail page (`DisplayPage.tsx`); the classic grid `ProjectEditor` this file's own setup
-// depends on (via testids/interaction patterns like `front-slot`/`back-slot`/`common-cardback`/
-// the "Add Cards" right-panel dropdown/the classic "Print!" tab, or a component with no rendered
-// equivalent on the new page yet - see issue #272's own tracked parity gaps) is fully unrouted,
-// not just delisted from the nav. Skipped here rather than deleted (component files themselves
-// are untouched, per this swap's own scope) or silently left red - porting this coverage to
-// DisplayPage's DOM is real, non-mechanical work tracked against #272, not done as part of the
-// route swap itself (the owner's directive was to proceed with the swap regardless of the
-// checklist's open items).
-test.beforeEach(async ({}, testInfo) => {
- testInfo.skip(
- true,
- "Proposal H switchover (2026-07-23): tests classic /editor-only UI, now unrouted - see issue #272"
- );
-});
-
-// Shared by all three picker suites below (identical across their source files).
-//
-// Proposal H switchover (2026-07-23, issues #231/#272) note: /editor now resolves to the
-// unified page, whose own left rail ALSO carries "Card details" text (offcanvas title, handle
-// button) in addition to CardDetailedViewBody's own "Card Details" heading - a plain
-// getByText("Card Details") (case-insensitive substring by default) matched all three and threw
-// a strict-mode violation. The heading role disambiguates to the one that's actually
-// CardDetailedViewBody's own content, which is what this helper always meant to assert on.
-const openDetailedView = async (page: any, cardName: string) => {
- await page.getByAltText(cardName).click();
- await expect(
- page.getByRole("heading", { name: "Card Details" })
- ).toBeVisible();
-};
+// Proposal H parity port (2026-07-23, issue #272 wave 1): ported onto the unified /editor page.
+// Shared by all three picker suites below (identical across their source files) - the pickers
+// themselves live inside CardDetailedViewModal's own "Printing Tags" region (PrintingTagsBlock,
+// CardDetailedViewBody.tsx), reached the same way the rest of this cluster reaches the modal - see
+// openDetailedView's own module comment (test-utils.ts) for the Browse-mode route and the "Card
+// details" text-collision fix.
test.describe("ArtistVotePicker tests", () => {
test("shows the attribute-voting panel once printing consensus is unresolved, listing candidate artists", async ({
@@ -86,7 +62,7 @@ test.describe("ArtistVotePicker tests", () => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await openDetailedView(page, cardDocument1.name);
+ await openDetailedView(page, "my search query", cardDocument1.identifier);
// longer than the default 5s: showing this panel is gated behind a chain of fetches
// (printing consensus resolves -> CardDetailedViewModal re-renders -> the panel mounts
@@ -124,7 +100,7 @@ test.describe("ArtistVotePicker tests", () => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await openDetailedView(page, cardDocument1.name);
+ await openDetailedView(page, "my search query", cardDocument1.identifier);
const artistPicker = page.getByTestId("artist-vote-picker");
await expect(artistPicker.getByText("Not yet resolved")).toBeVisible();
@@ -163,7 +139,7 @@ test.describe("TagVotePicker tests", () => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await openDetailedView(page, cardDocument1.name);
+ await openDetailedView(page, "my search query", cardDocument1.identifier);
const tagPicker = page.getByTestId("tag-vote-picker");
await expect(tagPicker.getByText("Borderless")).toBeVisible();
@@ -193,7 +169,7 @@ test.describe("TagVotePicker tests", () => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await openDetailedView(page, cardDocument1.name);
+ await openDetailedView(page, "my search query", cardDocument1.identifier);
const tagPicker = page.getByTestId("tag-vote-picker");
// "Borderless" has displayName "Frameless Border" set - shown instead of the raw name
@@ -228,7 +204,7 @@ test.describe("TagVotePicker tests", () => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await openDetailedView(page, cardDocument1.name);
+ await openDetailedView(page, "my search query", cardDocument1.identifier);
const tagPicker = page.getByTestId("tag-vote-picker");
await tagPicker.getByText("Borderless").click();
@@ -259,7 +235,7 @@ test.describe("PrintingTagPicker tests", () => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await openDetailedView(page, cardDocument1.name);
+ await openDetailedView(page, "my search query", cardDocument1.identifier);
await expect(
page.getByTestId("detailed-view").getByText("What's That Card?")
@@ -337,7 +313,7 @@ test.describe("PrintingTagPicker tests", () => {
page,
`my search query${SelectedImageSeparator}${cardDocument1.identifier}`
);
- await openDetailedView(page, cardDocument1.name);
+ await openDetailedView(page, "my search query", cardDocument1.identifier);
const picker = page.getByTestId("printing-tag-picker");
await expect(page.getByText("Not yet resolved")).toBeVisible();
diff --git a/frontend/tests/test-utils.ts b/frontend/tests/test-utils.ts
index a133fec3a..10c29b2d8 100644
--- a/frontend/tests/test-utils.ts
+++ b/frontend/tests/test-utils.ts
@@ -77,6 +77,142 @@ export const importTextOnEditorLanding = async (page: Page, text: string) => {
).not.toBeVisible();
};
+// Card-detail modal ecosystem parity port (2026-07-23, issue #272 wave 1). The classic editor
+// opened the real, unforked `CardDetailedViewModal` (`data-testid="detailed-view"`) by clicking
+// ANY card image in the grid. On the unified `/editor` page that same click behaviour
+// (`showDetailedViewOnClick`, `Card.tsx`) is suppressed everywhere a `cardOnClick` handler is
+// also wired - which is every `EditorCard` mount on this page except one: the Browse-mode catalog
+// tiles `CatalogBrowseResults.tsx` renders have no `cardOnClick` at all, so clicking one still
+// opens the real modal, unmodified. (Sheet slots select the rail instead; Select Version's own
+// candidate tiles select an image instead - neither opens this modal any more.) This helper
+// re-runs the caller's own already-mocked query through Browse mode and opens that result's
+// detail view - the KNOWN fix this whole cluster needed (2026-07-23 triage): the unified page's
+// left rail ALSO renders "Card details" text verbatim, lowercased, in its offcanvas dialog title
+// and edge-handle button (both present in the DOM regardless of viewport/rail state) - a bare
+// `getByText("Card Details")` (case-insensitive substring match by default) hit a 3-way
+// strict-mode collision. Scoping to the modal's own `detailed-view` testid (NOT a heading role -
+// react-bootstrap's `Modal.Title` renders a styled `
@@ -801,8 +576,24 @@ test.describe("ImportXML", () => {
`, not a real heading element) resolves
+// it once, here, for the whole cluster - consolidated out of near-duplicate helpers previously
+// declared separately in ArtistSupportLink/VotePickers/ReportCard/AddCardToFavorites' own spec
+// files (each still assuming the classic grid's plain "click the grid image" flow).
+export const openDetailedView = async (
+ page: Page,
+ query: string,
+ cardIdentifier: string
+) => {
+ await page.getByTestId("display-search-mode-browse").click();
+ await page.getByTestId("display-browse-search-input").fill(query);
+ const tile = page.getByTestId(`catalog-browse-tile-${cardIdentifier}`);
+ await expect(tile).toBeVisible();
+ await tile.locator("img").click();
+ await expect(
+ page.getByTestId("detailed-view").getByText("Card Details")
+ ).toBeVisible();
+};
+
+export const closeDetailedView = async (page: Page) => {
+ await page.getByTestId("detailed-view").getByLabel("Close").click();
+ await expect(page.getByTestId("detailed-view")).not.toBeVisible();
+};
+
+// Proposal H parity port (2026-07-23, issue #272 wave 1): the classic grid's `front-slot`/
+// `back-slot` testids (and the "N / M" selected/total-image fraction `CardSlot.tsx` rendered
+// inline on each one) have no equivalent on the unified page - `PagePreview.tsx` renders each
+// sheet slot as a plain, un-testid'd `![{cardName}]()
`, with no inline candidate-count
+// readout at all (that signal, where it exists, lives one layer deeper - the slot's own rail -
+// and isn't reconstructable slot-by-slot without opening each one individually, which these
+// import-cluster tests never needed to do before). These two helpers port the part that IS
+// cleanly available: which named card is showing, for a given (1-based, row-major) sheet slot and
+// face. `selectedImage`/`totalImages` numeric assertions are dropped, not silently - every
+// fixture in this suite gives each result-set index its own distinct `name` (Card 1/2/3/...), so
+// asserting the right NAME landed in the right slot already fully captures what those counts were
+// standing in for (which specific candidate got auto-selected); see this port's own report for
+// the one place that stops being true.
+export const ensureDisplayFace = async (page: Page, face: "front" | "back") => {
+ const wantLabel = face === "front" ? "Showing: Fronts" : "Showing: Backs";
+ const otherLabel = face === "front" ? "Showing: Backs" : "Showing: Fronts";
+ if (await page.getByText(otherLabel).isVisible()) {
+ await page.getByText(otherLabel).click();
+ }
+ await expect(page.getByText(wantLabel)).toBeVisible();
+};
+
+export const expectDisplaySheetSlotState = async (
+ page: Page,
+ slot: number,
+ face: "front" | "back",
+ cardName: string
+) => {
+ await ensureDisplayFace(page, face);
+ const sheetSlot = page.getByTestId("page-preview-slot").nth(slot - 1);
+ await expect(sheetSlot.locator("img")).toHaveAttribute("alt", cardName);
+};
+
+interface DisplaySheetSlotAssertion {
+ slot: number;
+ name: string;
+}
+
+export const expectDisplaySheetSlotStates = async (
+ page: Page,
+ fronts: Array,
+ backs: Array
+) => {
+ for (const { slot, name } of fronts) {
+ await expectDisplaySheetSlotState(page, slot, "front", name);
+ }
+ for (const { slot, name } of backs) {
+ await expectDisplaySheetSlotState(page, slot, "back", name);
+ }
+ // leave face state as fronts, matching expectCardGridSlotStates' own toggle-back convention
+ await ensureDisplayFace(page, "front");
+};
+
+// Every sheet position renders a `page-preview-slot` div regardless of whether it's a real
+// project member (PagePreview.tsx's own comment: "every cell gets a slot, only some get an
+// ![]()
"), so an unfilled/no-query "gap" slot (a real project member with nothing resolved for it
+// yet) is indistinguishable at a glance from a genuinely-past-the-end-of-the-deck empty grid cell
+// - neither renders an `![]()
`. Clicking through to the rail disambiguates: only a real project
+// member selects it (`display-rail-header` shows "Slot N"); a past-the-end grid position ignores
+// the click (DisplayPage.tsx's own onSlotClick guard) and the rail stays idle.
+export const expectDisplaySheetSlotToExist = async (
+ page: Page,
+ slot: number
+) => {
+ await page
+ .getByTestId("page-preview-slot")
+ .nth(slot - 1)
+ .click();
+ await expect(page.getByTestId("display-rail-header")).toContainText(
+ `Slot ${slot}`
+ );
+};
+
+export const expectDisplaySheetSlotToNotExist = async (
+ page: Page,
+ slot: number
+) => {
+ await expect(
+ page
+ .getByTestId("page-preview-slot")
+ .nth(slot - 1)
+ .locator("img")
+ ).toHaveCount(0);
+};
+
+// The populated-project toolbar's compact search-bar row (ImportText's "inline" variant, no
+// Submit button of its own - a plain browser form submit fires on Enter, see ImportText.tsx's own
+// comment) - the unified page's equivalent of importText's "add more cards to a non-empty
+// project" step above.
+export const importTextInline = async (page: Page, text: string) => {
+ const field = page.getByRole("textbox", { name: "import-text-inline" });
+ await field.fill(text);
+ await field.press("Enter");
+ await expect(
+ page.locator('span:has-text("Loading your cards...")')
+ ).not.toBeVisible();
+};
+
export const importText = async (page: Page, text: string) => {
await openImportTextModal(page);
await page.getByRole("textbox", { name: "import-text" }).fill(text);
@@ -262,6 +398,107 @@ export const importXML = async (
).not.toBeAttached();
};
+// Import cluster parity port (2026-07-23, issue #272 wave 1). DisplayPage's EMPTY-project landing
+// (`display-empty-state`) mounts the bare `ImportCSV`/`ImportXML` components verbatim (DisplayPage
+// module comment: "the same plain ImportText/ImportURL/ImportXML/ImportCSV components
+// ProjectEditor.tsx's own AddCardsPanel mounts") directly inline inside a collapsed "Import a File
+// or URL" Accordion - not behind the classic "Add Cards" dropdown-triggered modal
+// openImportCSVModal/openImportXMLModal open (that dropdown only mounts once the project already
+// has a member - see openDisplayToolbarAddCardsDropdown below for that non-empty-project path).
+// The underlying `TextFileDropzone` `label`s ("import-csv"/"import-xml") are identical either way
+// - only how you REACH the form differs.
+export const importCSVOnEmptyLanding = async (
+ page: Page,
+ fileContents: string
+) => {
+ await page.getByRole("button", { name: "CSV", exact: false }).click();
+ const fileInput = page
+ .getByLabel("import-csv")
+ .locator('input[type="file"]')
+ .first();
+ const buffer = Buffer.from(fileContents);
+ await fileInput.setInputFiles({
+ name: "test.csv",
+ mimeType: "text/csv",
+ buffer: buffer,
+ });
+ await expect(
+ page.locator('span:has-text("Loading your cards...")')
+ ).not.toBeVisible();
+};
+
+export const importXMLOnEmptyLanding = async (
+ page: Page,
+ fileContents: string,
+ useXMLCardback: boolean = true
+) => {
+ await page.getByRole("button", { name: "XML", exact: false }).click();
+ if (!useXMLCardback) {
+ await page.getByText("Use XML Cardback").click();
+ }
+ const fileInput = page
+ .getByLabel("import-xml")
+ .locator('input[type="file"]')
+ .first();
+ const buffer = Buffer.from(fileContents);
+ await fileInput.setInputFiles({
+ name: "test.xml",
+ mimeType: "text/xml;charset=utf-8",
+ buffer: buffer,
+ });
+ await expect(
+ page.locator('span:has-text("Loading your cards...")')
+ ).not.toBeAttached();
+};
+
+// The non-empty-project counterpart of the two helpers above: once a project has at least one
+// member, DeckInputLanding (and its inline CSV/XML accordion) is no longer rendered at all -
+// DisplayPage's populated toolbar mounts `