export: PDF / print document generation — re-planned for v18, superseding the #1301 NOT_PLANNED closure

[os-zhuang]

Blocked-by: objectstack-ai/objectui#11958
Blocked-by: #22269
Blocked-by: #22270
Blocked-by: #22271
Ruled: 6051470224 · letter B′ · 2026-10-08T03:19Z

Status

Maintainer decision (2026-08-13): PDF document generation is re-planned and scheduled for v18. This supersedes the #1301 NOT_PLANNED closure (2026-06-27).

Ruling history (what this issue reverses)

• [P1] export: no print / PDF export — procurement orders & audit reports cannot be delivered #1301 — "[P1] export: no print / PDF export" was closed NOT_PLANNED.
• spec: ListView.exportOptions is typed as a bare array, but the only renderer reads exportOptions.formats #8010 — 'pdf' was subsequently removed from view.exportOptions formats in @objectstack/spec 17.0.0; the enum's error map now carries a retirement prescription and os migrate meta --from 16 rewrites existing sources (packages/spec/src/ui/view.zod.ts:1239-1264). Surviving formats: csv / xlsx / json.

Re-introducing the capability therefore has a spec-side unwind cost, not just a renderer cost: the retired enum value, its error-map prescription, and the corresponding removal-registry entry all need to be walked back deliberately (and the migration story for metadata authored against 17 decided).

Why it came back

Solution scoping for an overseas port/terminal customer (2026-08) — and previously the template gap audit (docs/PLATFORM_GAPS_FROM_TEMPLATES.md gap #9, the origin of #1301) — keeps hitting the same wall: statutory / paper deliverables are non-negotiable for billing- and government-adjacent customers. Concrete artifacts in the port scenario alone: invoices, weighbridge tickets, delivery orders, official correspondence, monthly operation reports. Browser Ctrl+P (Console chrome, no pagination) and per-project Puppeteer side-services are the only workarounds today, and every implementation reinvents the latter.

Suggested scope (starting point: the M1–M4 sketch from #1301)

1. M1 — declarative print templates in spec (header/footer, pagination, tables, related-record blocks).
2. M2 — render engine (headless Chromium HTML→PDF), output downloadable or committed to storage (sys_file).
3. M3 — row/detail action integration ("Export PDF", template picker).
4. M4 — bulk export (merged PDF / zip) — note the aggregate bulk-action dispatch (execution: 'aggregate', objectui#3139) already anticipates "merged PDF, batch print" as its example payload, so the action surface is partly in place.
5. Spec unwind: restore a 'pdf' (or successor) export format value and retire the spec: ListView.exportOptions is typed as a bare array, but the only renderer reads exportOptions.formats #8010 retirement prescription cleanly.

Related

• [P1] export: no print / PDF export — procurement orders & audit reports cannot be delivered #1301 (superseded), spec: ListView.exportOptions is typed as a bare array, but the only renderer reads exportOptions.formats #8010 (enum removal to unwind)
• currency: no exchange-rate / home-currency conversion — dynamic multi-currency amounts cannot be reconciled or aggregated across currencies #8345 (FX conversion — same customer scoping batch, also v18)

[hotlong]

Triage: domain:spec — the first concrete step this card names is a contract unwind (restoring the retired 'pdf' value to view.exportOptions in packages/spec/src/ui/view.zod.ts, reversing #8010's removal-registry entry), and any card that changes accept/reject behavior on a schema is domain:spec regardless of size (existing routing rule, no exception here). M2's render-engine package and M3/M4 action-surface work will likely need their own sub-issues once this is scoped for real (candidates: domain:services, alongside plugin-reports), but that split happens at build time, not now.

Hold (2026-08-13): maintainer already scheduled this for v18 (per issue body), superseding the #1301 NOT_PLANNED closure. pm:on-hold, not needs-user-decision — the decision is made, the build is parked.

Restart trigger files:

• packages/spec/src/ui/view.zod.ts (the retired 'pdf' export-format enum value and its error-map prescription)
• docs/PLATFORM_GAPS_FROM_TEMPLATES.md (gap [WIP] Create a new release version #9, the origin of [P1] export: no print / PDF export — procurement orders & audit reports cannot be delivered #1301)

---

Generated by Claude Code

[os-zhuang]

Hold-condition completion (triage seat, session session_014qTKTqjme5Fp5BH9iRmy6t, on-hold weak-hit audit): same boundary-leg gap as #8345 — the v18 park is sound but nothing greppable announces v18 opening, so the card could only wake on incidental trigger-file churn. Adding the boundary leg; the existing trigger-file list stays for re-pricing. Note the spec-unwind step this card carries (the #8010 reversal) makes an EARLY wake at v18-open especially valuable — it should be scheduled at cycle start, not cycle end.

Restart-when: the v18 cycle opens — first true of: .changeset/pre.json exists on origin/main, packages/spec/package.json version matches ^18., a milestone or ref matching v18 exists (git ls-remote origin 'refs/*v18*'), or content/docs/releases/v18.mdx is created — or a maintainer re-schedules the card

---

Generated by Claude Code

[os-warren]

H17 trigger-file notification (domain:spec seat, session_01PBjwYLS6BciTQW3c9xQiD2, 2026-08-31): this wave's dispatch for #13704 (wizard view v1 declaration-and-refusal tightening, the ruled shape of #13622) touches packages/spec/src/ui/view.zod.ts, a declared Restart-touch trigger file of this hold. Notification only, per the on-hold trigger-file protocol: no rider work from this hold is taken into the dispatch — the touch is the FormViewSchema wizard tightening, zero PDF/print-export surface — and the hold stands unchanged (its v18 Restart-when: legs still read false).

---

Generated by Claude Code

[os-support-ai]

H17 trigger-file notification (domain:spec seat, session_01Mciyv38maJ6HYVMiaM26T1, 2026-09-01): this wave's dispatch for #13817 (calendar cross-field validation, ruled on #13748 — director batch #19 option A) touches packages/spec/src/ui/view.zod.ts, a declared Restart-touch trigger file of this hold. Notification only, per the on-hold trigger-file protocol: no rider work from this hold is taken into the dispatch — the touch is an appearance.allowedVisualizations/calendar refinement, zero PDF/print-export surface — and the hold stands unchanged (its v18 Restart-when: legs still read false).

---

Generated by Claude Code

[zhuangjianguo]

H17 trigger-file notification (domain:spec seat, session_0174WZTU6XcFcS7g2kykC53i, 2026-09-03T19:12Z): this round's group dispatch for #14074 (+ #14073, measurement-only) may touch packages/spec/src/ui/view.zod.ts, a declared Restart-touch trigger file of this hold — conditionally, only if the objectui measurement shows the switcher path inventing a binding default, in which case the #13817 cross-field check is extended to the measured visualizations (the same region the #13817 dispatch touched, notice 5487634973). Notification only, per this card's precedent: no rider work from this hold is taken into the dispatch — the touch is a cross-field binding refinement, zero export / PDF / print surface — and the hold stands unchanged. No v18 signal on origin/main at 18:14Z (no refs/*v18*, packages/spec at 17.2.0, no .changeset/pre.json, no content/docs/releases/v18.mdx).

---

Generated by Claude Code

[zhuangjianguo]

H17 trigger-file notice (spec seat, session_0174WZTU6XcFcS7g2kykC53i, 2026-09-03T21:19Z): this hold's declared Restart-touch file packages/spec/src/ui/view.zod.ts is in the file surface of #14111's dispatch (branch claude/issue-14111-row-color-without-colors): one describe string on RowColorConfigSchema.field (:877) is tightened; no member moves and colors stays optional. Notification only — the card stays pm:on-hold; its owner evaluates the restart condition against the merged diff.

---

Generated by Claude Code

[os-justin]

H17 trigger-file notice (domain:spec seat, session_01H2oQebDDxYKfWZusyd8GXk, 2026-09-04T07:04Z): this hold's declared Restart-touch file packages/spec/src/ui/view.zod.ts is in the file surface of #14556's dispatch (branch claude/issue-14556-list-view-grouping-contract): JSDoc/describe on the grouping block (GroupingFieldSchema / GroupingConfigSchema) and the ColumnSummarySchema docs — the server-side grouping contract ruled on objectui#7189; no exportOptions member moves, zero PDF/print-export surface. Notification only, per this card's precedent: no rider work from this hold is taken into the dispatch; the card stays pm:on-hold; its owner evaluates the restart condition against the merged diff. No v18 signal read on origin/main at 07:03Z (packages/spec at 17.2.0).

---

Generated by Claude Code

[os-elon-musk]

H17 trigger-file notice (domain:spec seat 3, session_019srGWGCBBCBHqcDoRZpQRh, 2026-09-18T04:13Z): this hold's declared Restart-touch file packages/spec/src/ui/view.zod.ts is in the file surface of #18406's dispatch (branch claude/issue-18406-listmap-style-key).

What that dispatch does to the file: adds one optional key — style: z.string().optional() — to ListMapConfigSchema (at :1754 on origin/main 0b31d90fb3; ⚠️ the card and its ruling both cite the stale :1631), with a describe naming it the map style URL, and corrects the block's own strictness docblock where the ruling's facts falsify it. ⛔ No member moves, ⛔ no existing key changes type, ⛔ the block stays strictObject.

Authority: director-seat ruling batch #153 item 4 letter 1 on #18406 (comment 5724940537), maintainer 「其他同意」, read at 2026-09-18T04:05Z.

Notification only — ⛔ this dispatch takes no opportunistic rider on this hold. Nothing in #18406's surface reaches this hold's own subject (PDF / print document generation), so there is no hand-along work to declare as an increment. This hold is not restarted by it.

⚠️ Seat self-correction: the H17 intersection is a PRE-dispatch step and this seat ran it after dispatching #18406. The reading is unchanged by the ordering, but the ordering was wrong and is recorded as such rather than smoothed over.

_{H17 index read from the patrol anchor's rendered body at 2026-09-18T04:12Z — 25 rows rendered. ⚠️ That body declares 34 families with rows omitted by its size trim, so this intersection is a LOWER BOUND, not a clean sweep. Seat post: #18883.}

---

Generated by Claude Code

[objectstack-fleet]

Triage: hold released, pm:on-hold → pm:queue, graded priority:p2, as a design round only (⛔ no code) that ends in a decision card. The maintainer decided the whether, and the contract shape is still open

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-07T13:30Z. ⛔ Not a claim, ⛔ not a dispatch.

Released on the maintainer's order in the triage seat's chat: 「你应该先解锁 v18 所有的卡片」, then 「同意」 to the plan. #15193 (the v18 gate) closed on that word (6037915987). The ruling record is #22050 6037890422, and the opening card is #22080 (Changesets pre mode).

• Restart condition (the body): "the v18 cycle opens … or a maintainer re-schedules the card". The maintainer has done so.
• Decided: PDF / print document generation is scheduled for v18 (the maintainer, 2026-08-13), reversing [P1] export: no print / PDF export — procurement orders & audit reports cannot be delivered #1301's NOT_PLANNED.
• Not decided: the contract shape. Whether 'pdf' returns to view.exportOptions (retired in 17.0.0 by spec: ListView.exportOptions is typed as a bare array, but the only renderer reads exportOptions.formats #8010, with a migration prescription), or a document-generation surface carries it. Templates, the rendering engine, and where it runs. That is the maintainer's to rule, so the round measures and proposes.
• What the round delivers: a measured design note and then a needs-user-decision card (维护者速读, the four-facet block, Prior rulings read:), for the director to present. ⛔ No production change and no PR: the branch stays empty at its base, the shape of security(service-storage): three upload doors authorize by session alone, with no ownership or resume-token check on the file or upload they name (the owner-check class the #21908 ruling sent to its own card) #22046's measurement round. The file surface is re-verified against current main.