chore: sync core lib and CLAUDE.md from agent-core

[avifenesh]

Automated sync of lib/ and CLAUDE.md from agent-core.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Summary of Changes

Hello, 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 performs an automated synchronization of core library files from the agent-core repository. The primary impact is a significant refactoring of data collection mechanisms, specifically by deprecating direct binary module interaction for documentation drift analysis and updating git data collection to align with repo-intel terminology and an enhanced set of collected metrics.

Highlights

• Documentation Drift Analysis Removal: The functionality for detecting documentation drift using an external binary module has been entirely removed from docs-patterns.js, including its lazy-loading mechanism, the getBinary function, and the getDocDriftSignals function.
• Git Data Collection Refactoring: The git data collection in git.js has been updated to use 'repo-intel' terminology and commands instead of 'git-map'. This includes changes in documentation, agent-analyzer calls, and the structure of collected metrics.
• Updated Git Metrics: The collected git data now includes recentChanges for file activity and confidence for AI attribution. Conversely, the commitShape metric has been removed, and scopes in conventions was replaced by usesScopes.

Changelog

• lib/collectors/docs-patterns.js
  • Removed the lazy-loading mechanism for a binary module and its associated binaryModule and binaryLoadError variables.
  • Removed the getBinary function, which was responsible for loading the binary module.
  • Removed the getDocDriftSignals function, which previously used the agent-analyzer binary for documentation drift detection.
  • Removed the docDrift property from the object returned by the collect function.
• lib/collectors/git.js
  • Updated comments to refer to 'repo-intel' instead of 'git-map' for git history analysis.
  • Changed the agent-analyzer command from git-map init to repo-intel init for collecting git data.
  • Removed the commitShape property from the collected git data.
  • Added a recentChanges property to the file activity data.
  • Added a confidence property to the aiAttribution data.
  • Replaced the scopes property with usesScopes in the conventions data.
• lib/collectors/index.js
  • Removed the export of the getDocDriftSignals function.

Activity

• No specific activity (comments, reviews, progress) has been recorded for this pull request yet.

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 refactors data collection by removing the 'doc-drift signals' feature and its associated binary module loading from lib/collectors/docs-patterns.js. It renames the internal git-map concept to repo-intel in lib/collectors/git.js and refines the collected git data by removing commitShape data, adding recentChanges to file activity, including confidence in AI attribution, and changing conventions.scopes to a boolean conventions.usesScopes. The lib/collectors/index.js file is updated to reflect the removal of getDocDriftSignals.