---
title: "Changelog | Pinstripe docs"
description: "All notable changes to this project."
url: https://pinstripe.apps.wayne.edu/docs/changelog.html
llms: https://pinstripe.apps.wayne.edu/llms.txt
generator: Squire agent-ready
---

# Changelog [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#changelog)

All notable changes to Pinstripe are documented here.

## Unreleased [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#unreleased)

- Fixed: the contributing guide names Preflight 0.9.0, the tag CI pins, where it still said 0.8.0. Content only.
- Changed: the deploy kit is Squire 0.11.1 (was 0.10.7): the release script fetches PROCTOR when `--no-dev` left it out and installs the frontend from a `yarn.lock`, the HAProxy pin is current, the fallback base follows the app's PHP line, and the parity scripts carry the deprecation note.
- Changed: CI pins Preflight 0.9.0 (components and the a11y checker copy).
- Changed: `deploy/` requires PROCTOR `^0.16`, whose `ci-pipelines` check no longer asks for a GitHub workflow (D-069); `^0.15` failed the `wayneui-copies` job.
- Removed: the GitHub Actions workflow; CI runs on git.wayne.edu only (the GitHub copy is a mirror).
- Site: the line under the hero's buttons says "Version 0.4.0 is cut" (it still said 0.3, with 0.3.0's news). The number carries `data-docs-version` like the hang tag, so the docs builder rewrites it at every release and `composer docs:check` fails while it is stale; the words name no feature and link to the "Just off the cutting table" note, which the release steps already rewrite. New `FrontPageTest::testTheHeroNoteWearsTheVersionStamp` fails `composer ci` if the number is typed by hand again.
- Docs: the README shows the Docker command for `composer ci`, so the checks run with no local PHP.

## 0.4.0 (2026-11-11) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-4-0-2026-11-11)

- Docs: every install line says `^0.4` (README, front page, its agent prompts, the Raw PHP, Laravel and Proof pages), since `^0.3` does not allow 0.4.0, and the Upgrading section's steps say to move the constraint rather than `composer update`. The front page's "Just off the cutting table" note names 0.4.0 and its two opt-in Rector presets.
- CI pins Preflight 0.8.0 on GitLab; MAINTAINING.md and the contributing guide say so (the GitHub workflow stays on 0.5.0, the newest tag on the mirror it can call).
- Added: `rector/strict-types.php`, an opt-in Rector preset for the careful route to strict types on an old app. It runs Rector's `SafeDeclareStrictTypesRector` and nothing else, so it adds `declare(strict_types=1)` only to files whose calls, returns and property assignments already pass the types they ask for, and leaves the rest for a later run. Opt-in, so no app sees a change until it points a config at it. New fixture `tests/fixtures/rector-strict-types` with `PresetsTest::testRectorStrictTypesPresetDeclaresOnlyTheSafeFile` and `testRectorStrictTypesPresetLeavesTheCoercingFileAlone`; the README, Require strict types and Rector guides show it, and BEST_PRACTICES.md gains the row (24 rows, 24 Enforced).
- Added: `rector/levels.php`, an opt-in Rector preset for an app that has never met Rector. It returns a function: `$levels(deadCode: 0)` runs only the first dead-code rule, and you raise the number one merge request at a time, then start `typeCoverage`, `codeQuality` or `php` the same way (each family stays off until named, and naming none throws). It wraps Rector's own `withDeadCodeLevel`, `withTypeCoverageLevel`, `withCodeQualityLevel` and `withPhpLevel`, and leaves out the import tidying and Laravel rules that touch every file. Opt-in, so no app sees a change until it points a config at it. New fixture `tests/fixtures/rector-levels` with four `PresetsTest::testRectorLevelsPreset*` tests; the README and Rector guide show the climb, and BEST_PRACTICES.md gains the row (25 rows, 25 Enforced).
- Site: the front page's "Just off the cutting table" note says what 0.3.2 brought (it still led with 0.3.0), and new `tests/FrontPageTest.php` fails `composer ci` while the note names anything but the newest CHANGELOG release, so it cannot fall behind again. The release steps in MAINTAINING.md and on the Releasing page say to rewrite it in the release commit.
- Site: the install card's "`^0.3` gets you" line names 0.3.2, the current release (it still said 0.3.1). The version carries `data-docs-version` like the hang tag, so the docs builder rewrites it at every release and `composer docs:check` fails while it is stale.
- Docs: Banned calls gains "Type the connection, or the ban cannot see it": the PDO and mysqli bans match by the connection's type, so a joined query on an untyped `global $db` passes, and one `@var \PDO` (or a typed property) gets it reported. It was one line under "Other ways out"; now it is its own section with both halves proven by new fixture `UntypedConnection.php` and `PresetsTest::testPhpStanSeesJoinedSqlOnlyOnATypedConnection` (raw and strict cuts). No rule changed.
- Docs: the Upgrading page has a draft section for the next release (the two opt-in Rector presets, no breaking change), and its three oldest headings carry their dates. New `tests/UpgradingTest.php` fails `composer ci` while a CHANGELOG release has no Upgrading section, or the two disagree on a date or the order, so a release cannot ship without its fitting notes. The release steps in MAINTAINING.md and on the Releasing page say to rename the draft in the release commit.
- Tests: the TypeScript preset's typed linting is proven, not only claimed. New fixtures in `tests/js/typed` (a `tsconfig.json`, a clean `.ts` file, and a `save()` nobody awaits in `floating.ts` and `FloatingSave.vue`) and three `npm test` cases: the clean file has no findings, and each floating promise fails with `@typescript-eslint/no-floating-promises` as an error. The README and Vue guide gain "Typed linting" (what it catches, that it reads the app's `tsconfig.json`, and to run it in CI), and the front page's mirror gains the pair. No preset changed.
- Site: the front page's mirror ("Every piece has a mirror") names every fixture the tests run, not half of them. "It fits" gains `BoundSql` and `SecureTransport` (the clean ways past the bans), "It catches" gains `Leftovers` and `JoinedSql`, and a new row of size labels sews on one per app shape Sourdough starts (raw PHP, raw PHP with Vue, Laravel with Blade, Blade with Vue, Inertia and Vue), each with its fixture's name. The labels drop in and their running stitch sews round one after another; under reduced motion they are simply there.
- Site: Parity's hanger on the front page's rail links its site, parity.apps.wayne.edu, like every other part's. It hung there unlinked while Parity had no site; now it has one, and the stack's environment script already points a pre-production page at Parity's pre-production site.
- Site: the hero's hang tag can be read on a phone. Its handwriting was 12px and its labels 7px at 390 px wide; now the writing never drops below 17px (with a hairline stroke behind the thin hand), the labels never below 9px, and the labels and values line up in two columns like a real ticket. The tag is wider, and the extra width hangs out past the cloth into the margin, so it covers no more of the label than before. The README hero is rebuilt to match.

## 0.3.2 (2026-11-10) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-3-2-2026-11-10)

- Changed: the deploy layer requires PROCTOR ^0.15 (locked 0.15.0, was ^0.12): 0.13 checks the release cooldown against the CREED policy, 0.14 adds `script-pair` and 0.15 adds `mysql56-ci`; all only warn, nothing breaks.
- Docs: the Proof page says its 82-app run used the presets as they were on `main` on 2026-11-05, not "as they are on main".
- Added: `node scripts/readme-art/build.mjs --check` rebuilds the README art in a temp folder and fails when `docs/readme/` is stale (SVGs byte for byte, images by pixels within a small tolerance), and the `readme-art` CI job runs it. The license badge says `license`, not `licence`.
- Changed: the deploy layer requires PROCTOR ^0.12 (locked 0.12.0, was ^0.11): two new warning-only checks, nothing breaks.
- Docs: the proof page's last run is 2026-11-10 at e42cf2f (113 PHP tests, 36 npm tests with the raw-vue and laravel-inertia fixtures).
- Changed: the deploy kit is Squire 0.10.7 (was 0.10.6): it ships a `.gitattributes` that pins line endings, so the deploy layer clears PROCTOR's line-ending warnings.
- Changed: the Vue presets let Inertia page components under `Pages/` or `pages/` have one-word names such as `Index` and `Show` (`vue/multi-word-component-names` is off there only).
- Tests: a Laravel plus Inertia plus Vue fixture (tests/fixtures/laravel-inertia) proves the presets on WELD's app shape, so every stack app shape now has a fixture.
- Docs: the ban tables in the README and on the Banned calls page name the OWASP ASVS 5.0 requirement each ban enforces (V1.2.4, V1.3.2, V12.3.2, V13.4.2, and V15.3.3 as the closest fit for `extract()`). The messages keep their OWASP Top 10 tags.
- Tests: a raw PHP plus Vue fixture (tests/fixtures/raw-vue) proves the presets on that app shape too, with one planted PHP error and two planted Vue defects.
- Changed: the GitHub workflow calls Preflight 0.5.0 (was 0.1.4), now that GitHub's copy of Preflight has the tag; MAINTAINING.md and the contributing guide name the 0.5.0 pins.
- Changed: the docs, agent-ready and deploy kits are Squire 0.10.6 (was 0.10.5): the docs builder and agent-ready generator see every file on Docker Desktop mounts.
- Site: `assets/stack-env.js` knows Parity, so a pre-production page links Parity's pre-production site and a dev page links its local `site/` folder. Until now Parity, of all parts, was the one link that ignored its environment.
- Changed: Deploy kit refreshed to Squire 0.10.5 (was 0.10.2).

## 0.3.1 (2026-11-09) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-3-1-2026-11-09)

A patch: no preset passes or fails anything it did not in 0.3.0. It adds proof and docs (PHPStan findings in the merge request, the fix for SQL kept in `.sql` files), keeps Code Quality reports when a lint job fails, and brings the deploy kit and CI pins up to date.

- Docs: Parity joins the party. The README cast ("Fifteen parts, one fitting room") and the front page's rail carry Parity next to Squire, with its spirit-level mark: the stack's new tool that runs Citadel on your computer (its PHP image, its proxy and MySQL 5.6). 0.1.0 is coming and it has no site yet, so its tag links nowhere. With fifteen parts the rail hangs three rows of five on wide screens, so no part is left hanging alone at the end. Every good suit gets a fitting at home before the big day, and the hem comes out level.
- Changed: the deploy kit is Squire 0.10.0 (was 0.7.1): release.sh keeps Composer and npm download caches in the app folder and the gate takes SQUIRE_PHP_RUNTIME; the compose file, health.php and .env.squire.example follow the template, and the portable image files are added (build.sh keeps its deliberate SQUIRE_BUILD_REVISION=2 marker).
- Docs: every install line says `^0.3` (it said `^0.1`, which stops at 0.1.4), with the one `composer config repositories` line that installs 0.3.0 from git.wayne.edu while Packagist's GitHub mirror trails the release; the npm notes say the ESLint and Prettier presets have not changed since 0.1.4. The front page drops its "0.1.4 on Packagist and npm" note and a "coming soon" chip for the CREED PHP floor (built in 0.2.0), keeps a Docs link in the header at phone width, and gains House rules: a notice of the banned call families with their OWASP tags, struck through in chalk and stamped as they scroll in (already struck and stamped with reduced motion).
- Docs: truth pass. The `laravel-vue` fixture's Vue side runs under `npm test`, not `composer ci` (README, Laravel guide); MAINTAINING.md and Contributing list all five `composer ci` steps, the Node 22, 24 and 26 matrix, every CI component and job, and `spaze/phpstan-disallowed-calls` among the runtime dependencies; the release steps no longer say to set the version twice, and `npm pack` lists `LICENSE` too; Banned calls says `ociparse()` is reported as deprecated on every supported PHP, not only 8.4 and newer; the Baselines guide gains the `legacy` opt-in and `--composer=<path>`; the Vue guide covers the error-level presets and their `-warn` twins; Upgrading 0.1.3 no longer lists the docs site (it shipped in 0.1.4); and BEST_PRACTICES.md marks three rows proven in one direction only (`pint/laravel.json`, `pint/laravel-strict.json`, ESLint GitLab output) as Checked, a status it now defines.
- Changed: CI's `composer-ci` and `wayneui-copies` jobs, and the Docker-only command in MAINTAINING.md and Contributing, use Composer 2.11.1 pinned by its multi-arch list digest (was 2.10.3, which is no longer maintained; 2.11 fixes GHSA-c968-33g3-wh7p and GHSA-fm2w-xgf2-f9fh).
- Changed: the deploy kit is Squire 0.10.2 (was 0.10.0): the fallback base names its images in full and copies Composer 2.11.1 from a `COMPOSER_IMAGE` build argument, `.squire/php.ini` sets `session.cookie_samesite = Lax`, and the portable image drops `node_modules/` after the build; build.sh takes the template's note on what a Citadel Update runs and keeps its deliberate SQUIRE_BUILD_REVISION=2 marker.
- Changed: the front-page deploy layer requires HELMET `^1.3` (was `^1.0`, locked 1.3.0, was 1.0.0), PROCTOR `^0.11` (was `^0.8`, locked 0.11.1, was 0.8.0) and CREED `^0.1.8` (was `^0.1`, locked 0.1.8, was 0.1.7). `proctor check` still passes on `deploy/`.
- Docs: MAINTAINING.md names the maintainer as a role (the stack maintainer), reached through an issue on git.wayne.edu, not a person; the CI file's cache comment drops an internal decision number.
- Added: the three presets the truth pass marked Checked are Enforced again, each now proven in both directions: `PresetsTest::testPintLaravelPresetRejectsTheMessyFixture` (`pint/laravel.json` fails the messy fixture), `PresetsTest::testPintLaravelStrictPresetAcceptsTheStrictTypesLaravelCleanFixture` (`pint/laravel-strict.json` passes a new Laravel-style clean fixture, `tests/fixtures/strict-types/laravel-clean`), and a `gitlab-formatter.test.mjs` case where the clean Vue fixture gives an empty Code Quality report. Two stale comments are fixed: the GitHub workflow names its real Preflight pin (0.1.4, not 0.1.2), and `PresetsTest` says the `ociparse()` deprecation is expected on every PHP version, not only 8.4 and newer.
- Added: BEST_PRACTICES.md (and its docs page) ends the table with a tally, today 22 rows, 22 Enforced, 0 Checked, and `BestPracticesTest::testTheTallyCountsTheTable` recounts it on every run, so a new row or one slipping back to Checked moves the tally in the same change.
- Docs: Banned calls shows the fix for the joined-SQL report older apps meet most: SQL kept in `.sql` files, read by one helper typed `@return literal-string` with a single reasoned ignore (its file name is `literal-string` too, so a request value cannot pick the file). It also says to type a wrapper's SQL parameter `literal-string` and never baseline it, because a plain-`string` wrapper is reported once, inside, and hides every caller. Both are proven: new fixtures `SqlFiles.php` (green in the raw and strict cuts) and `JoinedThroughAWrapper.php` (each joined caller reported as `argument.type`, the loose wrapper once), with `PresetsTest::testPhpStanAcceptsSqlReadFromFilesThroughATypedWrapper` and `PresetsTest::testPhpStanReportsSqlJoinedThroughAWrapperAtTheCaller`. No rule changed.
- Added: "Show PHPStan findings in the merge request" (README and the Raw PHP guide): an `analyse:gitlab` script with PHPStan's own `--error-format=gitlab`, each finding named by its identifier. New `PresetsTest::testPhpStanGitlabFormatReportsTheNullBugAsCodeQualityJson` and `testPhpStanGitlabFormatIsAnEmptyArrayForTheCleanFixture` prove both sides, and BEST_PRACTICES.md gains the row (23 rows, 23 Enforced).
- Fixed: the Pint, PHPStan and ESLint Code Quality snippets set `artifacts: when: always`. Without it GitLab keeps a job's artifacts only when the job passes, so a lint job that found something, the one time the report matters, uploaded nothing.
- Docs: no internal decision numbers in public text. This changelog's 0.2.0 and 0.1.5 entries, the CI file, the deploy layer's composer.json and a comment on the front page drop numbers that pointed into a private repository, and the old entries say "an internal GitLab" instead of naming it.
- Fixed: the Composer package's description (what Packagist shows) names the Rector preset and the banned calls; it said "shared Pint and PHPStan presets".

## 0.3.0 (2026-11-09) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-3-0-2026-11-09)

- Added: every cut bans SQL joined from strings (`pinstripe.banned.joinedSql`, OWASP A05:2025): a variable concatenated, interpolated or `sprintf()`'d into the SQL given to `PDO::query()`, `prepare()` or `exec()`, mysqli's `query()`, `prepare()`, `mysqli_query()` and the rest, `oci_parse()` (and the old alias `ociparse()`), or Laravel's `DB::select()`, `insert()`, `update()`, `delete()`, `statement()`, `scalar()`, `cursor()` and `fromQuery()`. No taint rule: spaze/phpstan-disallowed-calls asks for PHPStan's own `literal-string` type, so literal SQL with bindings, class constants and literal pieces joined together pass; Laravel already types `DB::raw()`, `DB::unprepared()` and the `*Raw()` builder methods that way, and a test now holds it to that. Breaking for apps that build SQL from variables. New fixtures `JoinedSql.php`, `BoundSql.php`, `JoinedQueries.php` and `BoundQueries.php`.
- Docs: the Best practices docs page carries BEST_PRACTICES.md word for word again (it had fallen behind: no ESLint GitLab output row, no banned-call rows), and BEST_PRACTICES.md gains rows for `phpstan/strict.neon` and `phpstan/disallowed.neon`. New `tests/BestPracticesTest.php` keeps them in step: every test and file the table names exists, each row has one known status, an Enforced row names its proof, and the docs page matches.
- Fixed: the `Http::withoutVerifying()` ban (the static entry) carries the same tip as the others, linking to the Banned calls page and the CREED rule; `BannedCallLinksTest::testEveryBanCarriesAnIdentifierAndATip` now reads `phpstan/disallowed.neon` and fails on any entry without a message, identifier or tip.
- Added: every cut bans TLS checks turned off: `curl_setopt()` and `curl_setopt_array()` with `CURLOPT_SSL_VERIFYPEER` false or `CURLOPT_SSL_VERIFYHOST` 0 (`pinstripe.banned.curlVerifyOff`), `stream_context_create()` with `ssl` `verify_peer` or `verify_peer_name` false or `allow_self_signed` true (`pinstripe.banned.streamVerifyOff`), and Guzzle's `verify` option set to false through Laravel's `withOptions()`, `new GuzzleHttp\Client()` or a request's options (`pinstripe.banned.verifyFalse`), each tagged OWASP A02:2025. The `curl_setopt()` ban is Pinstripe's first PHPStan rule of its own (`src/PHPStan/CurlVerifyOffRule.php`), since it needs the option and the value together; the rest are spaze/phpstan-disallowed-calls entries. Breaking for apps that skip the certificate check. New fixtures `InsecureTransport.php`, `SecureTransport.php`, `VerifyFalse.php`, `VerifiedHttp.php` and the Laravel app's `banned/InsecureCurl.php`.
- Added: Laravel's own `dd()` and `dump()` methods are banned too (`$users->dd()`, `DB::table('users')->dumpRawSql()`, `$request->dump()`, `Http::get($url)->dd()`, `Http::dump()` and the rest of the family), under the functions' identifiers `pinstripe.banned.dd` and `pinstripe.banned.dump`; only methods Laravel declares match, so an app's own `dump()` and the schema dump behind `php artisan schema:dump` pass. Breaking for Laravel apps with one left in. New fixtures `tests/fixtures/laravel/src/LeftoverDebugMethods.php` and `SchemaDump.php`.
- Changed: CI pins the Preflight components to 0.4.0 (the proctor job clones the full history, so the override-approver check can read git blame).

## 0.2.0 (2026-11-08) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-2-0-2026-11-08)

- Changed: every banned call's tip links to the CREED rule it enforces (code handbook, Banned patterns) as well as to Pinstripe's banned-calls page; `tests/BannedCallLinksTest.php` keeps it that way.
- Docs: the README says how CREED's PHP floor reaches the tools (PROCTOR's php-floor check, then Booster; the presets keep reading composer.json); "Coming next" is empty for now, since both items it named are built.
- Changed: the deploy layer runs Squire's kit 0.7.1 (was 0.6.0): `.squire/php.ini` no longer sets the deprecated `session.sid_*` lines, web requests get a `disable_functions` list and Apache hardening (`.squire/php-web.ini`, `.squire/apache-hardening.conf`), and opcache gets production settings with `SQUIRE_OPCACHE_VALIDATE` as the one switch.
- Added: CI runs Preflight's a11y component (0.3.1) on site/, every page in light and dark at 320 and 1280 px with the WCAG 1.4.10 reflow check, blocking.
- Changed: CI pins the Preflight components to 0.3.1 (fixed cache keys, and caches saved even when a job fails).
- Changed: CI saves its Composer and npm caches even when a job fails, so a retry after a dropped download fetches only what is missing.
- Changed: CI caches Composer and npm downloads under a fixed key, so a lock change downloads only what changed.
- Changed: HELMET moves to `^1.0`, its first stable release, wherever this repo requires it.
- Fixed: the docs menu closes with Escape and hands focus back to its button (docs kit synced from Squire).
- Fixed: the docs kit's copy button no longer covers the first line of code when it says Copied or Failed: over the code it keeps its resting width and shows a check or a cross when the word does not fit (docs kit synced from Squire).
- Fixed: the front page's version chip shows the full version the docs show (size 0.1.4, was size 0.1). It carries `data-docs-version` now, so the docs builder (synced from Squire) rewrites it at every release and `composer docs:check` fails while it is stale.
- Changed: the deploy layer requires PROCTOR ^0.8 (locked 0.8.0).
- Changed: the pipeline pins every Preflight CI component to 0.3.0 ([preflight@0.3.0](mailto:preflight@0.3.0)); component image inputs are plain image names, since Preflight adds the Dependency Proxy prefix itself.
- Added: a test that proves `npm install --ignore-scripts` stops a postinstall script, and the eslint-config-prettier floor is ^10.1.8, past the releases hit by CVE-2025-54313.
- Added: banned calls. Every PHPStan cut includes the new `phpstan/disallowed.neon`, which bans `eval()`, `extract()`, `var_dump()`, `dd()`, `dump()` and Laravel's `PendingRequest::withoutVerifying()` (the `Http::withoutVerifying()` facade call too) through `spaze/phpstan-disallowed-calls` `^4.15` (now in `require`, locked 4.15.0, loaded by the extension installer). Each message says why and what to use instead, ends with its OWASP Top 10:2025 tag (A05 Injection or A02 Security Misconfiguration), and has a stable identifier (`pinstripe.banned.*`) for a reasoned ignore. Breaking for apps with one left in: a leftover `dd()` now fails the pipeline. `md5()`, `sha1()`, `rand()` and `mt_rand()` are not banned; that call is open. New README section and docs page, Banned calls; new fixtures `tests/fixtures/raw-disallowed`, `tests/fixtures/laravel/src/InsecureHttp.php` and `tests/fixtures/laravel-app/banned`.
- Added: the Rector preset turns on the composer-based Laravel sets (`withComposerBased(laravel: true)`); apps that install driftingly/rector-laravel get the Laravel upgrade rules for their installed version, and apps without it see no change.
- Changed: the front page's `deploy/build.sh` revision marker is 2, for a Citadel build-cache test (does a full Update run the edited `build.sh`?).
- Fixed: the pipeline's PROCTOR jobs no longer pass `--policy`, which PROCTOR 0.7 refuses in CI; PROCTOR checks against the CREED policy it bundles.
- Changed: the front page's deploy layer (`deploy/`) runs Squire's kit 0.6.0 (was 0.5.0): `scripts/release.sh` asks PROCTOR's deploy gate for a go or no-go on each release (a report, not a stop, unless `SQUIRE_PROCTOR=enforce`), and `.env.squire.example` lists the new setting. The layer's pins move to HELMET `^0.4` (locked 0.4.0) and PROCTOR `^0.7` (locked 0.7.0).
- Fixed: the front page says Sourdough starts all five app shapes and that every app it makes comes with Pinstripe on; it said raw PHP only, and that Sourdough apps did not include Pinstripe yet.
- Changed: CI caches Composer and npm downloads per lock file (`.composer-cache`, keyed on `composer.lock` and `deploy/composer.lock`, and `.npm-cache`), so a pipeline stops fetching every package from Packagist and npm on every run. Images already come through the Dependency Proxy.
- Changed: the front page's deploy layer (`deploy/`) runs Squire's kit 0.5.0 (was 0.3.4): `oracle-check.php` arrives, `scripts/release.sh`, `scripts/parity.ps1` and `.squire/base-fallback.Dockerfile` take the new templates, and `docker-compose.squire.yml`, which Renovate had edited, is Squire's template again, so `squire init --check` passes. `site/assets/stack-env.js` takes the stack's one copy, with bindingless catch blocks.
- Changed: The canonical repository is git.wayne.edu; docs, links and package metadata no longer point at the archived internal copy.
- Added: The Proof page records its last run.

## 0.1.5 (2026-11-09) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-1-5-2026-11-09)

A patch on the 0.1 line, cut from 0.1.4 on the `0.1.x` branch, for consumers that pin `^0.1` (Booster among them). It changes no preset; 0.2.0 and 0.3.0 already carry the same fix.

- Fixed: the deploy kit's lock (`deploy/composer.lock`) names git.wayne.edu and GitHub for CREED, HELMET and PROCTOR instead of the archived internal host.
- Changed: The canonical repository is git.wayne.edu; docs, links and package metadata no longer point at the archived internal copy.

## 0.1.4 (2026-11-06) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-1-4-2026-11-06)

- Fixed: `pinstripe-baseline` mutes deprecations while it loads the app's autoloader, so an old package in the app no longer prints PHP warnings ahead of the count a script reads (found by the 2026-11-05 proof run; new test in tests/BaselineTest.php).
- Added: a public Proof page (`docs/reference/proof.md`, under Reference): the presets run against 82 Wayne State applications, what held, what the run caught in Pinstripe, and what it does not prove.
- Docs: the install steps say to rerun `composer require` with `-W` when a package the app already locks blocks it; Adopting on an existing app covers errors PHPStan cannot baseline and keeping Pint off bundled third-party code.
- Security: the front-page deploy layer moves to Symfony 7.4.23 (symfony/http-foundation and symfony/yaml advisories, including CVE-2026-118514).
- Changed: the docs, README and front page say the npm package, `@waynestate/pinstripe`, is at 0.1.3 (published); the docs pages' dark mode is now charcoal suiting instead of the green cloth, and wide tables shade the edge they scroll toward.
- Changed: the docs pages wear the front page's look: its header and main menu (Docs marked current), Bodoni titles with the gold chalk line, pattern-piece callouts and pager, the gold Copy pill and the green footer, plus a dark mode cut from the green cloth. The theme lives in `docs/_header.html` and `docs/theme/pinstripe.css`, named by the `theme` key in `docs/docs.json`; the vendored docs builder and kit are synced from Squire's unified builder (theme hook, callouts, copy button and keyboard fixes).
- Added: `min-release-age=3` to the repo `.npmrc` beside the existing `ignore-scripts=true`, with a comment naming the unit (days) and the agreeing Renovate `minimumReleaseAge` rule, so npm waits 3 days before installing a freshly published release and never runs dependency lifecycle scripts; the README gains a "Supply chain" section that explains both settings and tells apps to copy both lines into their own `.npmrc`.
- Changed: `pinstripe-baseline` now requires the app's composer.json to carry `"extra": { "pinstripe": { "legacy": true } }` before it counts or checks a baseline; this is breaking for existing baseline users, who must add the flag, because a baseline is only for apps adopting Pinstripe late and new apps never set it.
- Added: `--composer=<path>` to `pinstripe-baseline count` and `check` (default `composer.json` in the current working directory), so tests and monorepos can point at another composer.json.
- Changed: the ESLint presets (`eslint/javascript.js` and `eslint/typescript.js`) fail lint on every Vue and accessibility finding: rules the plugins' recommended configs report as warnings are raised to errors, so the editor, a local `npm run lint` and CI agree on what fails. Pre-1.0 break: apps that keep the old behavior (those findings as warnings) spread the new `-warn` export instead.
- Added: `eslint/javascript-warn.js` and `eslint/typescript-warn.js`, exported as `@waynestate/pinstripe/eslint/javascript-warn` and `@waynestate/pinstripe/eslint/typescript-warn`, which keep the exact previous behavior (the plugins' plain recommended configs, warnings stay warnings) for apps adopting the stricter presets gradually; `tests/js/presets.test.mjs` gains four tests around a `tests/js/warn-tier` fixture whose only findings (`vue/attributes-order`, `vue/no-v-html`) were warnings before, proving the strict presets report them as errors and the `-warn` presets keep them as warnings.
- Added: a docs site (site/docs/) built by the shared docs builder from docs/, checked in composer ci.
- Added: `eslint-formatter-gitlab` as a dependency and `tests/js/gitlab-formatter.test.mjs`, which lints the bad Vue fixture with the javascript preset, runs the results through ESLint's `gitlab` formatter, and asserts the Code Quality report is a non-empty JSON array whose findings each carry a description, fingerprint, severity and location, so `eslint --format gitlab` shows ESLint findings in GitLab merge requests; the README gains a "Show ESLint findings in the merge request" note for the Vue section.
- Added: `prettier-plugin-blade` (pinned to 3.3.3, no caret) as a dependency and a `*.blade.php` override in `prettier/index.json` (parser `blade`, 4-space tab width), so the Prettier preset formats Blade views; `tests/js/blade.test.mjs` checks a clean and a messy Blade fixture through Prettier's Node API, and the README gains a "Format Blade views" section with the one-time reformat command and an adopting note.
- Changed: Blade files now format with prettier-plugin-blade; the first run rewrites every Blade file (4-space indent, a space after directive names such as `@vite (`, void tags self-closed), so reformat in its own commit.

## 0.1.3 (2026-11-03) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-1-3-2026-11-03)

- Added: `docs/adr/0001-phpstan-level-and-baseline-policy.md`, the ADR recording the PHPStan level 8 cut, the baseline policy (generated once for an existing app, never for new code, and only ever shrunk), and the `composer ci` / `composer-ci` pipeline enforcement point, plus a README note that apps adopting Oxlint keep ESLint for `.vue` files because the Vue and accessibility plugins run only in ESLint.
- Changed: the install instructions now include `composer config allow-plugins.phpstan/extension-installer true`, so a non-interactive install works.
- Added: a Node matrix to the `npm-test` jobs on GitLab and GitHub (Node 22, 24 and 26), so the ESLint and Prettier presets are proven on all three majors; the floor stays 22.13.
- Changed: the front-page deploy layer pins HELMET ^0.3, PROCTOR ^0.4 and CREED ^0.1 (lock: HELMET 0.3.0, PROCTOR 0.4.0, CREED 0.1.6).
- Changed: CI pins Preflight 0.1.4 (GitLab component includes and the GitHub reusable workflow tag).
- Added: `tests/fixtures/laravel-vue`, a combined Laravel + Vue fixture with `resources/js` beside `app/`, so one app tree is linted by Pint and PHPStan (PHP side) and ESLint and Prettier (Vue side) on every run; it carries one planted PHP error (`bad/BrokenGreeting.php`) and two planted Vue defects (`resources/js/bad/Broken.vue` missing a `v-for` key, `resources/js/bad/NoAlt.vue` missing an `alt`), and `tests/js/presets.test.mjs` gains five tests for the Vue side.

## 0.1.2 (2026-11-03) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-1-2-2026-11-03)

- Added: PHPUnit tests for the PHPStan ignore rules in `phpstan/base.neon`, which run the raw preset against three one-class fixtures in `tests/fixtures/raw-ignores` and prove an `@phpstan-ignore` without a comment fails, an ignore that matches no error fails, and a commented ignore passes.
- Added: PHPUnit tests for Pint's `--format=gitlab` output, which prove the messy `per` fixture becomes a non-empty GitLab Code Quality JSON array and the clean fixture becomes `[]`.
- Added: a "Tool floors" section in the README with the PHP or Node floor of each locked tool, read verbatim from `composer.lock` and `package-lock.json` and checked by `tests/ToolFloorsTest.php`, so a dependency bump fails `composer ci` until the table is re-cut.
- Added: `phpstan/laravel.neon` pins Larastan's `noEnvCallsOutsideOfConfig` rule on, with `tests/fixtures/laravel/src/EnvLeak.php` and `tests/fixtures/laravel/src/ConfigRead.php` proving the Laravel preset reports an `env()` call outside `config/` and accepts a `config()` call there.
- Added: PHPUnit tests for the opt-in strict-types Pint presets, which run the real Pint against clean and missing fixtures for `pint/per-strict.json` and `pint/laravel-strict.json` and assert each strict config declares its preset and the `declare_strict_types` rule.
- Added: `tests/js/prettier.test.mjs`, which runs the Prettier preset through Prettier's Node API on clean and messy JS and Vue fixtures and on the preset's own options, so `npm test` enforces the preset like the ESLint ones.
- Added: PHPUnit tests for `pinstripe-baseline check --against=<git-ref>`, which build a throwaway git repository in a temp dir and assert the count at the ref and the exit codes.
- Added: `npm-test` CI jobs on GitLab and GitHub that run `npm ci` then `npm test` on Node 22, so the ESLint and Prettier presets are covered in CI.
- Changed: the GitHub workflow pins Preflight's reusable workflow by tag (0.1.2) instead of a SHA, as its comment intended.
- Added: agent-ready site (prompt blocks, Markdown twins, llms.txt), from Squire's kit.
- Pinned symfony/mime v7.4.22 in composer.lock, the fixed version for CVE-2026-45070 (PKSA-wtxr-p26d-nn42, GHSA-vqc8-7275-q272), so the audit step of `composer ci` passes.
- Changed: project names written as words except acronyms.
- Changed: the deploy layer's Squire kit is refreshed to 0.3.3 (release options can now live in ./.env.squire).
- Changed: the deploy layer's Squire kit is refreshed to 0.3.4 (the local .env.squire file is now git-ignored).
- Fixed: stale capability claims in the site and README.
- Added: `tests/PackageVersionTest.php`, which fails `composer ci` when the `version` in `package.json` does not match the newest `## X.Y.Z (date)` heading in `CHANGELOG.md` or, on a tag pipeline, the tag itself, so npm can always publish from the tag; `package.json` is now 0.1.1, the version the 0.1.1 tag shipped without.
- Changed: CI pulls its Docker Hub images through the GitLab Dependency Proxy (the group's CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX), so pipelines no longer hit Docker Hub's anonymous pull limit.
- Changed: `deploy/composer.json` drops `minimum-stability: dev` (every constraint resolves at stable), and the PROCTOR job for `deploy/` in `.gitlab-ci.yml` drops `allow_failure`, since PROCTOR now passes on `deploy/`.
- Changed: docs and package metadata name an internal GitLab as the canonical repository, with git.wayne.edu and GitHub as read-only mirrors, until git.wayne.edu has CI runners.

## 0.1.1 (2026-10-29) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-1-1-2026-10-29)

- Fixed the raw and Laravel PHPStan cuts inheriting `reportMaybesInMethodSignatures` and `reportStaticMethodSignatures` from `phpstan/phpstan-strict-rules`, which made them report phpdoc method signature issues they should not; `base.neon` now pins both to false and `strict.neon` keeps them on.
- Pinned the other eight parameters `phpstan/phpstan-strict-rules` forces on: four low-noise ones stay on in every cut, and `checkDynamicProperties`, `reportMaybesInPropertyPhpDocTypes`, `reportWrongPhpDocTypeInVarTag` and `reportNonIntStringArrayKey` are off in `base.neon` and on in `strict.neon`; the README lists each decision.

## 0.1.0 (2026-10-29) [#](https://pinstripe.apps.wayne.edu/docs/changelog.html#0-1-0-2026-10-29)

- Added `bin/pinstripe-baseline`, which counts a PHPStan baseline's ignored errors (`count`) and fails when the baseline grows (`check --max=<n>` or `check --against=<git-ref>`), so baselines only shrink.
- Added `phpstan/strict.neon`, an opt-in PHPStan preset for new apps that turns on `phpstan/phpstan-strict-rules`.
- Added `tests/fixtures/per`, a Pint fixture proving the `per` preset is the PER Coding Style.
