docs: stale references to removed @langchain/community package in contributing guides

[navyabijoy]

Checklist

• I added a very descriptive title to this issue.
• I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:

The contributor documentation currently contains stale references to the removed @langchain/community package and describes an integration workflow that is no longer valid.

Specifically, .github/contributing/INTEGRATIONS.md still links to:

• libs/community/langchain-community/langchain.config.js
• libs/community/langchain-community/package.json

Those files were removed with PR #10600 (merged April 1, 2026), so the links now return 404. In addition, the surrounding sections (“Creating a separate entrypoint” and “Third-party dependencies”) still instruct contributors to modify the old monolithic community package, which conflicts with the current policy in CONTRIBUTING.md that new integrations must be published as standalone packages.

There is also a stale path in CONTRIBUTING.md (integration test setup) referencing libs/community/langchain-community/.env, which no longer exists.

Because these are core onboarding docs, this mismatch creates confusion for new contributors, increases setup friction, and results in avoidable failed attempts when following outdated instructions.

Idea or request for content:

Update the contribution docs to fully align with the post-@langchain/community structure and standalone integration policy.

Proposed documentation updates:

1. Revise .github/contributing/INTEGRATIONS.md to remove or rewrite sections that depend on the deleted community package workflow:
   • Replace “Creating a separate entrypoint” with guidance for standalone provider package structure (e.g., package layout, entrypoint conventions, and where to place exports).
   • Replace “Third-party dependencies” guidance so it reflects standalone package dependency management instead of peerDependenciesMeta in the deleted package.
2. Remove broken links to deleted files under libs/community/langchain-community/.
3. Cross-link to current canonical guidance in CONTRIBUTING.md and a real standalone package example such as libs/providers/langchain-openai/.
4. Update CONTRIBUTING.md to remove the obsolete .env path reference to libs/community/langchain-community/.env in the integration testing section.

Steps to Reproduce (Broken Links)

1. Open .github/contributing/INTEGRATIONS.md
2. Click the link on line 13 → 404 Not Found: https://github.com/langchain-ai/langchainjs/blob/main/libs/community/langchain-community/langchain.config.js
3. Click the link on line 48 → 404 Not Found: https://github.com/langchain-ai/langchainjs/blob/main/libs/community/langchain-community/package.json
4. Click the link on line 54 → 404 Not Found: https://github.com/langchain-ai/langchainjs/blob/main/libs/community/langchain-community/langchain.config.js

[navyabijoy]

hi Christian Bromann (@christian-bromann) John Kennedy (@jkennedyvz) i would like to fix these stale links in the docs, please !

[Parker-Fawcett]

Stale docs are a real pain - especially when the package name changed. This is exactly the class of problem rebuild-dossier solves: mechanically-enforced contracts between code and docs so they can't drift. Happy to help if useful - paper context: https://arxiv.org/abs/2608.23616