Skip to content
Menu

Changelog#

All notable changes to Sourdough are recorded here. The format follows Keep a Changelog; the project follows Semantic Versioning once 1.0 is out.

Unreleased#

Changed#

  • Fixed: the Squire copy docs name the ^0.11 dev dependency (they said ^0.10), and StackPinsTest's comments name PROCTOR 0.16, the line the templates pin. Content only.

  • Changed: the deploy kit is Squire 0.11.1 (was 0.10.7): the release script, parity scripts, HAProxy pin and fallback base follow the new templates, and waynestate/squire is ^0.11 (the exported copy in templates/squire/ moves with it).

  • deploy/ requires PROCTOR ^0.16 (was ^0.15, which does not allow 0.16), whose ci-pipelines check no longer asks for a GitHub workflow (D-069).

  • Every generated app requires SESAME ^0.8, Pinstripe ^0.4 and PROCTOR ^0.16 (was ^0.7, ^0.3 and ^0.15, which do not allow the current releases), and Sourdough's own dev dependency is Pinstripe ^0.4.

  • Docs: each generated README says how to turn on the nightly run (a GitLab pipeline schedule reruns the full PHP test matrix); a test keeps scheduled pipelines from being skipped.

  • CI pins Preflight 0.9.0 (components and the a11y checker copy).

  • Every shape and the GitHub workflow pin Preflight 0.9.0 (commit fb73b53), like Sourdough's own pipeline.

  • Added: sourdough check [dir] [--json], the baker's poke test: one read-only run that says whether an app is fed and supported. It prints the Support: line (the shape's status and owner and its Laravel major's or PHP floor's end-of-security date from CREED's policy), the manifest drift and whether a feed is due, then OK or a Needs attention: list. Exit 0 fed and supported, 1 behind the template, a deprecated shape or a line past security support, 2 the tool errors feed --dry-run stops on. The app's own edits are listed and never fail it. It writes nothing and needs no clean tree. BEST_PRACTICES 3.2 and backlog item 2 are done; tests/CheckCommandTest.php covers it.

  • Changed: Sourdough's own GitLab pipeline gains a blocking smoke-floor job that bakes the raw and Inertia shapes on PHP 8.3, the floor every shape pins in config.platform.php; the other smoke jobs bake on 8.5, so a template that quietly needed a newer PHP would have passed them. tests/SmokeFloorTest.php keeps the job's image on the templates' pin. No change to what a bake writes.

  • Docs: the front page and the README name Preflight 0.8.0, the release every pipeline pins (they still said 0.6.0), and tests/PreflightPinTest.php now fails when a sentence that names the pin on the front page, the README, MAINTAINING, BEST_PRACTICES or a docs page (not the changelog or upgrading notes) names another release.

  • CI pins Preflight 0.8.0.

  • Fixed: the front page's "Adopt an existing app" prompt asked the agent to run sourdough adopt with the values of --shape and --name missing: the <shape> and <name> placeholders sat in the HTML unescaped, so browsers read them as unknown elements and the copied prompt, index.md and llms-full.txt lost them. They are escaped now, as is a raw <name> in an old changelog entry, and tests/SitePlaceholdersTest.php fails on any element the page does not really use and on any flag left without its value.

  • Site: the order ticket has "Copy a link to this order", a link such as https://sourdough.apps.wayne.edu/#order?loaf=laravel-inertia&oven=docker&name=Parking%20Permits&advisor=no that opens the counter with the same loaf, oven, name and ADVISOR choice, so a lead can send a new developer the exact order. A loaf or oven that is not on the menu is ignored and the name goes through the usual rule, so a mangled link still lands on a good ticket. The button appears only once the script has opened the counter.

  • Docs: the every-OS guide says what to do when Windows will not run a script ("running scripts is disabled on this system"): on a Windows client with no execution policy set, PowerShell runs no script files at all, so it shows how to check the policy, set RemoteSigned for your own account, unblock a downloaded copy, or run one script with its own policy. It no longer says the generator's scripts are never affected. BEST_PRACTICES 5.3 says the same.

  • Docs: BEST_PRACTICES says what the code does today: 1.6 (each shape baked into a temp directory, the Laravel ones offline from the fixture skeleton) is Checked, 5.1 (.gitattributes pins in every shape, GitattributesPinsTest) is Enforced, 5.3 (Squire's parity.sh and parity.ps1 in every shape) is Checked, and each line of the gap list says whether it is done (and where) or what is still open.

  • Site: the front page has an order counter (#order), the command half of the "new app" page (BEST_PRACTICES 1.8). Pick a loaf, an oven and a name and its ticket writes the sourdough new command, the bake and the next steps to copy, read from site/assets/order-menu.json, which composer site:order-menu builds from the same plan code as sourdough new --dry-run --json. composer ci fails when the menu is stale, and tests/OrderMenuTest.php runs every order the ticket can write through the real command. It checks names with the generator's rule and offers only the ovens a shape takes.

  • Added: sourdough new --dry-run --json carries next_steps, the lines a real bake prints under "Next steps:" for that shape and oven (Sail, Docker or the bench, with or without ADVISOR). The plan now owns them (Plan::$nextSteps), so the printed list and the JSON can never disagree; the printed output is unchanged.

  • Docs: the maintaining guide, the troubleshooting page and the README name Preflight 0.6.0, the release CI and the templates pin (they still said 0.1.4 or 0.5.0).

  • Added: the Laravel shapes include Preflight's mysql56-migrate component, so every pipeline runs the migrations against MySQL 5.6.51 (D-078); every Preflight pin moves to 0.6.0.

  • Changed: new bakes require PROCTOR ^0.15 (was ^0.12) in the raw composer.json and both Laravel overlays, and the front page's deploy layer requires ^0.15 (locked 0.15.0). PROCTOR 0.13 checks the release cooldown against the CREED policy and 0.14 adds script-pair; 0.15 adds mysql56-ci; all of these only warn, nothing breaks.

  • Docs: the shapes guide's quick start says each sourdough new line runs the same in Windows PowerShell as in sh (one PHP command, no bash or WSL needed).

  • Docs: MAINTAINING no longer says "in 0.1" for the shapes; three BEST_PRACTICES backlog lines carry a status, and the one that named a sourdough check command says it is not built yet.

  • Changed: the GitHub workflow calls Preflight 0.5.0's reusable workflow (pinned to its release commit), the same release as the GitLab pipeline; it was on 0.1.4 because GitHub's copy of Preflight had no later tag.

  • Fixed: the manifest line-ending test normalises the kit's parity.ps1 before it starts, so it passes on a Windows checkout, where .gitattributes writes .ps1 files with CRLF.

  • Docs: the README and templates reference name the Squire 0.10.7 kit and PROCTOR ^0.12 (was 0.10.6 and ^0.11).

  • Changed: new bakes require PROCTOR ^0.12 (was ^0.11) in the raw composer.json and both Laravel overlays, and the front page's deploy layer requires ^0.12 (locked 0.12.0). PROCTOR 0.12 adds two warning-only checks (composer-cooldown, lock-tracked); nothing breaks.

  • Added: sourdough feed prints the Support: line (owner, status and the framework's end-of-security date from CREED's policy) on every run, so the app's sourdough-feed CI job keeps showing when its framework stops getting security fixes; --json carries it as support.

  • Site: the front page's stale facts are current (every shape answers /ready, not only the Laravel ones, and the "Also in the kitchen" shelf links Parity's site instead of its repository, without the "coming soon" tag).

  • Added: generated Laravel apps turn on HELMET's fixed 4xx page (helmet.error_pages, env HELMET_ERROR_PAGES, default true in the app's config/helmet.php), so an abort() message never reaches a visitor; the raw shapes already had HELMET's neutral error page.

  • Added: every app shape's composer.json sets Composer's release cooldown (config.policy.cooldown.period: "3 days"), CREED's 2026-11-03 decision; Composer 2.11 waits that long before it installs a newly published version.

  • Changed: every app shape's root .gitattributes pins *.ps1, *.bat and *.cmd to CRLF and *.sh to LF (CREED every-OS rule); the Laravel shapes append the pins to the skeleton's file.

  • 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. The templates' Squire copy (templates/squire/) is 0.10.7 too.

  • Added: raw and raw + Vue apps answer GET /ready through HELMET's readiness option, and in production an uncaught exception gets HELMET's neutral error page (the full detail goes to the log). Locally, PHP still shows the error.

  • Docs: the templates reference's rules table, the Squire kit version (0.10.6) in the README and the templates reference, and BEST_PRACTICES 2.1 and backlog item 6 say what the generator does today.

  • 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. The templates/squire/ copy and the lock move to 0.10.6 with them.

  • 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.

  • Version mentions: ADVISOR ^0.3 in the templates and generator, Squire kit 0.10.5 re-export, docs stamps current.

Fixed#

  • Fixed: a fresh app installs again right after a stack release; the Composer cooldown now exempts the stack's own packages (policy.cooldown.ignore: ["waynestate/*"]), which the templates require at their newest versions.

0.4.2 (2026-11-09)#

Added#

  • Added: every shape's README gains "Run it like Citadel" at the end of "Run it locally": the Parity commands that run the app on Citadel's PHP image, Apache, php.ini, proxy and MySQL 5.6.51, beside the everyday bench (composer serve or php artisan serve), which stays. Parity is a separate install, so Sourdough bakes no parity.json: parity init --from-squire writes it from the Squire kit every shape already ships, and that was proofed on a raw and a Blade bake (init, check, up and test). The raw shapes add --no-cron, because Parity would otherwise offer Laravel's scheduler to an app with no artisan, and say plainly that Citadel sets no APP_ENV, so a page boots as production and asks for CAS settings Parity 0.1.0 cannot set yet. The Laravel shapes add npm install for the Blade lock file and two parity shell --user citadel lines that migrate MySQL 5.6.51 and cache it, because the first deployment reads only .env. README is a seeded file, so apps you already baked keep theirs; copy the section from a fresh bake if you want it. New tests/ParityReadmeTest.php holds all five shapes to it.

Changed#

  • Docs: Parity joins the party. The README cast, the docs overview, Same kitchen, many ovens and the front page's "Also in the kitchen" shelf 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.51). It has no site yet, so it links to its repository on git.wayne.edu and hangs on the shelf with the dashed "coming soon" tag. Squire packs the loaf for the trip; Parity checks it rises the same in the home oven.
  • Docs: the pages that pick a local runner say when to use Parity. Building on Laravel gains "Run it like Citadel: Parity" with a which-to-use-when list (the bench, Sail or --docker while you write code; Parity before a release, after a PHP or Laravel upgrade, or for a bug that only shows on Citadel), and Every developer, every operating system, Quick start, Commands and the README's --docker line point at it. The --docker and --sail README sections drop "swap in Squire's Citadel-parity image when it exists" and "local parity with Citadel's database is not possible": Parity runs Citadel's MySQL 5.6.51 today. They also say that those ovens point .env at their own MySQL, so set DB_CONNECTION=sqlite for Parity runs, or the first deployment stops at the migrate step with Access denied (proofed on a Blade bake).

0.4.1 (2026-11-09)#

Added#

  • Added: the Laravel shapes (Blade, Blade + Vue islands, Inertia) carry the Pinstripe extras WELD carries. A composer lint:gitlab script writes Pint's findings as a GitLab Code Quality report (pint-codequality.json, [] when clean, ignored by git); the composer-ci job runs it in after_script, so it still reports when composer ci fails, and keeps it as a codequality artifact for seven days, which puts Pint's findings in the merge request widget. Each bake also gets tests/Unit/PinstripeWiringTest.php, the app's own test that Pinstripe is a dev dependency, that phpstan.neon includes its Laravel preset and leaves the level and the bans to it, and that pint.json is Pinstripe's laravel.json plus the three recorded skips for Squire's files (deploy, health.php, oracle-check.php). A fed app whose pint.json skips more paths fails that test until each extra skip is written into the test with its reason. The raw shapes are unchanged: they use Pinstripe's per preset and have no Laravel wiring to guard. New tests/PinstripeLaravelTest.php holds every Laravel overlay and pipeline to the same extras.

Changed#

  • Changed: the GitHub smoke matrix blocks: continue-on-error: true is gone, because every shape baked green there (as on GitLab, whose smoke jobs block since 0.4.0). A red shape now fails the GitHub workflow too.

Fixed#

  • Fixed: Sourdough's own tests pass on a tag build. Two ManifestTest tests expected the manifest's sourdough_version to be dev, but from a checkout sitting on a release tag Composer reports that tag, so Manifest::packageVersion() rightly says 0.4.0; the 0.4.0 tag pipelines failed on it on both GitLab and GitHub. Branch pipelines never saw it (Composer reports a dev- branch there), and neither did a local Docker run, where git refuses the copied files as another user's and Composer falls back to its no-version-set placeholder. The tests now accept dev or a release, and the new Manifest::versionFrom() (which packageVersion() now calls) is tested on its own: a release stays as it is, and nothing, a branch or the placeholder becomes dev. No change to what a bake writes.

0.4.0 (2026-11-09)#

Upgrading#

  • Upgrading: Pinstripe 0.3 may fail apps that build SQL by joining strings. Feed moves every shape to Pinstripe ^0.3, and PHPStan then fails a variable concatenated, interpolated or sprintf()'d into the SQL given to oci_parse(), PDO, mysqli or Laravel's DB::select() and friends. Bind the value instead, or type your own whole-SQL helper's parameter literal-string. The fix, with an example, is in the Upgrading page's 0.4.0 section.

Changed#

  • Changed: Sourdough's own GitLab smoke jobs (smoke-raw, smoke-raw-vue, smoke-blade, smoke-blade-vue, smoke-inertia) block the pipeline: allow_failure: true is gone from .smoke-base, because every shape baked green on CI. The scheduled proof job, which extends the same base, now fails a scheduled pipeline when it is red; started by hand it still only warns. The GitHub smoke matrix keeps continue-on-error: true for now.
  • Changed: every shape's .gitlab-ci.yml pins the Preflight CI components to the 0.5.0 release SHA (60314791565a264e97cb210813ef4f3e76512402 with # 0.5.0, was 0.4.0), and Sourdough's own pipeline names the 0.5.0 tag. Inputs and job names are unchanged. What 0.5.0 brings a baked app: every Composer default is 2.11.1 by digest, and on PROCTOR 0.11 (which the shapes require) the raw shapes' proctor job also keeps PROCTOR's JSON report as proctor.json, the file Rollcall reads. Sourdough's own composer-audit include drops its image input (a composer:2 digest), because 0.5.0's default is composer:2.11.1 by digest. The vendored a11y checker is unchanged at 0.5.0; tests/PreflightPinTest.php, tests/A11yCheckerPinTest.php and tests/RawGeneratorTest.php expect the new pin.
  • Changed: every shape requires Pinstripe ^0.3 in require-dev (was ^0.1; the raw shapes' composer.json and both Laravel overlays), and so does Sourdough itself (locked 0.3.0, was 0.1.4, with spaze/phpstan-disallowed-calls 4.15.0 new in the lock). This crosses two 0.x minors, and both break code that uses what they ban: 0.2.0 bans eval(), extract(), var_dump(), dd(), dump() and Http::withoutVerifying(), and 0.3.0 bans SQL joined from strings, TLS checks turned off, and Laravel's dd() and dump() methods. The raw shapes' src/Oracle.php now types query()'s $sql as literal-string (PHPDoc only, no behavior change), so the joined-SQL ban passes the helper and checks every caller instead; on the old string type a fresh raw bake failed PHPStan at its oci_parse() call, which tests/PinstripeRawTest.php now catches.
  • Changed: every shape requires ADVISOR ^0.2 in require-dev (was ^0.1; RawGenerator::ADVISOR_VERSION, the raw shapes' composer.json and both Laravel overlays), the same pin WELD carries. ADVISOR 0.2.0 is a dev-only MCP server, so no app code changes; --no-advisor still leaves it out.
  • Changed: the deploy kit is Squire 0.10.3 (was 0.10.2), in the checked copy (templates/squire/, which every bake takes) and in the front page deploy layer (deploy/); Sourdough's dev dependency is locked at 0.10.3. The kit's comments name what they used to cite by internal item ID, and nothing else changes. squire init --check on deploy/ and composer squire-copy:check pass.
  • Changed: the proctor job on Sourdough's own deploy layer (deploy/) blocks the pipeline: its allow_failure: true is gone, because proctor check on deploy/ passes on PROCTOR 0.11.1 (warnings only).

Docs#

  • Docs: the Docker commands in the README's and the Testing guide's "From the repo root" blocks pin the CI image, composer:2.11.1@sha256:8de2184c..., instead of the floating composer:2, like MAINTAINING and the composer ci line already did.
  • Docs: the README's which-command table no longer says rollcall report always exits 0: it exits 0, or 2 on a tool error (no scan yet, a bad option, an unreadable policy), the same words as WELD's table.

0.3.0 (2026-11-09)#

Added#

  • Added: the sourdough adopt command, so sourdough feed can look after an app Sourdough did not make: sourdough adopt [<dir>] --shape <shape> [--name <name>] [--sail | --docker] [--no-playbook] [--no-advisor] [--dry-run] [--json] [-v]. It writes .sourdough/manifest.json and nothing else, and prints each template path as yours, seeded or missing (match too with -v); a top-level folder whose every file is missing prints as one line, and --json lists every path. --shape is required (the refusal names the shape the app looks like), and the name defaults to the folder's. It refuses, with exit 1, an existing manifest, a leftover .sourdough/base/, a name the template cannot use, a folder outside git and a dirty tree; no git, a folder it cannot write and a failed bake are exit 2. A dry run writes nothing and turns the git and writable checks into notes. The wrong-name note now comes at two hinted files, not three, so a raw or laravel-blade app gets it too. Feed's "no manifest" message now says sourdough adopt <dir> --shape <shape>. New tests/AdoptCommandTest.php, tests/AdoptFeedTest.php and the fixture tests/fixtures/adopt/legacy-raw/.
  • Added: the adopt engine's edge cases, still with no command. A template path that is a symlink, or sits under a symlinked folder, is yours ("a symlink: Sourdough never writes through links") even when the link points nowhere, and so is a file whose realpath() leaves the app (a Windows junction). A file named in another case (readme.md for README.md on a case-insensitive disk) is yours, named as the disk has it. A file more than twice the template's size plus 1 KiB is yours without being read. A yours file that lacks the name the template writes into it says so, and two of those add a note that the --name may be wrong. The plan's notes also carry the deprecated-shape notice and a note when .squire.json records an older or newer Squire kit than the one Sourdough bakes. Adopt refuses a .sourdough/base/ left from a manifest that is gone. New tests/AdoptEdgeCasesTest.php.
  • Added: the engine behind the coming sourdough adopt (src/Adopt/), with no command yet. Given an existing app, a shape and a name, it bakes that shape into a scratch dir through the same Baker new and feed use, then looks at each template path in the app, and only those: no file is missing (left out of the manifest, so the next feed adds it), a file the template seeds is seeded, a file equal to the template's (line endings aside) is match and recorded as managed, and anything else is yours. Every recorded hash is the template's, the answers are the ones new would record plus adopted: true, and applying writes .sourdough/manifest.json and nothing else. It refuses an app that already has a manifest. Permutation::flags() now gives the flags a shape implies, for new --plan and adopt alike. New tests/AdoptTest.php: a lost manifest on every shape and oven adopts back to the bake's record, an edited app keeps its edits and its own files, a CRLF checkout matches, and feed then treats each status as the spec says.
  • Added: the manifest has a third file class, yours, for the coming sourdough adopt: a template file an adopted app keeps its own version of. sourdough feed never writes, merges, removes or reports a yours file and keeps no base copy of it, so the generated sourdough-feed job stays green; once the app's copy equals the template's, feed records it and manages it from then on. sourdough manifest --check skips yours files, as it skips seeded ones. Nothing writes the class yet, and schema stays 1. New tests/FeedYoursClassTest.php.
  • Added: deprecations fail the tests, in Sourdough's own suite and in every shape it bakes (BEST_PRACTICES 4.13, now Enforced for the suites). The phpunit config sets failOnDeprecation and failOnPhpunitDeprecation and skips indirect deprecations; the Laravel shapes get it on the skeleton's phpunit.xml at bake time, plus tests/Support/ReportsDeprecationsToPhpUnit.php, because Laravel's error handler drops deprecations while testing. Template code bakes clean on PHP 8.5, and the one PHPUnit deprecation in Sourdough's own tests (a doc-comment data provider) is now an attribute.
  • Added: the front-end shapes (raw + Vue, Blade + Vue, Inertia) ship a package-lock.json, seeded so npm owns it after the bake, and their frontend job installs it with npm ci --ignore-scripts, then fails on a high or critical npm audit finding (BEST_PRACTICES 4.10, now Enforced). New tests/TemplateNpmLockTest.php keeps each lock in step with its package.json, the smoke jobs install with npm ci, and apps already baked get the template's lock from sourdough feed only when they have none.
  • Added: the Laravel shapes (Blade, Blade with Vue, Inertia) ship tests/Feature/JobLimitsTest.php, which fails on any queued job under app/Jobs without Laravel's #[Tries] and #[Timeout] (the older $tries and $timeout properties count too) or with a timeout at or above the queue connection's retry_after; it passes while there are no jobs and is tested on fixture jobs that break each rule (WELD W18, W20). stubs/job.queued.stub and stubs/job.batched.queued.stub make php artisan make:job write #[Tries(3)] and #[Timeout(45)], and tests/LaravelJobLimitsTest.php holds every Laravel shape to both.
  • Added: tests/KitRoutesAbsentTest.php: no Laravel shape ships Fortify, Breeze or Jetstream, a routes/auth.php, or registration, password reset, email verification or two-factor routes (BEST_PRACTICES 2.2, backlog 5).
  • Added: the generated README carries a Support section with the support line sourdough new prints (status, owner and the end-of-security date from CREED's policy), on every shape (BEST_PRACTICES 2.4).
  • Added: WORKER_HEARTBEAT_MAX_AGE=0 turns the scheduler heartbeat check off, so an app that runs no scheduler still answers 200 on /ready.
  • Added: new bakes take the PHP floor from CREED's policy.json (BEST_PRACTICES 4.2, now Enforced). Sourdough requires waynestate/creed ^0.1 and reads its policy, or the file SOURDOUGH_POLICY names. As of the policy's refreshed_on, the floor is the oldest PHP line still supported 365 days later, bounded by the Laravel major's PHP range on the Laravel shapes. It is written into composer.json (require.php, config.platform.php), the .gitlab-ci.yml matrix and the README on all five shapes. A policy that cannot be read bakes on the pinned fallback (^8.3, tested on 8.3, 8.4 and 8.5) and says so. Today's output is unchanged. sourdough new prints a PHP: line, and --dry-run --json gains a php object. tests/PhpFloorTest.php changes the policy's floor and checks every shape.
  • Added: every shape has an owner role, a support status and a sunset path (BEST_PRACTICES 3.7, now Checked). The new "Support and sunset" guide (docs/guides/support.md) is the policy (the window lengths are a proposal), and resources/shapes.json holds the fields. sourdough new prints a Support: line with the framework's end of security from CREED, and --dry-run --json gains support. A deprecated shape prints a notice on every new and feed, and feeding a removed shape names its replacement. tests/ShapeSupportTest.php holds the catalog to the rules.
  • Added: every shape's pipeline carries three gates from Preflight 0.3.1 (BEST_PRACTICES 4.15, 6.4 and 6.5, now Enforced; 3 practices remain Not yet). Accessibility: an a11y-pages job boots the app with SESAME's fake driver and saves its pages (/, plus /dashboard signed in on the Laravel shapes), and the a11y component checks them at WCAG 2.2 AA, blocking. Bill of materials: the sbom component keeps sbom.cdx.json, and the front-end shapes' frontend job adds sbom-npm.cdx.json from CycloneDX's npm tool. Secrets: the secret-detection component runs Gitleaks, and a hidden .deploy template keeps any future deploy job off merge requests and on protected refs. Each generated README's new "Pipeline" section lists the GitLab settings a file cannot hold. New tests/TemplateCiGatesTest.php, plus testBakedPipelineCarriesTheCiGates in every generator test, holds all five shapes to it.
  • Added: the Laravel + Blade + Vue islands shape has its own .gitlab-ci.yml with a frontend job (it used to inherit the Blade pipeline, which never built its front end).
  • Added: the Laravel shapes (Blade, Blade with Vue, Inertia) ship Laravel Boost ^2.10 in require-dev, the stack's guidelines in .ai/guidelines/wayne-state.md (managed) and starter rules in .ai/rules/ (seeded), a .gitignore block for what boost:install writes (/.mcp.json, /boost.json, /AGENTS.md, /CLAUDE.md, /.claude/skills/, /.junie/; .agents/ stays tracked for Booster), a guarded composer boost-update appended to Laravel's post-update-cmd, a README section, and tests/Feature/BoostDevOnlyTest.php, which fails when Boost leaves require-dev or packages-dev. tests/BoostWiringTest.php holds the wiring; BEST_PRACTICES 2.3 is Enforced.
  • Added: every app with a front end ships an .npmrc with a one-day npm cooldown (min-release-age=1), a .nvmrc and engines.node >=22 in its package.json; the shapes without a front end get none of it (BEST_PRACTICES 4.9 and 4.11 are Checked by the generator tests).
  • Added: the Laravel shapes schedule a heartbeat each minute and register HELMET's readiness route at /ready with a scheduler check; while the cache stamp is missing or older than WORKER_HEARTBEAT_MAX_AGE seconds (default 180) /ready answers 503, so a stopped scheduler shows up instead of quietly dropping jobs. /up stays the liveness answer and never looks at the cache (WELD W23).
  • Added: the Laravel shapes can run the queue from the scheduler, for Citadel where nothing supervises a worker: with QUEUE_WORKER_MODE=scheduler (the new .env.example default) routes/console.php starts queue:work --stop-when-empty --max-time=50 --tries=3 every minute with withoutOverlapping(10); QUEUE_WORKER_MODE=none leaves the queue to a supervisor. QueueWorkerScheduleTest covers both (WELD W19).
  • Added: the two Laravel shapes ship tests/Feature/SchedulerNamingTest.php, which fails on any scheduled closure without ->name() (WELD W21).
  • 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.
  • Added: the Laravel shapes (Blade, Blade with Vue, Inertia) test that a POST without a CSRF token gets 419, and that a matching token or a same-origin request passes (CsrfTest, WELD W27).
  • Added: Laravel apps (Blade, Blade with Vue, Inertia) refuse to boot in production with APP_DEBUG on (ProductionDebug, beside the dummy-key guard).
  • Added: every shape's .gitlab-ci.yml runs a sourdough-feed job (BEST_PRACTICES 3.2, now Checked): on the shape's composer image, through ${IMAGE_PREFIX} and the Composer cache, it installs the newest Sourdough release and runs sourdough manifest --check and sourdough feed --dry-run. Drift in managed files is listed and never fails (feed merges it); a template release the app has not fed exits 1, which allow_failure: exit_codes: [1] shows as a warning, so it never blocks a deploy; exit 2 (no manifest, a newer manifest, leftover conflict markers, a failed bake) fails the job. Apps already baked get the job with their next sourdough feed. New tests/TemplateFeedJobTest.php holds every shape to the same job and runs its lines on fresh, edited, older and broken bakes of all five shapes and both ovens. BEST_PRACTICES 1.1, 1.2 and 1.3 are Enforced and name the tests that hold them.

Changed#

  • Changed: new bakes require HELMET ^1.3 (was ^1.0), SESAME ^0.7 (was ^0.6) and PROCTOR ^0.11 (was ^0.8) in the raw composer.json and both Laravel overlays, and the Laravel overlays CREED ^0.1.8 (was ^0.1). SESAME 0.7 and PROCTOR 0.11 are minor moves across a 0.x line: SESAME's NativeSession now warns once per request when the session cookie lacks HttpOnly, Secure or a Lax or Strict SameSite (the raw shapes call helmet_boot() before session_start(), and the kit's php.ini sets Lax, so a baked app stays quiet), and PROCTOR 0.9 to 0.11 add checks that mostly warn (case-clash and Boost or Debugbar in require fail). The front page's deploy layer moves to CREED ^0.1.8, HELMET ^1.3 and PROCTOR ^0.11 (locked 0.1.8, 1.3.0 and 0.11.1; were 0.1.7, 1.0.0 and 0.8.0), and Sourdough's own CREED requirement to ^0.1.8 (Pinstripe locked 0.1.4, was 0.1.0). BEST_PRACTICES 4.4, 4.6 and 5.2 name the new constraint, and 4.6 and 5.2 lose the gaps that waited for it.
  • Changed: every shape bakes Squire 0.10.2's kit (was 0.10.0), and the front page's deploy layer runs it too (squire update; squire init --check passes; the dev dependency stays ^0.10, locked 0.10.2). .squire/php.ini sets session.cookie_samesite = Lax (it was empty), so a raw app's session cookie gives SESAME 0.7 nothing to warn about; the kit's Dockerfiles name every image in full (docker.io/library/...) so Buildah and Podman build them, the fallback base copies Composer 2.11.1 from a COMPOSER_IMAGE stage, and the portable image drops node_modules/ after the frontend build. A fed app takes the three files on its next sourdough feed, like any kit move.
  • Changed: Composer 2.11.1 everywhere a pipeline, Dockerfile or documented command names it (was 2.10.3, which Squire calls unmaintained; 2.11.1 fixes GHSA-c968-33g3-wh7p and GHSA-fm2w-xgf2-f9fh), pinned by its multi-arch list digest (sha256:8de2184c..., arm64 included): every shape's composer-ci, sourdough-feed and a11y-pages jobs, the Docker oven's composer-bin stage, Sourdough's own composer-ci and wayneui-copies jobs, the smoke image and the smoke jobs' checksummed phar (cache key smoke-tools-composer-2.11.1-node-22.23.4). A fresh bake picks it up; an existing app takes it on its next sourdough feed.
  • Changed: the deploy kit is Squire 0.10.0 (was 0.9.0): no kit file changed, so the record moves to 0.10.0, and the dev dependency on waynestate/squire is now ^0.10 (locked 0.10.0). The README, the templates reference and the docs index name the 0.10.0 kit too.
  • Changed: the Laravel shapes' SESAME config defaults the CAS protocol to 2.0, as SESAME does, because WSU's CAS is believed to refuse the cookieless /p3/ validation CAS 3.0 uses; set SESAME_CAS_PROTOCOL=3.0 for a CAS server that answers it.
  • Changed: BEST_PRACTICES.md closes backlog 6, now that PROCTOR has all four checks it asked for: 4.6 is Checked on PROCTOR main (vite-secrets warns on secret-looking VITE_ names, not released yet), 4.4 names app-key and env-outside-config for a committed .env and env() outside config, and 5.2 names 0.9.0's case-clash. Baked apps get vite-secrets and case-clash once the shapes move past PROCTOR ^0.8.
  • Changed: every shape bakes Squire 0.9.0 (was 0.8.0; the dev dependency is ^0.9), and the front page's deploy layer moves from kit 0.7.1 to 0.9.0, gaining the portable image files. A Laravel release now stops before anything installs when APP_KEY is unset or APP_DEBUG is true in production and warns when APP_ENV is not production (BEST_PRACTICES 4.14, Checked for the release half; every Laravel shape's generator test pins it), and the release gate grades the PHP that runs it (SQUIRE_PHP_RUNTIME).
  • Changed: the Vue shapes' npm audit blocks on high or critical advisories in runtime dependencies only (--omit=dev); a second run lists dev-only findings without failing.
  • Changed: in the Laravel shapes (Blade, Blade with Vue, Inertia), /ready checks the database and the cache as well as the scheduler heartbeat (app/Health/DatabaseReady.php, app/Health/CacheReady.php), and answers 503 when one fails while /up stays liveness and never asks (WELD W11). The route moves from routes/web.php to bootstrap/app.php, outside the web group, as HELMET's readiness guide asks, so a probe no longer writes a session row or sets a cookie. tests/Feature/ReadyChecksTest.php breaks each dependency in turn, and tests/LaravelReadyChecksTest.php holds every Laravel shape to it.
  • Changed: the front-end templates floor Vite at ^6.4.1, the CVE-2025-62522 fix line, and ignore *.local, where Vite keeps local secrets (BEST_PRACTICES 4.12).
  • Changed: every app shape and Sourdough's own CI pin Preflight 0.4.0 (87d9b6f; the proctor job clones the full history, so the override-approver check can read git blame).
  • Changed: the Laravel shapes' config/helmet.php holds only the app's policy_path override, and HELMET's provider merges the rest from the package (BEST_PRACTICES 3.6). The old 403-line copy had fallen behind HELMET: it had no Playbook lookup for HELMET_PRESET, and no session.secure, metrics storage or warn settings. Feed replaces an unchanged copy, and an edited one gets a conflict to keep your own keys. 3.6 lists the template code still waiting for a library, starting with config/sesame.php, which skips Playbook's CAS URL and defaults CAS to protocol 3.0.
  • Changed: a Laravel bake drops the skeleton's CLAUDE.md and AGENTS.md when they hold only Laravel's Boost bootstrap block (boost:install writes them again); a file with other guidance is kept and stays in git. The overlay merge appends pre- and post- Composer hooks to the skeleton's instead of replacing them, and a new gitignore-additions.txt control file adds ignore lines once.
  • Changed: --no-advisor removes only ADVISOR's own .mcp.json line; the Laravel shapes keep /.mcp.json ignored for Boost.
  • Changed: BEST_PRACTICES.md marks 18 practices with their true status on main (exit codes, output, kit features off, Boost, the Laravel window, MySQL 5.6, env config, VITE_ secrets, Composer in CI, npm ci, Vite on localhost, the PHP matrix, APP_KEY, CRLF, Docker images, three OSes, templates as archives, boring startup); 9 remain Not yet.
  • Changed: every image in the baked CI files is pinned by digest: composer:2.10.3 now carries its multi-arch list digest, like the Node image already did.
  • Changed: the smoke jobs download Composer 2.10.3 and Node 22.23.4 once into a CI cache, check each sha256, and reuse them, instead of fetching both from the internet in every job.
  • Changed: the deploy layer and the templates/squire copy run Squire's kit 0.7.1 (was 0.7.0): .squire/php.ini no longer sets the deprecated session.sid_* lines.
  • Changed: the scheduled queue worker in the Laravel shapes sets --timeout=45, below the connection's retry_after (Laravel's default 90), and QueueWorkerScheduleTest checks the two (WELD W20).
  • Changed: every shape bakes Squire 0.8.0 (was 0.7.1): generated apps get the portable image (.squire/portable.Dockerfile and .squire/portable/), one image that runs as web, worker, scheduler or migrate for OpenShift, Coolify and raw Docker, and the READMEs say how to build it.
  • Changed: the local a11y scripts run Preflight's own checker (vendored from 0.3.1 and pinned by a test), so they check what CI checks: axe-core 4.14.0, 320 and 1280 px, and the reflow check.
  • Changed: every app shape and Sourdough's own CI pin Preflight 0.3.1 (b90323b; fixed cache keys, and caches saved even when a job fails).
  • Changed: every app shape's 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: new bakes require SESAME ^0.6 (was ^0.5); SESAME 0.6.0 has no breaking change for an app that keeps its driver.
  • Changed: new bakes start on the Squire 0.7.0 deploy kit: the release script restarts queue workers and the scheduler after optimize (report only; SQUIRE_ARTISAN_RESTART=0 turns it off), and the image drops shell functions from the web's PHP (SQUIRE_PHP_DISABLE_FUNCTIONS), turns on production opcache (SQUIRE_OPCACHE_VALIDATE) and reads secrets from /run/secrets. Sourdough's own deploy layer moves too.
  • Changed: every app shape's 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.
  • Changed: every shape requires PROCTOR ^0.8 (was ^0.7): the raw composer.json and both Laravel overlays. Breaking for apps you feed whose deploy scripts have Windows line endings, which PROCTOR 0.8's crlf-deploy-script fails; the upgrading page has the steps. The deploy layer requires PROCTOR ^0.8 (locked 0.8.0).

Fixed#

  • Fixed: the raw and raw + Vue pipelines' header comment says the components are pinned to the Preflight 0.4.0 release commit (it said 0.3.0; the pin was already 0.4.0), and the comment on Sourdough's own deploy-layer PROCTOR job no longer lists findings PROCTOR 0.11 does not report. Comments only.
  • Fixed: the manifest leaves out database/database.sqlite, so sourdough feed never treats an app's database as a template file and WELD's regen gate does not see it as drift.
  • Fixed: Laravel bakes (blade, blade-vue, inertia) create an empty database/database.sqlite when .env.example uses sqlite, as Laravel's own installer does, so the printed php artisan migrate runs without a prompt.
  • Fixed: the Laravel shapes' ProductionDebugTest passes the app's own Pint check and every case asserts something.
  • Fixed: the docs menu closes with Escape and hands focus back to its button (docs kit synced from Squire).
  • Fixed: scripts/a11y.ps1 works on a Windows checkout with CRLF line endings; it strips the carriage returns from the shell command it hands to Docker, which sh rejected with a syntax error.
  • 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: sourdough manifest --check forgives line endings, as sourdough feed does. The raw shapes' .gitattributes checks *.ps1 out with CRLF, so every clone of a fresh raw app reported scripts/parity.ps1 as changed. tests/ManifestCommandTest.php covers it.
  • Fixed: BEST_PRACTICES.md practice 3.4 counts the 0.2.0 tag among the releases that follow the release steps.

Docs#

  • Docs: the upgrading guide's 0.3.0 section says what a feed brings an app baked with 0.2.0 (the HELMET, SESAME, PROCTOR and CREED moves, Composer 2.11.1, the Squire 0.10.2 kit), the five breaking cases with a fix for each, what SESAME 0.7's cookie check means for a raw app, and the steps and checks, with sourdough adopt at the top for apps Sourdough did not make. The README gains a status line, and the install guide, docs index and front page ticket say 0.3.0.
  • Docs: MAINTAINING's "Who maintains it" names the stack maintainer as a role, not a person, and says to open an issue on git.wayne.edu to reach them; a CI comment, a test comment and BEST_PRACTICES 4.3 stop citing internal decision numbers.
  • Docs: sourdough adopt is documented. A new guide, Adopt an existing app (docs/guides/adopt.md, in the nav after The manifest), joins a sourdough adopt section in the commands reference, the yours class in the manifest guide, a troubleshooting entry for each refusal, and updates to the README, MAINTAINING, BEST_PRACTICES, keeping-current, CI, upgrading and docs index pages. On the front page, the feeding schedule gains an Adoption day row with a real adopt report and a Yours jar, a fourth agent prompt adopts an existing app, and the chalk rows now write themselves on even when a jump or a quick scroll skips past their edge.
  • Docs: the README, docs pages and front page catch up with main. Preflight 0.4.0 replaces 0.3.1 and 0.3.0 in the CI guide, MAINTAINING, troubleshooting (the 0.4.0 SHA), BEST_PRACTICES and the vendored a11y checker line; the templates reference names Squire 0.9.0's kit (^0.9) and SESAME ^0.6; the front-end pages show the runtime-only npm audit --omit=dev; the CI guide names the Laravel shapes' proctor-root job; "in 0.1" claims are gone, and --describe is said to stop at the plan. The README says Sourdough starts every shape and that the Laravel shapes keep oci8 ready. The front page no longer says the generated CI skips sourdough manifest --check, lists package-lock.json as seeded, adds CREED and ADVISOR to the recipe card and the CI gates to the proofing log, names the release that first baked each loaf, and its footer links the docs and git.wayne.edu. site/llms.txt and llms-full.txt are titled Sourdough again (they said # .): the README's title moves out of the centered HTML block the agent-ready kit drops.
  • Docs: the CI guide, MAINTAINING and BEST_PRACTICES name Preflight 0.3.1 (the release the templates pin), and the --no-input help no longer names Sourdough 0.1.

0.2.0 (2026-11-08)#

Added#

  • Added: tests/PreflightPinTest.php: one Preflight version across every shape's pipeline and Sourdough's own GitLab pipeline; no component image input with a registry prefix; every Docker Hub component in a shape takes the shape's IMAGE_PREFIX. BEST_PRACTICES 4.3 is Enforced by it. tests/TemplateCiCacheTest.php now checks the ${IMAGE_PREFIX}/ rule on the app's own jobs only.
  • Added: a third agent recipe on the front page, for the Laravel shapes (Blade, Blade with Vue islands and Inertia/Vue), and the stale "join the rack" line is gone.
  • Added: every bake saves its plan in the app as .sourdough/plan.yaml (ADR-0014, decision 3), after the bake succeeds: a --plan bake saves that plan with the name the app got, a bake from flags saves the shape, the name and all four parts. The file is not in the manifest, so it is neither managed nor seeded: sourdough feed and sourdough manifest --check never read, rewrite or flag it, and feed writes none for apps baked before. --plan now reads YAML plans (.yaml or .yml) as well as JSON, through the same schema, so the saved plan bakes the same loaf again. Sourdough requires symfony/yaml ^7.4. tests/SavedPlanTest.php and tests/FeedCommandTest.php cover it.

Changed#

  • Changed: every shape's .gitlab-ci.yml pins the Preflight CI components to the 0.3.0 release SHA (23038dfe767f6ef60e3b2efca1128f53d9acdff7 with # 0.3.0, was 0.1.4; Preflight 0.2.0 and later need GitLab 18.7 or later). From Preflight 0.3.0 each Docker Hub component adds the registry prefix itself (image_prefix, D-054), so the includes pass image_prefix: "${IMAGE_PREFIX}" and drop their image inputs, which only carried the prefix in front of the components' own defaults: the components and the app's own jobs follow one proxy rule. Apps already baked take it with sourdough feed; a Preflight include an owner added with a prefixed image keeps the plain name (docs/upgrading.md).
  • Changed: Sourdough's own GitLab pipeline pins the Preflight components to the 0.3.0 release tag (was 0.1.4), and their image inputs are plain names (the components add the proxy prefix); the jobs Sourdough defines itself keep ${CI_DEPENDENCY_PROXY_GROUP_IMAGE_PREFIX}/. The GitHub workflow stays on Preflight 0.1.4: GitHub's copy of Preflight has no tag after 0.1.4 yet (D-069).
  • Changed: the --docker setup publishes its ports on 127.0.0.1 only, so the dev server and Vite are not reachable from the network (SOURDOUGH-25).
  • 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).
  • Docs: the Docker commands in the README and docs mount the shared stack-composer-cache volume, so Composer downloads are cached between runs.
  • Changed: apps start on the Squire 0.6.0 deploy kit (was 0.4.0). The copy in templates/squire/ comes from Squire 0.6.0, and the dev dependency is ^0.6.
  • Changed: a baked app's scripts/release.sh asks PROCTOR's deploy gate (proctor gate) for a go or no-go instead of running proctor check, right after composer audit and before the frontend build and the migrations, so SQUIRE_PROCTOR=enforce stops a no-go before it touches the database. The verdict goes to storage/squire/proctor-gate.json (new setting SQUIRE_PROCTOR_RECORD_DIR, listed in .env.squire.example; the folder ignores itself) and becomes the baseline the next release is ratcheted against, so a failure that is already live is held and only a new one blocks. With a PROCTOR that has no gate the step warns and runs proctor check as before.
  • Changed: new apps in every shape require HELMET ^0.4 (was ^0.3), SESAME ^0.5 (was ^0.4) and PROCTOR ^0.7 (was ^0.6); CREED stays ^0.1 (0.1.7 today). PROCTOR 0.7 brings proctor gate, which the kit's release script now asks; HELMET 0.4's request metrics stay off until HELMET_METRICS_STORAGE is set. tests/StackPinsTest.php checks all three in every template composer file.
  • Changed: the Laravel shapes' config/sesame.php names SESAME 0.5's cas.require_pending_login (env SESAME_CAS_REQUIRE_PENDING_LOGIN, default on), with a note to leave it on; the Laravel adapter already hands the cas driver the session.
  • Changed: every shape's .gitlab-ci.yml caches its downloads. Docker Hub images in the app's own jobs are ${IMAGE_PREFIX}/<image>, digest pins kept, and the Preflight components get the same prefix as their image_prefix input; IMAGE_PREFIX defaults to docker.io, and a workflow: rule sets it to the group's GitLab Dependency Proxy when the GitLab has one. Composer and npm installs extend .composer-cache (keyed on composer.lock) and .npm-cache (keyed on package-lock.json and package.json). A project variable IMAGE_PREFIX=docker.io skips the proxy. New tests/TemplateCiCacheTest.php keeps every shape that way. Apps already baked take it with sourdough feed.

Fixed#

  • 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.
  • Fixed: BEST_PRACTICES.md's "Keeping generated apps current" tags match the code, each naming the file that holds it: 3.1 (record where the app came from) and 3.3 (merge, not overwrite) are Enforced by the manifest and sourdough feed, 3.2 (a check that fails CI) is Partly enforced (feed --dry-run and manifest --check exist; no template runs them in CI yet), 3.4 (tags and migration notes) is Documented in the release steps, and 3.5 (compatibility CI) is Checked by the smoke gate, which still only warns. They all said Not yet or Documented. 4.3 keeps Partly enforced and now names its templates and test.
  • Fixed: BEST_PRACTICES.md describes Sourdough as it is (0.1.7, all five shapes bake, manifest and feed ship) instead of a tool with no code on main, and practice 6.1 (wire the stack in by default) is Enforced by the generator tests in every shape; it said only the raw shape generated.
  • Fixed: the local parity fallback image builds when the host's uid or gid already belongs to an account in the image (a host gid of 1001, like GitHub's runners, collided with the container user's default).
  • Fixed: scripts/parity.ps1 builds the fallback image with the host's uid and gid (1000 on Windows, the current user's ids on Linux and macOS) instead of a fixed 1000, so the app container starts when the bind-mounted source belongs to another user.
  • Fixed: the raw shapes (--raw, --raw --vue) sign in with CAS in production. public/index.php called DriverFactory::make($config) with no HTTP client, so with APP_ENV=production the cas driver refused to boot; it now passes a Guzzle client (10 second timeout, no redirects, TLS verification on), a nyholm/psr7 request factory and the app's NativeSession, which SESAME 0.5's cas driver needs for its pending-login marker (a ticket is accepted only for a sign-in this browser started). The raw template requires guzzlehttp/guzzle ^7.9 || ^8.0 and nyholm/psr7 ^1.8.

0.1.7 (2026-11-07)#

Added#

  • Added: sourdough feed brings template updates into an app made with sourdough new, without clobbering what the app changed (ADR-0014, decision 4). It bakes the app's shape again with the answers in its manifest and goes file by file: files the template did not change are left alone, untouched managed files take the new version, files both sides changed are three-way merged by git merge-file, same-line changes get git's conflict markers (<<<<<<< app ... >>>>>>> sourdough <version>) and never a silent overwrite, new template files are added, dropped ones are removed only when untouched, binary files are never merged (the template's copy lands as <file>.sourdough-new), and seeded files are never touched. The base for a merge is found by its manifest hash, in .sourdough/base/ (the template's version of each changed managed file, kept by the previous feed) or anywhere in the app's git history; with no base, both versions are marked. Feed then moves the manifest to the new base. It runs only on a clean git tree, refuses while the last feed's markers are unresolved, and refuses a manifest from a newer Sourdough. --dry-run prints the plan and writes nothing (exit 0 fresh, 1 feeding would change files, so it works as a CI gate), --json prints the plan for machines; a real feed exits 0 fed cleanly, 1 fed with conflicts, 2 tool error. It needs git and nothing else. Every shape is covered by tests/FeedCommandTest.php, and the smoke gate now checks that a fresh bake of each shape has nothing to feed.
  • Added: the proof harness, scripts/proof.sh (Linux, macOS) and scripts/proof.ps1 (Windows), and the Proof page (docs/reference/proof.md) with its dated Last run table. In Docker, one after another, it runs the smoke gate on all five shapes and on every Laravel shape with --sail and with --docker (eleven runs), and feeds a bake of the last release (read from this changelog) forward in each. It writes proof-out/last-run.md, a summary and every step log, and exits 1 when any run fails. A GitLab proof job runs it by hand or on a schedule that sets SOURDOUGH_PROOF to 1, never on a push, and keeps the results as an artifact. tests/ProofHarnessTest.php keeps the two scripts, the gate, the CI job and the table listing the same runs.
  • Added: the smoke gate checks more of every loaf. Right after the bake, sourdough manifest --check must be clean. Every shape runs its own suite as its own step (the count goes in the proof table) and composer proctor. The Laravel shapes now boot too, on Laravel's own router: / must answer with the shape's home page (the Blade page, the built Vue islands, or the Inertia Home page), /dashboard after SESAME's fake sign-in, /nope 404 and /up 200; the raw shape's / must carry its home page in WayneUI's shell. A second argument, --sail or --docker, proves a Laravel shape's oven (the scaffold's files, install, suite, PROCTOR), and SMOKE_FEED_FROM=<version> bakes that release from Packagist and feeds it forward. scripts/smoke-shape.ps1 takes -Oven and -FeedFrom to match.
  • Added: the Laravel shapes ship skeleton feature tests (tests/Feature/SkeletonTest.php, Pest, next to the starter's example tests): /up answers 200, the home page answers 200 for a guest (the Blade page, the built Vue island, or the Inertia Home component), a guest at /dashboard goes to the sign-in flow, the dashboard renders for a signed-in user after SESAME's fake sign-in (with the islands view's data-vue-island="counter" island and the Inertia Dashboard component checked too), a missing page answers 404, and UserResolver::refreshUser() turns a stored user array back into the User by username, or null when the username no longer exists. Each baked Laravel suite grows from two tests to nine, and the proof table quotes the new counts.

Changed#

  • Changed: the front page's deploy layer (deploy/) runs Squire's kit 0.5.0 (was 0.4.0): .squire/base-fallback.Dockerfile and scripts/parity.ps1 take the new templates, 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 (ADR-0021); docs, links and package metadata no longer point at the archived nougat copy.
  • Changed: the Inertia shape bakes on Inertia 3: inertiajs/inertia-laravel ^3.0 and @inertiajs/vue3 ^3.0 (PHP 8.2+, Laravel 11+, ESM only, no bundled Axios). The root view marks its title data-inertia instead of the bare inertia attribute, and Inertia now hands the first page to Vue in a <script type="application/json"> element instead of the root div's data-page attribute (HELMET's CSP is untouched: a JSON data block never runs). The template never used Axios, Inertia::lazy(), router.cancel() or the future options, so the rest of it bakes as before (one fix rides along: the progress bar's nonce, below). Apps already baked: the Upgrading page's Unreleased section has the steps (sourdough feed, then composer update and npm install).
  • Changed: new apps in every shape require PROCTOR ^0.6 (was ^0.4). The Laravel shapes' composer proctor script is now plain proctor check: PROCTOR 0.6 refuses --policy in CI unless the job sets PROCTOR_ALLOW_OVERRIDES=1, and without the option it still reads CREED's released policy from vendor/waynestate/creed on its own. PROCTOR 0.6 also fails composer-audit when the app has no composer.lock or Composer is not on PATH; every baked pipeline installs first, so a baked app passes as before.
  • Changed: the smoke gate reads the Inertia Home and Dashboard pages from Inertia 3's JSON page element, and tests/StackPinsTest.php keeps the PROCTOR and Inertia lines, the plain proctor check script and the data-inertia title from slipping back.

Fixed#

  • Fixed: the Inertia shape's progress bar wears its styles again. Inertia injects them in an inline <style>, and HELMET's CSP admits one only with the request's nonce, so the browser refused it on every page ("Refused to apply inline style") and the bar ran unstyled. resources/js/app.ts now reads the nonce from the pre-paint script's nonce property and hands it to Inertia 3's new nonce option, which stamps it on everything Inertia injects; no CSP is loosened.

  • Fixed: the Laravel templates' UserResolver lists its interfaces in Pint's order (RefreshesUser before UserResolverContract), so a freshly baked app passes its own pint --test on the first run instead of failing composer ci.

  • Fixed: Baked apps pin config.platform.php to their PHP floor, so PROCTOR no longer flags the lock.

  • Fixed: Baked Laravel apps read the signed-in user again on every request, so Laravel 13's JSON sessions no longer sign everyone out after the first page.

  • Fixed: sourdough feed brings an app baked by 0.1.6 with --sail or --docker forward with its oven. 0.1.6 wrote the manifest before the oven's scaffold ran, so the answers named no oven, the oven's files were not in it, and composer.json was hashed before the scaffold edited it: feed baked the plain shape, found it "Fresh", and left sourdough manifest --check reporting composer.json changed for good. Feed now reads the oven from the app's files when a 0.1.6 manifest names none (a Dockerfile, compose.yaml and the dev-up script for Docker; laravel/sail and Sail's compose.yaml for Sail) and says so in a note: line. The proof harness found it.

  • Fixed: sourdough feed records a managed file that already holds the template's new version (a new record action) instead of passing over it in silence. Nothing in the file is written, but the manifest moves to the new hash, so sourdough manifest --check stops calling it changed. A plan of only record lines is a change: --dry-run exits 1, and the real feed writes the manifest.

  • Fixed: a 0.1.6 oven bake feeds forward without a composer.json conflict: the manifest hashed the file before the scaffold edited it, so feed undoes the scaffold's edit to recover the pre-scaffold composer data, verifies it against the recorded hash, reapplies the scaffold and uses the result as the merge base; an app that never touched the file takes the template's composer.json as an update, and a real app edit still merges or conflicts as before.

  • Fixed: the manifest of an app baked with --sail or --docker lists the scaffold's files (Dockerfile, compose.yaml, .dockerignore, the docker/ ini files) and the composer.json the scaffold edited, and records sail or docker in its answers again, so sourdough manifest --check is clean right after the bake. It was written before the scaffold ran, so the check reported composer.json as changed on a fresh app. new and feed now bake through one Baker.

  • Fixed: the front page's feeding schedule shows its rows again for visitors who allow motion. Each row is clipped until it wipes in, and Chromium counts a clipped row as 0 % visible, so the reveal's 20 % threshold never fired and the rows stayed blank. The reveal now trips on the row's first edge, 15 % above the bottom of the screen.

  • Fixed: the docs pages reflow at 320 px (WCAG 1.4.10). The version ticket in the shared header carried flex-shrink: 0, so the header row could not give up ground and every docs page measured 328 px wide in a 320 px viewport. The ticket now shrinks and wraps to its version number instead of holding its width. The front page's five crumb buttons are named by their visible words too: each aria-label starts with "Score it", the words the hint shows, so the accessible name contains the visible text (axe label-content-name-mismatch).

0.1.6 (2026-11-06)#

Added#

  • Added: the site accessibility gate: scripts/a11y.sh (Git Bash, Linux, macOS) and scripts/a11y.ps1 (Windows) run axe-core (WCAG 2.2 AA) in Docker over every committed HTML page under site/, in light and dark at 360 px and 1280 px.
  • Added: sourdough new --raw --vue bakes a raw PHP + Vue SPA over JSON app, the fifth and last shape. The raw template comes first (HELMET, the session and SESAME boot the same way, Squire's deploy files, Pinstripe, PROCTOR, Playbook and ADVISOR wiring), then templates/raw-vue/ over it: a front controller that answers JSON under /api/ (/api/me returns the signed-in user, or 401 instead of sending a fetch() to CAS) and sends the Vue page for / (and for any other path, with a 404); Vue 3 and Vite with WayneUI's Vue components and its layered dist stylesheet from @waynestate/wayne-ui-vue and @waynestate/wayne-ui-css 2.0.8, pinned exactly as in the Inertia shape; and src/Vite.php, a small tested reader for Vite's manifest that prints the tags with HELMET's CSP nonce, or points at the dev server while npm run dev runs (and adds it to the CSP, never in production). Its Next steps: composer install, npm install, npm run build, composer serve. The --raw --vue plan no longer ends in "not available in this release", and a smoke-raw-vue CI job bakes the shape and checks /, /api/me and /up on a live server. All five loaves bake now.
  • Added: the Laravel shapes refuse to boot production on the tests' dummy APP_KEY (app/Support/DummyAppKey.php, called from AppServiceProvider::boot()), and tests/Support/SkipEnvFile.php hands the tests that one dummy key (base64 of 32 zero bytes) when nothing else sets one. WELD ships the same files.
  • Added: the docs site in site/docs/ is built by the shared Squire docs-site builder (bin/docs-site.php) from the pages in docs/, and composer ci checks it with @docs:check.
  • Added: the smoke gate proves a live baked raw app serves: it fetches the pinned WayneUI release once into public/wayne-ui.php, starts the app with APP_ENV=local on 127.0.0.1:8099 and expects / 200, /nope 404 and /up 200. Every shape now bakes with --no-playbook, because Playbook is required by default and its private package cannot be installed credential-free.
  • Added: --docker generates the app's own Docker setup for the Laravel shapes (--laravel, --laravel --vue and --inertia): a two-target Dockerfile (dev and prod) whose base images are pinned by manifest-list digest, so one pin resolves natively on amd64 and arm64, a compose.yaml with a MySQL 8.4 service (and a vite service for the Vue and Inertia shapes), a .dockerignore, the PHP ini files the image copies in, the composer dev-up, dev-down and dev-shell scripts, the database settings in .env.example, and a "Run it locally with Docker" README section. It works natively on Windows, macOS and Linux (no WSL2 needed). Playbook credentials reach a production build only as a BuildKit secret, never a build arg, and the FROM lines are the single place to swap in SQUIRE's Citadel-parity image when it exists.
  • Added: --sail generates a Sail setup (compose.yaml, laravel/sail) for the Laravel shapes.
  • Added: the raw template's .gitlab-ci.yml runs an explicit composer-ci job (composer install, then composer ci), mirroring the Laravel overlay, so PROCTOR sees a composer ci in the pipeline instead of warning that no job runs it.
  • Added: generated apps in Require mode get a composer playbook script (@composer show waynestate/playbook --no-interaction) with its scripts-descriptions entry, so you can check any time whether Playbook (WSU shared values) is installed. Existing scripts keep their order and playbook is appended last; an existing playbook script is left alone.
  • Added: the raw template ships Pinstripe's coding standard: pint.json (the per preset, with the fetched public/wayne-ui.php kept out and vendor excluded) and phpstan.neon (Pinstripe's raw preset, level 8 over src/ and public/), waynestate/pinstripe in require-dev with the extension-installer plugin allowed, and lint, fix and analyse scripts, so composer ci runs test, lint, analyse, proctor and audit in that order.
  • Added: the front page's main nav links the docs site.

Changed#

  • Changed: the Inertia shape draws with WayneUI instead of the Tailwind starter kit, the same wiring WELD ships. @waynestate/wayne-ui-css and @waynestate/wayne-ui-vue 2.0.8 are pinned exactly; every page wears WayneUI's app bar (shield, theme toggle), the sidebar that becomes a focus-trapping drawer on phones, breadcrumbs, cards and footer; a pre-paint script under HELMET's nonce stops the dark-mode flash; Ziggy's client comes from the ziggy-js npm package. The home page and the dashboard are new, in WayneUI's components and tokens. eslint.config.js refuses components/ui imports and the kit's helper packages, .prettierrc is the stack's, and a frontend CI job runs lint, Prettier, vue-tsc and the build.
  • Changed: the Laravel shapes (Blade, Blade + Vue, Inertia) generate apps on Pest 4 (tests/Pest.php, a Pest example test, composer test and composer ci run Pest, PHPUnit tests unchanged, tests read .env, or .env.example when there is no .env); the raw shape is unchanged.
  • Changed: the docs site wears Sourdough's own look: the front page header and menu (Docs marked current), the gold version ticket, Caprasimo titles, the baker's Kalam hand for labels, the recipe terminal with its gold Copy pill for commands, recipe-card tables, baker's-note callouts and the deep green footer, with a derived chalkboard dark mode. Source: docs/_header.html, docs/theme/sourdough.css and a theme key in docs/docs.json; the kit's docs.css is unchanged.
  • Changed: sourdough new now requires waynestate/playbook in every app it bakes: the VCS repository, the package in require, config.gitlab-domains so Composer sends the token to git.wayne.edu, the .env.example block, and a README section with the access how-to. The command checks read access before writing anything (a Composer credential, then a direct git probe) and refuses with exit 1 until the developer can read the package; an unreachable git.wayne.edu generates with a warning, and non-interactive and CI runs skip the check. --playbook stays as a no-op for old scripts, and --no-playbook is for CI and automated tests only.
  • Changed: the raw template's code passes both of Pinstripe's tools: per-preset style fixes in Oracle, OracleException, public/index.php and OracleTest, precise closure and binds types in Oracle, a false guard for oci_error() results, and the connect-failure branch reporting the last driver error instead of passing the failed connection as its source. A freshly baked raw app passes its own checks.
  • 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 at its tag commit); the deploy layer sets minimum-stability to stable.
  • Changed: new apps now get HELMET ^0.3, SESAME ^0.4 and PROCTOR ^0.4, and their .gitlab-ci.yml pins the Preflight CI components to the 0.1.4 release SHA (79029cc2300702d0d450c42cc699e12af1b731f8, with the tag in a trailing comment) because PROCTOR 0.4's preflight-pinned check wants a 40-hex SHA.
  • Changed: the smoke gate runs php artisan migrate like the Next steps, and the Laravel template READMEs show migrate for local and migrate --force for deploys.

Removed#

  • Removed: from the Inertia shape, tailwind.config.js, cn() (resources/js/lib/utils.ts), tailwindcss, autoprefixer, tailwind-merge, clsx, lucide-vue-next, @vueuse/core, prettier-plugin-tailwindcss, the Bunny Fonts link and the ten kit components they served.

Fixed#

  • Fixed: --sail apps answer 200 on / and /up when the checkout is one Sail's sail user cannot write (a Windows drive under Docker Desktop, or files a root container wrote). Every page was a 500 naming tempnam(), because Blade could not write storage/framework/views. The compose file's entrypoint now gives the sail user its WWWUSER uid first (so a sail artisan run the moment sail up -d returns no longer runs as the image's uid 1337 and leaves a log file the server cannot append to), opens the app's files to that user only when it cannot write them (vendor/, node_modules/ and .git untouched), then starts Sail as usual.
  • Fixed: --docker apps with a vite service (Blade + Vue, Inertia) serve / on the first composer dev-up. Nothing installed node_modules, so the vite service exited with vite: not found and / was a 500 (Vite manifest not found). The service now runs npm install when Vite is missing, then npm run dev.
  • Fixed: the Laravel shapes' (Blade, Blade + Vue, Inertia) .gitlab-ci.yml runs the php-test matrix with vendor/bin/pest. The Preflight component defaults to vendor/bin/phpunit, which refuses the Pest example tests ("Please run ./vendor/bin/pest instead"), so every job in the matrix crashed with exit 255. Pest runs the PHPUnit class tests too.
  • Fixed: --docker apps with a vite service (Blade + Vue, Inertia) load their pages. The service ran npm run dev -- --host 0.0.0.0, so laravel-vite-plugin wrote http://0.0.0.0:5173 to public/hot and the browser got a blank page; it now runs npm run dev with LARAVEL_SAIL=1, which listens on every address and writes http://localhost:5173.
  • Fixed: the GitLab smoke jobs (raw, Blade, Blade + Vue, Inertia) failed before they started: the Composer installer's options were handed to php itself (no argument for option -). They now go after --, with Composer pinned to 2.10.3, and the image gets unzip so Composer can unpack the locked packages.
  • Fixed: a freshly baked Laravel app passes its own pint --test again: the Pest example tests are written out over several lines and tests/Support/SkipEnvFile.php uses imports and Laravel's operator order, so composer ci no longer fails on the template's own style.
  • Fixed: raw apps start with composer serve. The old php -S localhost:8000 -t public line booted the app as production, because the raw front controller defaults APP_ENV to production when it is unset. The raw template's new serve script disables Composer's process timeout, sets APP_ENV=local cross-platform with @putenv, then starts php -S localhost:8000 -t public, so SESAME signs in with its fake driver; the raw Next steps, the raw README and the site recipe all point at composer serve now.
  • Fixed: the raw front controller answers 404 for any path but / (a short not-found page that keeps WayneUI's layout and links home) instead of rendering the home page for every URL. /up stays HELMET's and answers first.
  • Fixed: the GitHub CI workflow was rejected as invalid (every run failed with "workflow file issue") because the smoke job used GitLab's allow_failure; it now uses continue-on-error.
  • Fixed: the sourdough command now works after composer global require (bin/sourdough also looks for the autoloader three folders up, where a dependency install keeps it).
  • Fixed: the Laravel Next steps now run php artisan migrate after php artisan key:generate (all three Laravel shapes), so a freshly baked app has its database before the first request instead of answering 500 until someone migrates by hand.
  • Fixed: the Blade and Blade + Vue islands views read the signed-in user as an array ($user['name']), because SESAME's Sesame::user() returns an array, not an object; the dashboard and the layout no longer crash after sign-in.
  • Fixed: the laravel-blade template ships app/Providers/AppServiceProvider.php with Schema::defaultStringLength(191) like the laravel-inertia one, so string columns stay inside Citadel's MySQL 5.6 index limit (PROCTOR mysql56-string-default).
  • Fixed: the Oracle check command in the laravel-blade and laravel-inertia templates compares in Pint's non-Yoda order ($script === null), so a freshly baked app passes its own composer ci on the first run.
  • Fixed: the laravel-blade-vue template ships tests/Feature/ExampleTest.php with $this->withoutVite(), so composer ci in a freshly baked islands app no longer fails on the missing Vite manifest before npm run build has run.
  • Fixed: the Playbook wiring no longer drops a template's own composer config keys.
  • Fixed: the raw template ships stubs/wayne-ui.php, a static-analysis stub for the run-time WayneUI functions (wsu_shell_start, wsu_shell_end) that phpstan.neon scans through scanFiles, so composer ci in a freshly baked raw app no longer fails with function-not-found errors for functions that arrive only with the fetched public/wayne-ui.php.

Security#

  • Security: the front-page deploy layer moves to Symfony 7.4.23 (symfony/http-foundation and symfony/yaml advisories, including CVE-2026-118514).

0.1.5 (2026-11-03)#

Added#

  • Added: sourdough new --laravel bakes a Laravel + Blade app: a fresh Laravel skeleton from Composer, the laravel-blade overlay, the stack packages, Squire's laravel deploy files and the manifest. Its Next steps suit the shape: composer install, cp .env.example .env, php artisan key:generate, php artisan serve. One more loaf on the bench.
  • Added: sourdough new --inertia bakes a Laravel + Inertia/Vue app: the same Laravel skeleton, the laravel-inertia overlay (Inertia pages rendered by Vue, Ziggy routes, the stack packages), Squire's laravel deploy files and the manifest. Its Next steps suit the shape: composer install, cp .env.example .env, php artisan key:generate, npm install, npm run build, php artisan serve. Three of the five loaves bake now.
  • Added: sourdough new --laravel --vue bakes a Laravel + Blade + Vue islands app: the Laravel + Blade bake under a front-end layer (Vite with the Vue plugin, a resources/js/app.js registry that mounts a Vue 3 app on every [data-vue-island] element, and a Counter island live on the dashboard view). Its Next steps suit the shape: composer install, cp .env.example .env, php artisan key:generate, npm install, npm run build, php artisan serve. Four of the five loaves bake now.
  • Added: the raw template ships scripts (test, proctor, ci) and scripts-descriptions, so a generated raw app can run its own gate locally with composer ci.
  • Added: generated apps ship ADVISOR by default. waynestate/advisor lands in require-dev (raw template and the laravel-blade overlay), .mcp.json is git-ignored, the README gains an "ADVISOR" section, and the Next steps print php vendor/bin/advisor install --client=claude --write. --no-advisor skips all of it and records the choice in the manifest.
  • Added: the smoke gate (scripts/smoke-shape.sh, scripts/smoke-shape.ps1, scripts/smoke.Dockerfile) bakes a shape with this checkout's own CLI and runs the generated app's own checks; CI runs one job per shape, all allow_failure: true until seen green once.

Changed#

  • Changed: --name on the Laravel bakes reaches every place WELD applies it by hand: composer.json's name becomes app/<slug> (an application is not a published package) with the description reading "<name>, a Wayne State app baked from Sourdough.", .env.example's APP_NAME carries the app name (quoted when it holds a space), and the config/app.php default follows it.
  • Changed: the raw template pins WayneUI 2.0.8 (https://wayneui.apps.wayne.edu/v2/releases/2.0.8/wayne-ui.php) instead of fetching the floating main branch copy.
  • Changed: the raw template's .gitlab-ci.yml pins the Preflight components to released Preflight tags; the "not cut yet" note is gone.
  • Changed: the Squire copy comes from Squire 0.4.0 (adds oracle-check.php to every target; the dev dependency is now ^0.4).
  • 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).
  • Changed: the deploy layer's Squire kit is refreshed to 0.4.0 (deploy/oracle-check.php arrives; release.sh runs it without failing the release).
  • 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: the laravel-inertia template ships AppServiceProvider (string length 191 for Citadel's MySQL 5.6) and a tests/TestCase.php that writes a stub Vite manifest, so view tests boot without a build. WELD had both; now every Inertia app does.
  • Changed: the laravel-inertia template's .gitlab-ci.yml gains the ziggy job WELD carries by hand: it regenerates resources/js/ziggy.* and fails on any diff, so the route list that ships inside the Vite bundle always matches the routes.
  • Changed: docs and package metadata name nougat as the canonical repository, with git.wayne.edu and GitHub as read-only mirrors, until git.wayne.edu has CI runners.
  • Changed: the front page tells the truth about the shapes. The Laravel + Blade, Laravel + Blade + Vue islands and Laravel + Inertia/Vue loaves come out of the oven with their real commands; the hero, the rack note and the two agent prompts name the four that bake in 0.1; and WELD reads as the Inertia/Vue shape already built from Sourdough, not the other starter. Only raw PHP with Vue stays proofing.

Fixed#

  • Fixed: the laravel-inertia bake drops the skeleton leftovers before the manifest is written: vite.config.js (next to the overlay's vite.config.ts it breaks npm run build), the dead resources/js/app.js stub, and resources/views/welcome.blade.php (no route renders it); the manifest no longer lists a file that is gone.
  • Fixed: php artisan oracle:check finds the kit where it lives, in both the laravel-blade and the laravel-inertia templates: oracle-check.php at the app root (Squire's Laravel layout) first, then deploy/oracle-check.php (WELD's home).
  • Fixed: composer install in a freshly baked Laravel + Blade app no longer stops at the plugin gate; the overlay allows phpstan/extension-installer next to the pinned ext-oci8.
  • Fixed: the laravel-inertia overlay now passes a real run of a generated app. The overlay allows phpstan/extension-installer in composer config so composer install succeeds, the appended SESAME and HELMET env keys ship commented out (except SESAME_DRIVER=fake) so package defaults hold instead of being overridden by empty values, the generator removes the skeleton's vite.config.js so it no longer sits next to the overlay's vite.config.ts and breaks npm run build, and the Oracle command, Oracle error helper and bootstrap are Pint-clean like their Blade twins.
  • Fixed: a fresh Laravel + Blade app boots with nothing in its environment. config/sesame.php defaults SESAME_FAKE_USERNAME to jane.doe (SESAME wants a non-empty fake username), and the appended SESAME and HELMET env keys ship commented out so their defaults hold instead of being overridden by empty values.
  • Fixed: the plan printed after sourdough new --laravel no longer carries the "(not available in this release)" suffix; only the permutations that really refuse keep it.
  • Fixed: the generated Laravel + Blade app passes its own composer ci. The template's Oracle command, Oracle error helper and bootstrap are Pint-clean, and Pint skips the two Squire-owned root scripts (health.php, oracle-check.php) through notPath.
  • Fixed: the agent-ready site twins (site/index.md, site/llms-full.txt) are resynced with the README, so the site:agent-ready-check step of composer ci passes.
  • Fixed: the laravel-inertia template boots a fresh app out of the box: config/sesame.php defaults SESAME_FAKE_USERNAME to jane.doe so the fake driver has a non-empty username, and Pint skips the two verbatim Squire files (health.php, oracle-check.php) through notPath.

0.1.4 (2026-10-29)#

Added#

  • Added: agent-ready site (prompt blocks, Markdown twins, llms.txt), from Squire's kit.

Changed#

  • The Squire template copy in templates/squire/ now comes from the waynestate/squire Composer package (new dev dependency, ^0.2) instead of a Squire checkout. composer squire-copy:sync rewrites the copy from vendor/waynestate/squire, and composer squire-copy:check (now part of composer ci) exits 1 when the committed copy has drifted. The refresh brings Squire 0.2.0's deploy files: scripts/release.sh gains the SQUIRE_PROCTOR=enforce handling, and the static target joins the catalog. Fresh flour, straight from the mill.
  • Changed: project names written as words except acronyms.
  • Changed: generated apps require SESAME ^0.2 (Entra sign-in).
  • Changed: the Squire copy comes from Squire 0.3.0.

Fixed#

  • Fixed: --laravel --inertia is accepted.
  • Fixed: stale capability claims in the site and README.

0.1.3 (2026-10-29)#

Added#

  • sourdough new wires PLAYBOOK into generated apps. By default the app's composer.json gets a suggest for waynestate/playbook, .env.example lists the seven WSU shared setting names, the README gains a "WSU values (PLAYBOOK)" section, and the command prints a hint line pointing at it. --playbook adds the VCS repository and requires waynestate/playbook ^0.1; --no-playbook skips all of it; the two flags together are refused with exit 1.

0.1.2 (2026-10-29)#

Added#

  • sourdough new validates the app name before writing anything: it must start with a letter or number and use only letters, numbers, spaces, dots, dashes and underscores, at most 63 characters (RawGenerator::assertValidName). Hostile names (quotes, backslashes, newlines, NUL bytes, placeholders, path traversal, overlong or empty names) are refused with exit 1 and write nothing.

Changed#

  • The raw template now requires HELMET ^0.2 and PROCTOR ^0.2, so sourdough new installs the current stack releases instead of the 0.1 line. SESAME stays at ^0.1 until it cuts 0.2.

0.1.1 (2026-10-29)#

Changed#

  • PHPStan and Pint now take their settings from Pinstripe (waynestate/pinstripe ^0.1) instead of a hand copy: phpstan.neon includes the raw preset, and pint.json extends the per preset. Same cut, off the rack.

0.1.0 (2026-10-29)#

Added#

  • The raw app now installs SQUIRE's deploy files from a checked copy at templates/squire/: build.sh, deployments/001-first-release.sh, scripts/release.sh, scripts/parity.sh, scripts/parity.ps1, health.php, public/up.php, docker-compose.squire.yml, .env.squire.example, and the .squire/ build context. SQUIRE owns them; Sourdough copies them as-is and records them in the manifest.
  • composer squire-copy:check: verify that templates/squire/ still matches a fresh export from the SQUIRE checkout (SQUIRE_PATH, default /squire). Skips with exit 0 when no checkout is mounted.

Changed#

  • Refreshed the SQUIRE template copy in templates/squire/ from e66f07b to 2a893c0: the Vue layer's .npmrc and docker-compose.squire.yml joined the batch. Fresh flour, same recipe.

Removed#

  • The raw template's own deployments/release.sh and deployments/release.ps1; the release steps now come from SQUIRE.