Store settings in rows of their own at every scale

packages/core/README.md

@@ -194,14 +194,14 @@ final class Greeting implements ComponentInterface {
 
 `Assets` registers the plugin's built scripts and styles. Built as `new Assets( $identity )` and defined once in the container, it reads the dependencies and version that wp-scripts writes beside each built file in its `.asset.php`: `register_script()` loads the script's translations from the plugin's `languages/` directory under its slug, and `register_style()` gives the stylesheet the right-to-left variant wp-scripts writes beside it. The `style-{entry}.css` chunk of a `style.scss` import takes its version from its entry's `.asset.php`. Only wp-scripts builds are supported. As a best effort, a file built outside wp-scripts, which has no `.asset.php`, registers with its modification time as its version and, for a script, no dependencies, and a stylesheet without a `-rtl.css` beside it keeps its own file on right-to-left sites.
 
-The plugin's `uninstall.php` hands its footprint, a constant of its composition root, to `Uninstaller::run()`, which unschedules the plugin's jobs on every site and deletes the rest of the footprint on each site that consents. The footprint names the plugin's data by kind: `options`, `option_prefixes`, `transients`, `network_options`, `post_types`, `comment_types`, `meta` and `meta_prefixes` by meta type, `user_meta_site`, `user_meta_global` and their `_prefixes`, `capabilities`, `tables`, `cron_hooks`, `as_hooks` and `as_groups`. A site consents through an option that holds `yes`, a key holding `yes` in an option's array, or a constant defined as `true`. The file loads the engine as the main file does, builds the plugin's identity from the root's constants, and on a site below the floors or with an incomplete build it keeps the data:
+The plugin's `uninstall.php` hands its footprint, a constant of its composition root, to `Uninstaller::run()`, which unschedules the plugin's jobs on every site and deletes the rest of the footprint on each site that consents. The footprint names the plugin's data by kind: `options`, `option_prefixes`, `transients`, `network_options`, `post_types`, `comment_types`, `meta` and `meta_prefixes` by meta type, `user_meta_site`, `user_meta_global` and their `_prefixes`, `capabilities`, `tables`, `cron_hooks`, `as_hooks` and `as_groups`. A site consents through an option that holds `yes` or a constant defined as `true`. The file loads the engine as the main file does, builds the plugin's identity from the root's constants, and on a site below the floors or with an incomplete build it keeps the data:
 
 ```php
 	public const array FOOTPRINT = array(
 		'option_prefixes'           => array( self::PREFIX . '_' ),
 		'user_meta_site_prefixes'   => array( self::PREFIX . '_' ),
 		'user_meta_global_prefixes' => array( self::PREFIX . '_' ),
-		'network_options'           => array( self::PREFIX . '_network_notices' ),
+		'network_options'           => array( 'acme_pc_network_notices' ),
 		'cron_hooks'                => array( 'acme_persona_core/migration/run' ),
 		'as_groups'                 => array( self::PREFIX ),
 	);
@@ -212,10 +212,7 @@ Uninstaller::run(
 	$acme_pc_identity,
 	$acme_pc_footprint,
 	array(
-		'consent' => array(
-			'option' => $acme_pc_consent,
-			'key'    => 'delete_data',
-		),
+		'consent' => array( 'option' => $acme_pc_consent ),
 	)
 );
 ```