Compatibility

caique/inquirer and caique/clack are graded, not described as compatible. Each is run against its incumbent's own test suite, by compat-oracle, in CI.

The counts are compat-oracle's baselines, the pass count each drop-in is held to. The family's compatibility page is generated from the oracle's last run and is the authority for the current figures.

How a suite is gradedCopy Anchor Link

1. The incumbent's repository is cloned at the release tag and its test directory copied into packages/compat-oracle/vendor/. PROVENANCE names the tag, the commit and the command that reproduces it.
2. The only edit is the import that reaches the library, rewritten to a shim generated per run. Assertions and fixtures are upstream's, byte for byte.
3. A control run points the shim at the real incumbent first, which proves the harness and sets the total every rate is measured against.
4. The target run points the same shim at caique's path.

@inquirer/core: the loop, not the drawingCopy Anchor Link

@inquirer/testing renders through a headless terminal and asserts the screen, so the 41 grade hooks keeping their place across re-renders, keypresses that stop the instant a prompt settles, an effect cleanup that throws superseding the answer, and an aborted signal still restoring the cursor — behaviour a second implementation can share. usePagination is not implemented, and no case in the suite reaches it.

@clack/prompts: 16 behavioural casesCopy Anchor Link

289 of clack's 444 assertions are snapshots of clack's exact frames, in 17 of its 19 files. Matching them frame for frame would make caique/clack clack, so they are subtracted by name, as a declared subset. caique/clack passes all of limit-options.test.ts and the two guide.test.ts cases that render all twelve prompts with and without the guide.

One more case is subtracted, by its exact title. It calls updateSettings({ withGuide: false }) imported from @clack/core and asserts the prompts obey it. That is module-level state inside @clack/core, a package caique does not depend on and cannot read, so the case grades @clack/core and not @clack/prompts. caique/clack exports its own updateSettings, as @clack/prompts does, and its prompts obey that one. The subtraction is published on the compatibility page. The row reads 16 / 16, level with clack's own 16 / 16, so burgee migrate rewrites @clack/prompts to caique/clack. It leaves a file that imports box, progress or taskLog on clack.

Known differencesCopy Anchor Link

• caique/clack's frames are clack's layout, not its bytes. A test of yours that snapshots clack's output will see different escape sequences.
• updateSettings must come from caique/clack, as above. burgee migrate does not rewrite @clack/core. It refuses a file that imports both @clack/prompts and @clack/core (reason sibling-state), with the fix: import updateSettings from caique/clack, then run it again. It reads one file at a time, so an updateSettings from @clack/core in a file with no clack prompts is not caught. Move that import yourself.
• caique/clack does not build box, progress or taskLog; no graded case reaches them.
• caique/inquirer has no usePagination.
• The legacy inquirer package is not a drop-in: its object API is out of scope, and caique/inquirer is @inquirer/core's surface.