Skip to content

feat: add file-based plugin discovery config#21

Open
joy7758 wants to merge 2 commits intoexternal-plugin-packagesfrom
plugin-config-file
Open

feat: add file-based plugin discovery config#21
joy7758 wants to merge 2 commits intoexternal-plugin-packagesfrom
plugin-config-file

Conversation

@joy7758
Copy link
Owner

@joy7758 joy7758 commented Mar 15, 2026

Summary

  • add file-based plugin discovery config with support for a default plugin_config.json, an explicit POP_PLUGIN_CONFIG_FILE, and environment variable overrides
  • extend registry/discovery introspection to track loaded config paths and search paths, while keeping external package loading and persona path resolution intact
  • add plugin_config.example.json, ignore local plugin_config.json, and document the workflow in the README

Validation

  • python3 -m compileall demos/discovery.py demos/task_registry.py demos/persona_workflow_demo.py demos/stage_handlers.py demos/persona_definitions.py demos/task_types.py
  • python3 demos/persona_workflow_demo.py
  • python3 demos/persona_workflow_demo.py --task-input demos/product_design_task.json
  • python3 demos/persona_workflow_demo.py --task-input demos/ux_review_task.json
  • python3 demos/persona_workflow_demo.py --task-input /tmp/pop_legacy_task.json
  • schema validation for market_research_task.json, product_design_task.json, and ux_review_task.json
  • file-based external plugin validation with POP_PLUGIN_CONFIG_FILE=/tmp/pop_demo_plugins/plugin_config.json and /tmp/content_strategy_task.json
  • default root plugin_config.json auto-discovery validation using a temporary local config file

joy7758 and others added 2 commits March 16, 2026 01:08
* feat: validate plugin config schema

* feat: validate plugin config in ci (#23)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant