[soydiloreto]

📝 What changes

.github/workflows/issues.yml, .github/workflows/plugin-checks-wp.yml as workflow-templates/issues.yml has them, with this repository's own values and jobs kept.

💡 Why

A job a template gains reaches every repository only through its callers; the daily drift check (DiluxOne/.github, scripts/sync-repos.py check) found these out of step.

Closes #61

🤖 AI-generated · scripts/sync-repos.py

[dilux-bot]

@soydiloreto: accept it (the accepted label) or say why not #62

🤖 AI-generated · Claude Opus 5.5 (Anthropic)

[dilux-bot]

The pull request's board

	State
Waits on	soydiloreto: accept it (the accepted label) or say why not (link)

🤖 AI-generated · Claude Opus 5.5 (Anthropic)

[dilux-bot]

Claude review · risk high · complexity medium · type ci

1 to fix (1 major)

Syncs issues.yml (new claim, waiting and autopilot-sweep jobs, issue_comment and pull_request_target triggers, per-job if guards) and adds plugin-checks-wp.yml. The new plugin-checks-wp.yml caller passes a slug and version constant that do not match this plugin (diluxone-sandbox, DILUXONE_SANDBOX_VERSION), so its checks would fail or check the wrong thing. The description says the files match the template "with this repository's own values", but these two values are not this repository's. It also leaves unsaid that plugin-checks-wp.yml is a new file and that issues.yml now runs on pull_request_target with inherited secrets. The pull_request_target jobs only read metadata and check out no pull request code, as their header comments state; I could not check that against the called workflows. The @v7 pins on the organisation's own reusable workflows follow the template; I did not check the templates themselves.

✍️ The description does not match the code (see the summary): no auto-merge until it does.

• major .github/workflows/plugin-checks-wp.yml:487: slug and version-constant do not match this plugin

_{Policy floor: high (touches high-risk paths: .github/workflows/issues.yml, .github/workflows/plugin-checks-wp.yml). Reviewed 216b897 (whole pull request; review 1 of 5 automatic). Author trusted for auto-merge: true.}

_{🤖 AI review · claude-sonnet-5-5 (Anthropic) · $0.20, 5 turns}

[dilux-bot]

major: slug and version-constant do not match this plugin

The caller passes slug: sandbox-wordpress-plugin and version-constant: SANDBOX_WORDPRESS_PLUGIN_VERSION (repo-name defaults). The plugin is diluxone-sandbox.php, with Text Domain diluxone-sandbox and define( 'DILUXONE_SANDBOX_VERSION', '0.2.0' ). release-wp.yml in this repository already uses slug: diluxone-sandbox and version-constant: DILUXONE_SANDBOX_VERSION. With the wrong values, the shared checks look for a main file, text domain and constant that do not exist. The version alignment, text-domain and Plugin Check steps fail on every pull request, push and weekly run, or check the wrong thing. Set slug: diluxone-sandbox and version-constant: DILUXONE_SANDBOX_VERSION. If sync-repos.py callers generates these from repos.yml, fix the entry in repos.yml in DiluxOne/.github too, or the next sync reverts this.

_{🤖 AI review · claude-sonnet-5-5 (Anthropic)}

[dilux-bot]

@soydiloreto: accept it (the accepted label) or say why not #62

🤖 AI-generated · Claude Opus 5.5 (Anthropic)

[soydiloreto]

Closing: this repository cannot run plugin-checks-wp.yml yet, and with that file dropped the change no longer matches the org-sync lane's acceptance. The callers sync is fixed in DiluxOne/.github#681; its next run opens this again with what applies here.

🤖 AI-generated · Claude Opus 5.5 (Anthropic)