Automate list of contracts on each API README file

[ernestognw]

After #220, each README page will have 2 lists of contracts: one provided manually and the other automatically generated from the docs scripts. See #220 (comment)

As proposed by @james-toussaint, an alternative to unify both list may be to use the @notice NatSpec tag:

2. Do the same but if we don't like what is in @dev we could add @notice and extract it from:

/**
* @notice An executor module that enables executing calls from accounts where the it’s installed.
* @dev Basic implementation for ERC-7579 executor modules that provides execution functionality
* for smart accounts.
*/

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

OpenZeppelin/openzeppelin-contracts#6050 - Add notice about the use of NPM tags in README.md [merged]

👤 Suggested Assignees

• Amxx

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!