Squash-merge of PR #22: adopt shared reusable CI workflow, convert PHPUnit to stubs, update branch-protection contexts.
QA-approved at 05d8094a1d. All required CI checks green.
Agent-Session: 2026-06-17-prcore-ci-deploy
Replaces the per-repo staging/smoke/production jobs with one call to
peptiderepo/peptide-e2e/.github/workflows/deploy-app.yml (target_path=wp-content/plugins/peptide-repo-core).
Validated end-to-end on the calculator pilot.
Agent-Session: cto rollout-reusable-deploy
* ci(audit): retry PR-association check to stop false positives on squash-merges
listPullRequestsAssociatedWithCommit is eventually-consistent after a squash
merge; the single immediate call intermittently flagged legit merges as
'direct push to main'. Now polls up to 5x/10s before opening an issue.
Agent-Session: cto audit-race-fix
* chore: bump plugin header to 0.5.0 to match PR_CORE_VERSION constant
The smoke job is a reusable-workflow 'uses:' call; Actions does not support
continue-on-error there, producing a 0-job workflow failure that has failed
every deploy (so v0.5.0 never reached production). Matches the prautoblogger
fix in #147. Smoke is not in deploy-production needs, so it stays non-blocking.
Agent-Session: cto restore-prcore-deploy
Co-authored-by: peptiderepo <peptiderepo@users.noreply.github.com>
- Remove invalid continue-on-error from reusable workflow call
(GitHub Actions doesn't support this property on 'uses:' jobs;
it caused 0-job workflow failures)
- Remove 'smoke' from deploy-production needs — smoke failures (e.g.
Playwright infra issues) must not block valid production deploys.
This matches the pattern already used by the theme repo.
- Smoke still runs and uploads artifacts; it's just not a gate.
- smoke job now has continue-on-error: true so a Playwright infra failure
never silently blocks a valid production deploy
- smoke.yml root cause was fixed in peptide-e2e (da79ee2) — explicit
checkout of peptide-e2e in workflow_call context
- This commit retriggers the CI/deploy pipeline for PR Core v0.5.0
Consolidates the `peptide` CPT under PR Core ownership, dropping the `pr_peptide` slug-collision that was 404ing all 89 peptide detail pages.
- POST_TYPE: pr_peptide -> peptide
- TAX_CATEGORY: pr_peptide_category -> peptide_category
- TAX_FAMILY + pr_peptide_family taxonomy removed
- Defensive post_type_exists/taxonomy_exists guards on both registrations
- Args harmonized as superset of PSA + prior PR Core (adds thumbnail support)
- Activation hook + init:999 version-change flush handler
- Uninstall scoped to _pr_core_authored flag (PSA-authored posts survive)
- Plugin version 0.1.1 -> 0.2.0, CHANGELOG in same commit
- ARCHITECTURE.md + CONVENTIONS.md updated with CPT ownership rule
QA gate verdict: PASS (qa-reviews/peptide-repo-core/2026-04-22-874f93b.md)
Sibling release: peptiderepo/peptide-search-ai#15 (PSA v4.5.0)
Known follow-up: manage_peptide_content capability is not granted to any role as of v0.2.0. No current UI/theme reads or writes PR Core-defined meta keys, so no regression. Follow-up thread to decide role assignment.
The deploy workflow references ci.yml as a reusable workflow
via `uses: ./.github/workflows/ci.yml`. Without workflow_call
in the trigger list, GitHub Actions rejects the reference.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Rsync over SSH on push to main. Runs CI first, then syncs
production files to wp-content/plugins/peptide-repo-core/
on Hostinger. Includes LiteSpeed cache purge and health check.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Drop PHP 8.0 from matrix — DTOs use readonly properties (8.1+)
- Add composer.json with PHPCS/WPCS as dev dependencies
- Add phpcs.xml.dist for WordPress coding standard config
- Use dealerdirect/phpcodesniffer-composer-installer for auto path setup
- Separate lint jobs: PHP syntax (8.1/8.2/8.3) + PHPCS + file-size
- Update Requires PHP header to 8.1
- Update ARCHITECTURE.md file tree
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
PHPCS 4.0.1 was installed first via sequential composer require,
locking the version before WPCS could constrain it. WPCS 3.x
requires PHPCS ^3.x. Fix: install all packages in one command
with --with-all-dependencies and pin PHPCS to ^3.13.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
