fix: publish nariyanto cron diagnostics release

Author: nariyanto

.github/workflows/release.yml

@@ -39,12 +39,12 @@ jobs:
       - name: Upload build artifact
         uses: actions/upload-artifact@v4
         with:
-          name: snworks-cron-diagnostics
-          path: dist/snworks-cron-diagnostics.zip
+          name: nariyanto-cron-diagnostics
+          path: dist/nariyanto-cron-diagnostics.zip
 
       - name: Publish GitHub release asset
         if: startsWith(github.ref, 'refs/tags/')
         uses: softprops/action-gh-release@v2
         with:
-          files: dist/snworks-cron-diagnostics.zip
+          files: dist/nariyanto-cron-diagnostics.zip
           generate_release_notes: true

CHANGELOG.md

@@ -1,14 +1,14 @@
 # Changelog
 
-All notable changes to SNWorks Cron Diagnostics will be documented in this file.
+All notable changes to Nariyanto Cron Diagnostics will be documented in this file.
 
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project uses semantic versioning for GitHub releases.
 
 ## [0.1.2] - 2026-06-03
 
 ### Changed
 
-- Renamed the plugin display name, text domain, admin page slug, and package slug to `snworks-cron-diagnostics`.
+- Renamed the plugin display name, text domain, admin page slug, and package slug to `nariyanto-cron-diagnostics`.
 
 ## [0.1.1] - 2026-06-03
 
@@ -27,7 +27,7 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
 - Unusually frequent recurring hook detection for intervals shorter than one hour.
 - Overdue event counting.
 - Copyable plain-text support report.
-- Translation template for the `snworks-cron-diagnostics` text domain.
+- Translation template for the `nariyanto-cron-diagnostics` text domain.
 - Local PHP test runner and GitHub Actions CI.
 
 ### Notes

README.md

@@ -1,4 +1,4 @@
-# SNWorks Cron Diagnostics
+# Nariyanto Cron Diagnostics
 
 [![CI](https://github.com/nariyanto/wp-cron-inspector-lite/actions/workflows/ci.yml/badge.svg)](https://github.com/nariyanto/wp-cron-inspector-lite/actions/workflows/ci.yml)
 [![Latest Release](https://img.shields.io/github/v/release/nariyanto/wp-cron-inspector-lite?label=release)](https://github.com/nariyanto/wp-cron-inspector-lite/releases)
@@ -13,7 +13,7 @@ This plugin is read-only in the initial version. It lists scheduled WP-Cron even
 
 ## Screenshot
 
-![SNWorks Cron Diagnostics running on PeepSo staging](docs/screenshots/peepso-staging-cron-inspector.png)
+![Nariyanto Cron Diagnostics running on PeepSo staging](docs/screenshots/peepso-staging-cron-inspector.png)
 
 ## Current v0.1 scope
 
@@ -34,7 +34,7 @@ find . -path ./vendor -prune -o -name '*.php' -print0 | xargs -0 -n1 php -l
 bash scripts/build-release.sh
 ```
 
-The release package is written to `dist/snworks-cron-diagnostics.zip`.
+The release package is written to `dist/nariyanto-cron-diagnostics.zip`.
 
 ## Changelog
 

assets/admin.js

@@ -2,9 +2,9 @@
     'use strict';
 
     document.addEventListener('DOMContentLoaded', function () {
-        var button = document.getElementById('snworks-cron-diagnostics-copy-report');
-        var report = document.getElementById('snworks-cron-diagnostics-report');
-        var status = document.getElementById('snworks-cron-diagnostics-copy-status');
+        var button = document.getElementById('nariyanto-cron-diagnostics-copy-report');
+        var report = document.getElementById('nariyanto-cron-diagnostics-report');
+        var status = document.getElementById('nariyanto-cron-diagnostics-copy-status');
 
         if (!button || !report || !status) {
             return;

docs/wordpress-org-assets-plan.md

@@ -1,4 +1,4 @@
-# WordPress.org Asset Plan — SNWorks Cron Diagnostics
+# WordPress.org Asset Plan — Nariyanto Cron Diagnostics
 
 WordPress.org assets are committed to the assigned plugin SVN repository under `assets/` after approval. This GitHub repository keeps prepared assets under `.wordpress-org/` so they are ready to copy.
 
@@ -32,7 +32,7 @@ Add this to SVN `assets/` and reference it in `readme.txt` if we want it shown o
 
 Suggested screenshot caption:
 
-> SNWorks Cron Diagnostics shows scheduled WP-Cron events, duplicate hooks, frequent schedules, overdue events, and a copyable support report.
+> Nariyanto Cron Diagnostics shows scheduled WP-Cron events, duplicate hooks, frequent schedules, overdue events, and a copyable support report.
 
 ## Notes
 

docs/wordpress-org-submission-notes.md

@@ -1,9 +1,9 @@
-# WordPress.org Submission Notes — SNWorks Cron Diagnostics
+# WordPress.org Submission Notes — Nariyanto Cron Diagnostics
 
 Repository: https://github.com/nariyanto/wp-cron-inspector-lite
 GitHub release: https://github.com/nariyanto/wp-cron-inspector-lite/releases/tag/v0.1.2
-Release asset: `snworks-cron-diagnostics.zip`
-Target plugin slug: `snworks-cron-diagnostics`
+Release asset: `nariyanto-cron-diagnostics.zip`
+Target plugin slug: `nariyanto-cron-diagnostics`
 Version: `0.1.2`
 
 ## Short description
@@ -12,7 +12,7 @@ Find duplicate, stuck, and suspicious WordPress cron events before they cause su
 
 ## Suggested submission description
 
-SNWorks Cron Diagnostics is a read-only admin utility for WordPress support and debugging workflows. It lists scheduled WP-Cron events, highlights duplicate hooks, flags unusually frequent recurring events, counts overdue events, and provides a copyable support report.
+Nariyanto Cron Diagnostics is a read-only admin utility for WordPress support and debugging workflows. It lists scheduled WP-Cron events, highlights duplicate hooks, flags unusually frequent recurring events, counts overdue events, and provides a copyable support report.
 
 The first release is intentionally small and safe. It does not delete, reschedule, pause, or mutate cron events. It only reads WordPress' existing cron array and displays the information to administrators.
 
@@ -26,12 +26,12 @@ The first release is intentionally small and safe. It does not delete, reschedul
 - It only displays cron information to users with the `manage_options` capability.
 - The admin page is registered under **Tools → Cron Diagnostics**.
 - All admin output is escaped.
-- The plugin uses the `snworks-cron-diagnostics` text domain.
+- The plugin uses the `nariyanto-cron-diagnostics` text domain.
 - The release ZIP excludes development-only files such as `.git`, `.github`, `tests`, `docs`, and `scripts`.
 
 ## Privacy statement
 
-SNWorks Cron Diagnostics does not collect, store, transmit, or share personal data. The plugin reads scheduled WP-Cron events from the local WordPress installation and displays them only inside the WordPress admin area to administrators.
+Nariyanto Cron Diagnostics does not collect, store, transmit, or share personal data. The plugin reads scheduled WP-Cron events from the local WordPress installation and displays them only inside the WordPress admin area to administrators.
 
 The copyable support report is generated locally in the browser/admin page. Site administrators should review the report before sharing it in support tickets.
 
@@ -47,7 +47,7 @@ The copyable support report is generated locally in the browser/admin page. Site
 
 1. Log in to WordPress.org as `nariyanto`.
 2. Open the plugin submission page: https://wordpress.org/plugins/developers/add/
-3. Upload the GitHub release asset: `snworks-cron-diagnostics.zip`.
+3. Upload the GitHub release asset: `nariyanto-cron-diagnostics.zip`.
 4. Use the short description above.
 5. Add reviewer notes from this document if the form provides a notes field.
 6. Submit for review.

docs/wporg-publishing-checklist.md

@@ -1,25 +1,25 @@
 # WordPress.org Publishing Checklist
 
 Repository: `wp-cron-inspector-lite`
-Plugin slug target: `snworks-cron-diagnostics`
+Plugin slug target: `nariyanto-cron-diagnostics`
 
 ## Current status
 
 - Public GitHub repository exists.
 - Plugin has been tested on the staging site `peepso.nariyanto.id`.
 - Plugin is read-only and does not delete or mutate cron events.
 - CI runs PHP tests, readme metadata validation, and PHP syntax checks.
-- Release workflow builds `dist/snworks-cron-diagnostics.zip` for GitHub release assets.
+- Release workflow builds `dist/nariyanto-cron-diagnostics.zip` for GitHub release assets.
 - A screenshot from the staging site is available in `docs/screenshots/` for GitHub documentation.
 - WordPress.org banner/icon assets are prepared in `.wordpress-org/`.
 - Submission notes are prepared in `docs/wordpress-org-submission-notes.md`.
-- Translation template exists at `languages/snworks-cron-diagnostics.pot`.
+- Translation template exists at `languages/nariyanto-cron-diagnostics.pot`.
 
 ## Before WordPress.org submission
 
 - [ ] Finalize the v0.1.2 feature scope; avoid adding destructive cleanup in the first submission.
-- [ ] Review all user-facing strings for text domain `snworks-cron-diagnostics`.
-- [ ] Regenerate `languages/snworks-cron-diagnostics.pot` after any string changes.
+- [ ] Review all user-facing strings for text domain `nariyanto-cron-diagnostics`.
+- [ ] Regenerate `languages/nariyanto-cron-diagnostics.pot` after any string changes.
 - [ ] Run local tests: `php tests/run.php`.
 - [ ] Run PHP syntax checks: `find . -path ./vendor -prune -o -name '*.php' -print0 | xargs -0 -n1 php -l`.
 - [ ] Confirm `readme.txt` metadata: contributors, tags, requires, tested up to, requires PHP, stable tag, license.

languages/snworks-cron-diagnostics.pot languages/nariyanto-cron-diagnostics.potlanguages/snworks-cron-diagnostics.pot renamed to languages/nariyanto-cron-diagnostics.pot

@@ -2,8 +2,8 @@
 # This file is distributed under the GPL-2.0-or-later.
 msgid ""
 msgstr ""
-"Project-Id-Version: SNWorks Cron Diagnostics 0.1.2\n"
-"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/snworks-cron-diagnostics\n"
+"Project-Id-Version: Nariyanto Cron Diagnostics 0.1.2\n"
+"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/nariyanto-cron-diagnostics\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "MIME-Version: 1.0\n"
@@ -12,22 +12,22 @@ msgstr ""
 "POT-Creation-Date: 2026-06-01T14:45:42+00:00\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "X-Generator: WP-CLI 2.12.0\n"
-"X-Domain: snworks-cron-diagnostics\n"
+"X-Domain: nariyanto-cron-diagnostics\n"
 
 #. Plugin Name of the plugin
-#: snworks-cron-diagnostics.php
+#: nariyanto-cron-diagnostics.php
 #: src/AdminPage.php:14
 #: src/AdminPage.php:34
-msgid "SNWorks Cron Diagnostics"
+msgid "Nariyanto Cron Diagnostics"
 msgstr ""
 
 #. Description of the plugin
-#: snworks-cron-diagnostics.php
+#: nariyanto-cron-diagnostics.php
 msgid "Find duplicate, stuck, and suspicious WordPress cron events before they cause support issues."
 msgstr ""
 
 #. Author of the plugin
-#: snworks-cron-diagnostics.php
+#: nariyanto-cron-diagnostics.php
 msgid "Septiyan Nariyanto"
 msgstr ""
 

snworks-cron-diagnostics.php nariyanto-cron-diagnostics.phpsnworks-cron-diagnostics.php renamed to nariyanto-cron-diagnostics.php

@@ -1,12 +1,12 @@
 <?php
 /**
- * Plugin Name: SNWorks Cron Diagnostics
+ * Plugin Name: Nariyanto Cron Diagnostics
  * Description: Find duplicate, stuck, and suspicious WordPress cron events before they cause support issues.
  * Version: 0.1.2
  * Author: Septiyan Nariyanto
  * License: GPL-2.0-or-later
  * License URI: https://www.gnu.org/licenses/gpl-2.0.html
- * Text Domain: snworks-cron-diagnostics
+ * Text Domain: nariyanto-cron-diagnostics
  * Domain Path: /languages
  * Requires at least: 6.0
  * Requires PHP: 7.4
@@ -18,15 +18,15 @@
     exit;
 }
 
-define('SNWORKS_CRON_DIAGNOSTICS_VERSION', '0.1.2');
-define('SNWORKS_CRON_DIAGNOSTICS_FILE', __FILE__);
+define('NARIYANTO_CRON_DIAGNOSTICS_VERSION', '0.1.2');
+define('NARIYANTO_CRON_DIAGNOSTICS_FILE', __FILE__);
 
 require_once __DIR__ . '/src/CronEventInspector.php';
 require_once __DIR__ . '/src/AdminPage.php';
 
 add_action(
     'admin_menu',
     static function (): void {
-        (new SNWorks\CronDiagnostics\AdminPage())->register();
+        (new Nariyanto\CronDiagnostics\AdminPage())->register();
     }
 );

readme.txt

@@ -1,4 +1,4 @@
-=== SNWorks Cron Diagnostics ===
+=== Nariyanto Cron Diagnostics ===
 Contributors: nariyanto
 Tags: cron, wp-cron, debugging, support, admin
 Requires at least: 6.0
@@ -12,7 +12,7 @@ Find duplicate, stuck, and suspicious WordPress cron events before they cause su
 
 == Description ==
 
-SNWorks Cron Diagnostics is a read-only admin utility for support and debugging workflows. It helps you inspect scheduled WP-Cron events, identify duplicate hooks, flag unusually frequent events, and spot overdue jobs.
+Nariyanto Cron Diagnostics is a read-only admin utility for support and debugging workflows. It helps you inspect scheduled WP-Cron events, identify duplicate hooks, flag unusually frequent events, and spot overdue jobs.
 
 Initial scope:
 
@@ -28,7 +28,7 @@ No destructive cleanup actions are included in v0.1.2.
 == Installation ==
 
 1. Upload the plugin folder to `/wp-content/plugins/`.
-2. Activate **SNWorks Cron Diagnostics** from the Plugins screen.
+2. Activate **Nariyanto Cron Diagnostics** from the Plugins screen.
 3. Open **Tools → Cron Diagnostics**.
 
 == Frequently Asked Questions ==
@@ -44,7 +44,7 @@ Any recurring event with an interval shorter than one hour is highlighted for re
 == Changelog ==
 
 = 0.1.2 =
-* Renamed to SNWorks Cron Diagnostics with text domain `snworks-cron-diagnostics` for WordPress.org review.
+* Renamed to Nariyanto Cron Diagnostics with text domain `nariyanto-cron-diagnostics` for WordPress.org review.
 
 = 0.1.1 =
 * Renamed to a distinctive branded identity for WordPress.org review.