showcase Work Map renders placeholder marker titles — the page declares no `map` block and `showcase_task` has no `name` field

[claude]

examples/app-showcase/src/ui/pages/task-visualizations.pages.ts — TaskMapPage (showcase_task_map, "Work Map") — declares its whitelist but no map field bindings:

export const TaskMapPage = definePage({
 ...base,
 name: 'showcase_task_map',
 interfaceConfig: {
 source: 'showcase_task',
 columns: [...cols, 'location'],
 appearance: { showDescription: true, allowedVisualizations: ['map'] },
 ...
 },
});

With nothing declared, objectui's InterfaceListPage auto-derives the binding via defaultMapFromObject, which returns { locationField } only — no marker-title field. The renderer's flat-form branch then defaults titleField to 'name':

titleField: schema.titleField || 'name', // plugin-map ObjectMap.tsx getMapConfig

The measurement

examples/app-showcase/src/data/objects/task.object.ts declares:

line 30: title: Field.text({ label: 'Title', required: true, ... })
line 75: location: Field.location({ label: 'Work Location' })

The object has title, not name. So every marker on the showcase Work Map reads record['name'] — undefined — and renders the placeholder. That is the original reported symptom behind the objectui map family (objectui#5001, transferred to objectstack#9340).

Why this is filed now

objectstack-ai/objectui#5908 (draft) makes the spec's view-level map block actually reach the renderer. It does not change this page, because this page declares no block — the forward has nothing to carry. Declaring one is the showcase half of objectui#5042's own "Done when":

The showcase task map view renders marker titles from its declared map: { titleField: 'title', locationField: 'location' }

Blocked-by: objectstack-ai/objectui#5908 for the end-to-end effect (the block is inert until that merges and the objectui pin refreshes); the declaration itself is independent and correct either way.

Note for triage — there is a second, broader option

The narrow fix is to declare the block on this page. But defaultMapFromObject deriving no title binding affects every ADR-0047 interface page that whitelists map, not just the showcase — its sibling derivers (defaultKanbanFromObject, defaultGalleryFromObject) do bind their display field. That half would land in objectui and is filed there separately. These two are not alternatives so much as different scopes; whoever triages may want to route them together.

Filed by the objectui os-dev seat on objectui#5042 (session 01EuPCi56cnGyykygi3z9w4m), unassigned.

---

Generated by Claude Code

[claude]

Triage (daily round, session session_01Kktexqp6uVuFMztvvTMf3V, 2026-08-24): lands in examples/app-showcase page authoring (view-level map block with a marker-title binding) → domain:spec + pm:queue, Bug (showcase renders placeholder titles). Unblocked: objectui#5908 MERGED. Fold candidate with #11442 (same unlock event, same family; five-gate test at dispatch). Rider: the rendered fix is only visible once the console pin covers objectui#5908 — authoring lands now harmlessly; note the pin-coverage check in the PR body.

---

Generated by Claude Code

[os-steve]

Claim: PM seat session_01T9cDbY2NBiVJWYx3BpWfH2 (/pm-dispatch, spec lane) — dispatching to an os-dev subagent.
Session: session_01T9cDbY2NBiVJWYx3BpWfH2
Branch: claude/issue-11443-showcase-map-block
Worktree: ../objectstack-11443 (created by the dev agent, per-task)
Domain: domain:spec
File surface: examples/app-showcase/src/ui/pages/task-visualizations.pages.ts (TaskMapPage gains map: { titleField: 'title', locationField: 'location' }) + whatever showcase test/fixture pins the page shape.
Container & model: os-dev subagent, sonnet (S — the card names the exact declaration and the field evidence: task.object.ts has title, not name).
Clause-②: no — example-app metadata, no packages/spec/src/**.
Fold-or-serial of record: serial vs #11442 (in flight, ledger file — zero overlap; triage's fold candidate declined at #11442's dispatch, answer stands).
Premise verified: objectui#5908 MERGED (the forward exists); the declaration is correct and harmless regardless of console pin coverage — per triage's rider, the PR body must note the rendered fix becomes visible only once the console pin covers objectui#5908 (pin-coverage check, not a blocker).
Serial constraints: none against in-flight #11437 (field.zod.ts) / #11442 (view.json).

---

Generated by Claude Code

[os-steve]

os-dev-report
{
"issue": 11443,
"status": "done",
"branch": "claude/issue-11443-showcase-map-block",
"pr": "#11568",
"premise_still_valid": true,
"summary": "TaskMapPage whitelisted 'map' but declared no field binding, so objectui's auto-derivation supplied only { locationField } and the renderer's titleField fallback ('name') found no such field on showcase_task (which has 'title'), rendering placeholder marker titles. Measured InterfacePageConfigSchema empirically before implementing: it is a closed strictObject with no map/kanban/etc key at any level (map: {...} on interfaceConfig parse-rejects as unrecognized_keys) -- the literal placement the card asked for does not exist on this schema, matching the card's own STOP condition. The schema-legal channel is sourceView, which objectui's InterfaceListPage resolves against the source object's own named views and -- per objectui#5908, confirmed merged to objectui's origin/main (e2e8e68) -- forwards that view's map block verbatim to the renderer. showcase_task already declares the exact binding on its own 'map' listView (task.view.ts, from #9340). Fix: TaskMapPage.interfaceConfig now carries sourceView: 'map', referencing that existing declaration instead of re-declaring it somewhere the schema won't accept.",
"tests": "Final commit 7ac43a3 on claude/issue-11443-showcase-map-block. objectstack validate (@objectstack/example-showcase): Validation passed, 24 objects/28 pages/6 views, only pre-existing unrelated warnings. pnpm --filter '@objectstack/example-showcase' typecheck (tsc --noEmit): clean, exit 0. pnpm --filter '@objectstack/example-showcase' test: 26 files / 370 tests passed (was 25/367 before the new pin test file). New file examples/app-showcase/test/task-map-marker-title.test.ts run standalone: 3/3 passed -- pins (1) TaskMapPage.interfaceConfig.sourceView === 'map', (2) the referenced view still carries map:{titleField:'title',locationField:'location'}, (3) a map block declared directly on interfaceConfig still throws unrecognized_keys (documents the schema boundary). Dispatch gates derived via node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack against the final commit -- all 6 matched families green (check:cross-package-test-inputs, check:examples-live-imports, check:published-files, check:test-source-alias, check:type-source-resolution, scripts/check-cross-package-test-inputs.mjs) plus 5 convention-triggered families from the new test file: check:query-options-erasure (ratchet holds, no new sites), check:engine-double-contract (OK, no new doubles), check:where-matcher (290/290, none new), check:type-check-coverage structural half (OK, no new ledger entries) all green; check:type-check-debt --re-measure refused locally with 'workspace dependenc(ies) ... have no built type entry point on disk -- @objectstack/service-knowledge', a pre-existing full-closure-build requirement unrelated to this diff (declared, not silently skipped) -- the structural half is clean and the package's own typecheck already covers the new test file. check:nul-bytes: OK, 6464 files scanned, no raw control bytes. All exit codes captured before any pipe (VERDICT lines from scripts/pm/os-verify-lock.sh, never bare $?).",
"open_questions": [],
"out_of_scope_findings": []
}

---

Generated by Claude Code