feat(styling): init_sd as augmentation channel (nested merge + delete_keys + demo)

[paddymul]

Summary

Turns init_sd into a real augmentation channel for per-column display config — one that plays nice with lowcode ops (Search → highlight) instead of clobbering them like column_config_overrides does. Two style_column changes + a delete_keys escape hatch + a working demo notebook.

The plumbing this depends on already landed:

• feat(jlisp): sd channel — SDResult return + sd-as-arg read-only view #755 — jlisp sd channel (SDResult return)
• feat(polars-search): plumb search term to JS as highlight_regex via SDResult #758 — polars Search → highlight_regex via SDResult
• feat(js-core): highlight_phrase / highlight_regex on string displayer #742 — JS-side highlight_phrase / highlight_regex on the string displayer

This PR is the styling-layer half: the pieces that let an op's contribution and a user's init_sd coexist on the same column.

Pieces

1. feat(styling): merge column_metadata displayer_args + ag_grid_specs — two shallow merges in DefaultMainStyling.style_column. When column_metadata carries displayer_args (e.g. {'max_length': 5000}) or ag_grid_specs (e.g. {'wrapText': True, 'width': 400}), they merge into the styled bag instead of replacing. Caller wins per-key. Critically, this lets a Search op's highlight_regex and a user's max_length coexist on the same column — column_config_overrides's replace semantics would have clobbered the highlight.

2. feat(styling): init_sd delete_keys — column_metadata.delete_keys: list[str] pops the named top-level keys from the final base_config. Motivating case: drop the auto-attached tooltip_config on a string column the user doesn't want a permanent tooltip on, without subclassing the styling analysis. Operates on top-level only (tooltip_config, ag_grid_specs, displayer_args, col_name) — nested removal isn't needed for the motivating case.

3. Restaurant-Complaints demo notebook — working example combining init_sd (nested displayer_args + ag_grid_specs + delete_keys) with extra_grid_config (rowHeight, pinnedRowHeight) and a viol_status == 'Fail' filter on the polars Enum.

Usage

init_sd = {
    'comments': {
        'displayer_args': {'displayer': 'string', 'max_length': 5000},
        'ag_grid_specs': {'wrapText': True, 'width': 400, 'maxWidth': 800},
        'delete_keys': ['tooltip_config'],
    },
}
PolarsBuckarooInfiniteWidget(df, init_sd=init_sd, ...)

This shape is intentionally the same as column_config_overrides would take — but init_sd augments via merge_sds (each key wins per-call), while column_config_overrides replaces via shallow row.update().

Provenance

Salvaged from #748 after #755 / #758 landed the underlying SDResult plumbing. Branched fresh off main; the obsolete 2-tuple-contract commits and the now-merged Search/jlisp pieces were dropped.

Test plan

• pytest tests/unit/dataflow/ — 120 pass (3 new tests: nested-merge, search+max_length coexistence, delete_keys)
• CI green
• Manual: Restaurant-Complaints.ipynb renders without tooltip on comments column, wraps long text, max_length: 5000 honored

🤖 Generated with Claude Code

[github-actions]

📦 TestPyPI package published

pip install --index-strategy unsafe-best-match --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ buckaroo==0.14.1.dev25998799685

or with uv:

uv pip install --index-strategy unsafe-best-match --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ buckaroo==0.14.1.dev25998799685

MCP server for Claude Code

claude mcp add buckaroo-table -- uvx --from "buckaroo[mcp]==0.14.1.dev25998799685" --index-strategy unsafe-best-match --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ buckaroo-table

📖 Docs preview

🎨 Storybook preview

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 467e8ecdfd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".