docs: propose plugin system architecture for keeper resolvers (issue …

[OpadijoIdris]

Propose Plugin System Architecture for Keeper Resolvers (#121)

Summary

Drafted the architectural proposal for the Keeper Plugin System to support custom Task Resolvers. This new architecture allows node operators to load tailored, off-chain logic dynamically (via local directories or NPM packages) to determine task readiness and shape event logic without altering the main SoroTask Keeper loop.

Related Issue

Closes #121

Type of Change

• Feature
• Bug fix
• Refactor
• Documentation

Changes Made

• Created keeper/RESOLVER_PLUGINS.md encompassing:
  • The Javascript BaseResolverPlugin interface specifications (init, resolve, destroy).
  • Configuration schema design for a new plugins.json file.
  • The design flow detailing how the PluginManager dynamically instantiates classes during Keeper startup.
  • Procedural logic outlining the integration between the proposed custom resolver evaluation step and the existing TaskPoller interval and gas checks.

Validation

• cargo fmt --all (if contract changed)
• npm run lint in frontend (if frontend changed)
• Manual verification completed

Screenshots (if UI changes)

N/A

Checklist

• Scope is focused and avoids unrelated changes
• Commit messages are clear
• Documentation updated when needed
• ETA was provided when requesting assignment for the linked issue

[drips-wave]

@OpadijoIdris Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[ayomideadeniran]

Your pr is under review.