WORK-264
ID:WORK-264Status:pending

Collection heading-delimited table columns

The rich-table path: a table collection's body uses the sections content model (heading = column separator + label, body = per-cell markdoc template with $item), with collection owning the <table>/<thead> and row alignment.

Priority:mediumComplexity:moderateMilestone:v0.16.0Source:SPEC-070
main View source

Criteria completion

Criteria completion: 0 of 4 (0%) checked; tracking started on May 25, no incremental history yet0%25%50%75%100%May 25Jun 15

Tracking started May 25 — check back for trends.

Relationships

Implements 1
Branches 3
main current pending
claude/v0.16.0 doneclaude/milestone-v0.16.0 pendingmain pending

Acceptance Criteria

  • In table layout the body parses as heading-delimited sections; each heading is a column (label = heading text, ordered by sequence)
  • Each column cell is the section's markdoc template, transformed per entity with $item bound (reusing WORK-262 capture)
  • An empty body falls back to the fields shorthand; column heading text is static — $item in a heading warns
  • collection emits <table>/<thead> and aligned rows; tests cover multi-column tables and formatting/combining in cells (with WORK-265 functions)

Dependencies

  • WORK-263 (collection core)
  • WORK-262 (deferred-body capture)

References

  • SPEC-070 — Built-in layouts (heading-delimited columns)