fix: resolve all CI failures — types, gitleaks, deps, test, Windows

[chitcommit]

Summary

Type errors (Build & Test):

• config.ts: Add missing type: "input" to 5 inquirer prompt calls, fix validate signatures (string → unknown) for inquirer v13
• notion.ts: Use client.request() for databases.query (removed in @notionhq/client v5)

Gitleaks (secret-scan):

• Fix invalid .gitleaks.toml syntax — use [extend] useDefault = true
• Allowlist doc files with example tokens (.claude/mcp.json, INTEGRATION_STATUS.md, SECURITY.md)

Test (Build & Test):

• stemcell.test.ts: Remove branch.length > 0 assertion — GitHub Actions uses detached HEAD

Windows (Smoke Test):

• package.json: Replace Unix mkdir -p && cp with Node.js fs in copy:assets script

Dependencies (dependency-audit):

• npm audit fix patches express-rate-limit and hono
• Remaining: @modelcontextprotocol/sdk (no fix available, false positive from self-referential dep)

Test plan

• tsc --noEmit — zero errors
• npm run build — clean
• npm test — 15/15 pass
• gitleaks — no leaks found
• CI: Build & Test — should pass
• CI: Smoke Tests (all platforms) — should pass
• Governance: secret-scan — should pass
• Governance: dependency-audit — will fail (MCP SDK, unfixable)

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Rate limit exceeded

@chitcommit has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 20 minutes and 34 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ccbd6d73-88eb-476e-9c92-07a6d36284ce

📥 Commits

Reviewing files that changed from the base of the PR and between 119cf48 and 2a94c7a.

📒 Files selected for processing (7)

• .github/workflows/governance-gates.yml
• .github/workflows/parity-tests.yml
• .gitleaks.toml
• package.json
• tests/parity_node.js
• tests/parity_py.py
• tests/stemcell.test.ts

📝 Walkthrough

Walkthrough

Updates gitleaks configuration from allowlist to extend mechanism, adds explicit input type specifications to CLI prompts, and migrates Notion data retrieval from deprecated API method to REST-based request approach.

Changes

Cohort / File(s)	Summary
Configuration Files .gitleaks.toml	Replaces allowlist section with extend section and enables default extension behavior via useDefault flag.
CLI Configuration src/commands/config.ts	Adds explicit type: "input" specifications to CLI prompts, broadens validation parameter types from string to unknown, and includes type casting for public types. Extends notion-related prompts to collect actions/aiUsage/projects inputs.
Notion API Client src/lib/notion.ts	Replaces deprecated databases.query() call with REST-based request using generic request method with path databases/{databaseId}/query and POST method.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 We've tidied our secrets with gitleaks anew,
Added types where we whispered, now clear as the dew,
Notion's old ways have danced to the REST,
Each change a small polish—configuration's best! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly summarizes the main objective: resolving multiple CI failures across types, gitleaks, dependencies, tests, and Windows compatibility.
Description check	✅ Passed	The description covers all key sections of the template including Type of Change, Motivation and Context, How It Has Been Tested, and provides detailed implementation notes.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/ci-green

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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