# SiloNectra source and asset reproduction

Copyright (c) Digitaltcab. Licensed GPLv2 or later; see `LICENSE.txt`.

The complete preferred editable JavaScript and CSS source is included in `src/`.
The PHP files in the plugin root and `includes/` are also distributed as source.
No private source repository or account is needed to inspect or modify this release.

## Source-to-runtime map

| Editable source | Runtime file | Purpose |
| --- | --- | --- |
| `src/pro.js` | `assets/pro.js` | Dashboard, reports, linking workspace and Article Inspector |
| `src/locale.js` | `assets/locale.js` | Dashboard and editor interface language dictionaries |
| `src/assistant.js` | `assets/assistant.js` | Classic, Gutenberg and supported Elementor editor assistance |
| `src/audit.js` | `assets/audit.js` | Article link audit interface |
| `src/pro.css` | `assets/pro.css` | Main dashboard, including Article Inspector |
| `src/analytics-v45.css` | `assets/analytics-v45.css` | Reports and silo/network views |
| `src/themes.css` | `assets/themes.css` | Dashboard themes and index status |
| `src/assistant.css` | `assets/assistant.css` | Editor assistance styles |
| `src/audit.css` | `assets/audit.css` | Article audit styles |

## Reproduce the assets

1. Install Node.js 18 or later on a development machine.
2. Open a terminal in the `silonectra` plugin directory.
3. Run `node tools/build-assets.mjs`.
4. Run `node tools/build-assets.mjs --check` to verify the source/runtime pairs.

The included build tool uses only Node built-ins. It copies each JS/CSS source
file to the matching runtime path without transformations. There are no npm
dependencies, minification, mangling, bundling or transpilation steps. The output
is reproducible byte-for-byte and keeps readable names and formatting.

Normal WordPress installation and use require PHP/WordPress, not Node.js.
All required source and reproduction tools ship inside the plugin ZIP.

## Maintaining a change

Edit the file in `src/`, run the reproduction command, and distribute both the
updated `src/` and `assets/` files. `--check` returns a nonzero exit code if any
pair differs. Reviewers can directly compare the two files or regenerate all
runtime assets without downloading a dependency.

PHP files are executed directly and do not have an asset build step.
