Skip to content

docs(plans): post-merge follow-ups for #787/#788/#789#790

Open
paddymul wants to merge 1 commit into
mainfrom
plans/post-785-followups
Open

docs(plans): post-merge follow-ups for #787/#788/#789#790
paddymul wants to merge 1 commit into
mainfrom
plans/post-785-followups

Conversation

@paddymul
Copy link
Copy Markdown
Collaborator

Summary

Three planning docs capturing post-merge follow-up work for the in-flight scoped-SD / spike / pushdown PRs. No code changes — markdown only.

  • plans/0788-pushdown-consumer.md: how to actually consume StatFunc.pushdown once feat(paf): @stat(pushdown=...) declares engine push-down support #788 lands. Recommends the trust-the-author duck-typing path (Interp A) over the separate-registered-form approach, with a concrete _pushdown_eligible_for hook in XorqStatPipeline. Open questions + estimated scope.
  • plans/0787-xorq-rows-first-coverage.md: how to restore the phase-divergence assertion the spike test had to drop on xorq — the PR body flagged this as the most important item to resolve before un-gating the spike. Four hypotheses for the xorq failure, an instrumentation recipe to disambiguate, and a load-bearing assertion form pinned to concrete length / filtered_length values rather than just dict inequality.
  • plans/0789-analysis-klasses-traitlet.md: the deeper fix punted by feat(scoped-sd): wire cleaned_* into merged_sd + Codex P2 fix #789. analysis_klasses is a plain class attribute (not a traitlet), so observers don't fire on direct reassignment. add_analysis papers over this with a manual _handle_widget_change call. Outlines the traitlet conversion + subclass-override migration cost. Recommends deferring until a user-facing bug surfaces or a separate dataflow-init refactor is in flight.

Test plan

  • Markdown only — no test or build impact.

🤖 Generated with Claude Code

- ``0788-pushdown-consumer.md``: how to actually consume
  ``StatFunc.pushdown`` once #788 lands. Recommends the trust-the-
  author duck-typing path (Interp A) over a separate-registered-form
  approach, with a ``_pushdown_eligible_for`` hook in
  ``XorqStatPipeline``. Open questions + estimated scope.
- ``0787-xorq-rows-first-coverage.md``: how to restore the
  phase-divergence assertion that the spike test had to drop on xorq.
  Lists four hypotheses for the xorq failure, an instrumentation
  recipe to disambiguate, and a load-bearing assertion form pinned to
  concrete length / filtered_length values rather than just dict
  inequality.
- ``0789-analysis-klasses-traitlet.md``: the deeper fix punted by
  #789. ``analysis_klasses`` is a plain class attribute, not a
  traitlet, so observers don't fire on direct reassignment.
  ``add_analysis`` papers over this with a manual
  ``_handle_widget_change`` call. Outlines the traitlet conversion +
  subclass-override migration cost. Recommends deferring until a
  user-facing bug surfaces or a separate dataflow init refactor is in
  flight.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

📦 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.3.dev26199126641

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.3.dev26199126641

MCP server for Claude Code

claude mcp add buckaroo-table -- uvx --from "buckaroo[mcp]==0.14.3.dev26199126641" --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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triaged Reviewed and triaged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant