Assets: add the square plugin icon (128×128 and 256×256) used by the WordPress.org plugin directory listing and the installed plugins screen. No functional changes.
1.1.3
readme: the Source code section (public GitHub repository and npm run build reproduction steps for the compiled admin bundle) is now placed directly after Description so the build-source pointer is immediately visible.
readme: Tested up to bumped to 7.0 to reflect the current WordPress release.
Read tracker: plugin and mu-plugin frame classification in Tracker::classify_trace() now goes through plugin_basename() instead of comparing against WP_PLUGIN_DIR / WPMU_PLUGIN_DIR directly. This reuses WP core’s plugins-root resolution (including symlink awareness via $wp_plugin_paths) without duplicating the constant references in plugin code. Behavior is unchanged for standard setups; the legacy mu: slug prefix on mu-plugin readers is dropped (it was not consulted anywhere downstream).
1.1.2
Admin menu icon: the opacity override is now attached to a registered style handle via wp_add_inline_style() on admin_enqueue_scripts instead of being printed as an inline <style> tag from admin_head. Visual behavior is unchanged.
Read tracker: the WP_PLUGIN_DIR and WPMU_PLUGIN_DIR references used to classify backtrace frames are now routed through wp_normalize_path(), with a comment recording why those constants are referenced (identifying other plugins’ install roots — Orpharion’s own location is resolved from __FILE__).
Documentation: readme.txt now includes a “Source code” section pointing to the public GitHub repository (https://github.com/mt8/orpharion) and the npm run build flow used to regenerate the bundled admin assets.
1.1.1
WP-CLI: wp orpharion export –output=<file> now requires a bare *.json filename and always writes into wp-content/uploads/orpharion/. Absolute or relative paths and non-.json extensions are rejected so option_value content (which can include API keys, SMTP credentials, and other secrets) cannot be written to a web-accessible location. The export directory is created on demand with index.html and .htaccess so it is not browseable.
1.1.0
Renamed the plugin from “Optrion” to “Orpharion” to remove an external trademark conflict before the WordPress.org review. The slug, text domain, REST namespace, WP-CLI command, internal option keys, hooks, and the quarantine rename prefix all move from optrion/optrion_ to orpharion/orpharion_. There is no in-place migration: this is a one-shot rename done before any wp.org release.
1.0.3
Consolidated the protected-option rules (WordPress core options, Orpharion’s own orpharion_* namespace, and the quarantine rename namespace) into a single ProtectedOptions helper. The cleaner, importer, quarantine, and options-list filter now all derive their behavior from that one source of truth, with consistent name normalization across all of them.
1.0.2
Options list: pick rows per page (25 / 50 / 100 / 200) and jump directly to a page number.
Options list: the quarantine / export / delete action bar is now also rendered below the table, so you can act on a selection without scrolling back up.
Hardened the protected-option check to match the storage layer’s collation semantics (case-insensitive, trailing whitespace tolerant), so a non-canonical spelling cannot slip past Orpharion’s safeguards.
1.0.1
Hardened the importer to mirror the cleaner’s protected-name set: WordPress core options, Orpharion’s own internal options (orpharion_*), and the quarantine rename namespace are skipped instead of being written to wp_options. Skipped entries are reported in the import summary and the WP-CLI output.
1.0.0
Initial public release.
Per-option read tracking: every get_option() call is attributed to the real plugin or theme on the PHP backtrace.
Options list with individual signal columns (accessor, autoload, size, last accessed) and inactive-only / autoload-only / accessor-type filters.
Quarantine workflow with manifest table, automatic expiry (restore / delete / keep), and a still-accessed guard that blocks deletion of options that are still being read.
No server-side persistence of option_value content: JSON exports are browser downloads only.
REST API under /wp-json/orpharion/v1/* (requires manage_options).
WP-CLI commands for scripted pipelines, including –accessor-type, –inactive-only, and –autoload-only filters on list, export, and clean.
