I am concerned that in the future the lumo ui component templates will not be able to keep up with material3 updates and the library will become obsolete.

However, the component templates are not just copies of material3, but have placeholders and other arrangements made by the library authors, so they cannot be updated automatically.

Therefore, we propose to implement a pipeline that periodically detects differences from material3 by AI.
Specifically, we propose the following
(This idea is still just floating vaguely in my mind and may need to be pointed out from various perspectives)

• Use the Github Actions on: schedule: to have the component-check workflow run at a specified time.
• Tell some AI provider (ex. OpenAI, Gemini, Claude Code ...) in the component-check workflow the location of the material3 library code. The component-check workflow tells some AI provider (ex. OpenAI, Gemini, Claude Code ...) the location of the library code of material3 and compares it with the component code in the lumo ui repository.
• If there is a feature or difference between material3 and lumo ui, create an issue.
• (optional) When an issue is created, the AI will automatically generate a Pull Request to fix it.
• (optional) Of course, this should be incorporated into the lumo ui library during development, but it would be even better if there were a mechanism to distribute it to library users as well.

As the author of the library, I would appreciate your feedback on this idea. In some cases, I will try to implement it myself.