feat(drift): add --artifacts-dir, and say where the default actually lands (0.1.0-alpha.19)

[jaruesink]

Closes the flag gap you flagged — with one correction to the diagnosis that changes what the fix had to be.

The default doesn't write into the target repo

It writes into process.cwd(). Verified: run from /tmp against packages/vision and the report lands in /tmp, with nothing written to vision at all.

Report written to: /private/tmp/driftcwd/docs/audits/artifacts/currykit-vision-2026-08-10/drift-report.md
ls vision/docs/audits → No such file or directory

That's why lc-classic-starter got littered — the run happened from inside it. The same command from anvil's directory litters anvil instead, which is the worse failure, because the artifacts then look like they belong there.

So the flag alone wouldn't have closed it. The usage text said Default output: docs/audits/artifacts/... with no frame, which reads as relative to the repo being scanned. Both the CLI help and the docs now say relative to your current directory — not to the audited repo.

What shipped

• drift --artifacts-dir <dir> → writes <dir>/drift-report.md, matching audit
• --output still wins over --artifacts-dir
• Help and CLI reference now state the default's frame
• audit's own drift invocation is unaffected — it already passes --output explicitly

The cli-target-contract test pinned parseArgs's exact shape, so it's updated and extended with flag coverage.

Verify

lint · format:check · release:pin --check · typecheck · 529 pass / 0 fail · verify:self-audit-proof.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 34 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 9f52e9fc-a09c-429d-bc8b-842774e6036e

📥 Commits

Reviewing files that changed from the base of the PR and between 97d5689 and b02e2af.

📒 Files selected for processing (12)

• README.md
• bin/anvil.ts
• docs-site/public/llms-full.txt
• docs-site/src/content/docs/reference/cli.md
• docs/byok-trust-model.md
• docs/first-user-proof-packet.md
• docs/first-user-proof.md
• docs/getting-started.md
• docs/proofs/current-outside-tester-send-packet.md
• package.json
• scripts/cli-target-contract.test.ts
• scripts/drift-detect.ts

---

_{Comment @coderabbitai help to get the list of available commands.}