Skip to content

PRISM-v1.3.0-devt4c

Pre-release
Pre-release

Choose a tag to compare

@lemlnn lemlnn released this 15 May 17:16
· 8 commits to main since this release
f724895

PRISM v1.3.0-devt4c is a config and extension-control development build. It builds on the devt4b package split by adding direct config editing, per-extension enable/disable controls, and per-extension option storage. This makes the experimental extension system much more user-configurable.

Added

  • new config_edit.py module for config mutation helpers
  • config --set KEY=VALUE for editing config values from the CLI
  • config --unset KEY for resetting config values back to defaults
  • extension --list to show discovered extensions and enabled/disabled state
  • extension --enable NAME to remove an extension from the disabled list
  • extension --disable NAME to disable a specific extension in the current config
  • extension --set-option NAME KEY=VALUE for per-extension option storage
  • extension --unset-option NAME KEY for removing stored extension options
  • new disabled_extensions config field
  • new extension_options config field
  • config status output now shows disabled extension count and extension option count
  • extension modules now receive options through PRISM_EXTENSION_OPTIONS
  • optional configure_extension(options) hook for extensions that want setup-time configuration

Changed

  • extension loading now respects disabled extension filters
  • extension status output now includes disabled extension information
  • extension listing can scan extensions while showing whether they are disabled
  • config handling now supports direct edits without requiring full config --save workflows
  • CLI help/examples now include config editing and extension control commands
  • extension system now feels closer to a configurable plugin ecosystem instead of only an on/off framework

Notes

  • this is a pre-release / development build
  • extension API is still experimental
  • existing extensions will still load normally
  • per-extension options are stored by PRISM, but extensions must be updated to actually read and use those options