Hexa JPN Tools

Hexa JPN Tools owns JPN Miami's WordPress-specific event, host, notification, shortcode, and Code.Hexa integration behavior. The plugin replaces the legacy jpn-structure plugin without changing its event post type, taxonomies, ACF keys, shortcodes, options, or stored content.

Identity

• Display name: Hexa JPN Tools
• WordPress folder slug: hexa-jpn-tools
• Main file: hexa-jpn-tools.php
• Canonical basename: hexa-jpn-tools/hexa-jpn-tools.php
• PHP namespace: Hexa\JpnTools
• Repository: mikeyperes/hexa-jpn-tools

Code.Hexa contract

The authenticated REST namespace is hexa-jpn/v1. It uses WordPress's native Application Password authentication and the dedicated manage_jpn_integration capability. The plugin creates a minimal hexa_jpn_integration role with that capability during activation.

Code.Hexa should use these endpoints instead of database access, HTML scraping, or WordPress internals. The contract never returns application passwords, emails, raw host access codes, database credentials, or authentication state.

Hexa WP Core

The plugin vendors and registers Hexa WordPress Plugin Core. Core owns package selection, plugin update behavior, Core package update behavior, runtime identity, and shared safety checks. JPN-specific event and host behavior stays under Hexa\JpnTools.

Verification

php tests/run.php
php tests/architecture.php
find . -name '*.php' -type f -print0 | xargs -0 -n1 php -l

After installation, run the WP-CLI smoke and REST fixtures from the exact live WordPress root as the site owner:

wp eval-file wp-content/plugins/hexa-jpn-tools/tests/wp-bootstrap-smoke.php
wp eval-file wp-content/plugins/hexa-jpn-tools/tests/wp-rest-fixture.php

The REST fixture creates temporary draft records and removes them in finally. It never publishes an event.

See docs/architecture.md, docs/api-contract.md, and docs/migration-runbook.md.