fix(docs): correct TypeDoc entry point path

[jbdevprimary]

Summary

• Fix TypeDoc entry point from src/index.ts to packages/core/src/index.ts
• Make TypeDoc step non-blocking to allow deployment even if API docs generation fails

Context

The GitHub Pages deployment was failing because TypeDoc couldn't find src/index.ts - the monorepo uses packages/core/src/index.ts instead.

Test plan

• PR CI passes
• GitHub Pages deployment succeeds after merge

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@jbdevprimary has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 24 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.

📥 Commits

Reviewing files that changed from the base of the PR and between 4f5009e and 5d4b153.

📒 Files selected for processing (7)

• .github/workflows/deploy-gh-pages.yml
• biome.json
• docs-site/.astro/collections/docs.schema.json
• docs-site/.astro/content-assets.mjs
• docs-site/.astro/content-modules.mjs
• docs-site/.astro/content.d.ts
• docs-site/.astro/types.d.ts

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

---

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.}

[gemini-code-assist]

Summary of Changes

Hello @jbdevprimary, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to improve the reliability of the documentation build and deployment pipeline. It addresses a critical misconfiguration in the TypeDoc setup by updating the entry point path, which was causing documentation generation to fail. Furthermore, it enhances the overall deployment stability by making the TypeDoc step non-blocking, preventing documentation build issues from impeding the successful deployment of the GitHub Pages site.

Highlights

• TypeDoc Configuration: Corrected the TypeDoc entry point path from src/index.ts to packages/core/src/index.ts to accurately reflect the monorepo's structure, resolving previous build failures.
• Deployment Robustness: Modified the TypeDoc generation step to be non-blocking, ensuring that the GitHub Pages deployment process can successfully complete even if API documentation generation encounters errors.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/deploy-gh-pages.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to fix the TypeDoc entry point path for the documentation site. However, the current changes only include generated build artifacts from Astro located in the docs-site/.astro/ directory. Committing these files is not a good practice as they can bloat the repository and cause conflicts. The actual source code changes that fix the TypeDoc configuration are missing from this PR. I recommend removing the generated files, adding docs-site/.astro/ to the .gitignore file, and committing the relevant source files that contain the intended fixes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud