ome-zarr-C

Use a deterministic browser workflow only when direct fetch or extraction is insufficient for a public-web task.

Run the smallest correct verification lane and report it precisely.

Keep public-web research compliant, bounded, and efficient through rule checks, caching, and backoff instead of evasive scraping.

Optimize a parity-proven ome-zarr native C++ surface for measurable speedups by improving data layout, copies, cache behavior, and boundary design without changing behavior.

Benchmark converted code against the frozen upstream implementation before making performance claims.

Port one upstream ome-zarr-py surface to standalone native C++ without touching the frozen snapshot.

Legacy reference only. Current main does not use pybind11 ports; use this only to understand old debt before removing it.

Choose Python-side parity tests and syntax checks without weakening coverage.

Produce content-addressed parity evidence and protect the frozen upstream snapshot while porting or verifying native surfaces.

Extract the smallest useful amount of text or structured data from a known public page before falling back to full browser automation.

Verify public-web findings with source quality, dates, and second-source checks before turning them into advice or claims.

Plan and run current public-web discovery for docs, releases, issues, and community evidence without guessing or over-browsing.

Use when editing GitHub Actions, CodeQL, Dependabot, or workflow-installed tool pins and the repo needs verified current versions and scanner scope discipline.

Add narrow regression and differential tests that catch incomplete or overconfident code changes.

Keep context narrow and high-signal by loading only the smallest correct docs, code, tests, and skills.

Search the repo, the frozen upstream snapshot, and official upstream sources before adding code or dependencies.

Drive new ports and bug fixes with tests first or tests alongside the implementation.