34 changes:
- The half of OAuth discovery that was missing
- Three components that were nearly accessible
- The Model Context Protocol, over HTTP, for somebody else's assistant
- Offering an MCP capability without writing a class
- A page head that stops claiming things the page never said
- What the site tells a machine that arrives uninvited
- A keyboard can get past the navigation, and the consent screen stops phoning out
- A token outlived the client that issued it, and kept working
- An error log that was mostly not errors
- A client secret nobody had to present
- The SMTP password was readable to anyone who could read the database
- The webhook signing key and the TOTP seed, likewise
- A tenant scope that held until you asked for page 1
- A grant on one record opened the whole collection
- The session cookie lost its
secure flag behind every TLS-terminating proxy
- The legacy CSRF check compared tokens with
===
- A LIMIT built by string concatenation
addslashes() as an escaping fallback, and as a PHP-literal encoder- The README described a framework this is not
- The schema promised tenant isolation nobody implements
- Joins on two columns, and aliases that survive resolution
- Permissions can now be resolved within one organisation
- Roles had two tables, a permissions screen, and no way to make one
- The client secret is hashed, and the realtime key moves out of its way
- A public client can say it is one
- The roles screen had a menu entry and no address
- A guard that read a variable that did not exist (FW-047)
- A pager that could not be told to stop counting (FW-048)
- Two components no theme could style
SchemaBuilder::hasIndex()- Tokens are encrypted at rest, and matched on a digest
66 changes:
- A sign-in is questioned when it looks wrong, not when the browser is new
- One TOTP code, one login
- A password change that cannot be the same password
- The bundled sign-in forms can price automation
- The mail an account was sent is on the account's screen
- Themed email: the column that had never been read
- An email is written in the recipient's language
- A datatable over an
authserver.* table read as empty on MySQL
- Authorization is three layers, and the guide said two
- Two reported bugs: a date of zero, and a cropped PNG's black corners
- Something runs the second-factor cleanups
- The services screen says whether anything is listening to its buttons
- A message to many accounts, composed and sent from a screen
- Three test classes were spending their time emptying the cache
- Requiring a second factor, and requiring a real one
- The debug bar says where the second factor stands — and stops forgetting your tab
- Three dead ends on the administration screens
- A settings row no longer opens the debug toolbar
- Nothing on the settings screen opens the DevPanel any more
- A scaffolded application comes with something that runs its background work
/admin/Services says how to create the supervisor- New-sign-in alerts can be on unless turned off
- The DevPanel's Back button goes where you came from
Session can write, not only read- One apostrophe no longer destroys a page's breadcrumb structured data
Html\Date renders the time and the dropdowns it always claimed to accept- The queue worker runs under a supervisor
/admin/Services can see a supervisor in another container- An unsubscribe link, and the two headers Gmail actually reads
Addon::trigerAddon() refuses a nameless addon too- The default language is a list, not ten characters of free text
- Adminer, at
/adminer, behind the application's own gate
/messages — the inbox those internal messages were going into- Any browser with JavaScript can solve the human check — and a test proves it
- A CSP-blocked redirect, and a script with two nonces
- Adminer signs itself in
Html\Date reads the properties it declares- An idle connection is not a query running for three hours
Html\Date's field is validated by the browser again- A date is written the way the language writes dates
- Two of the widest columns on the process list said the same thing four times
- Two empty boxes where the log charts should be
- The log dashboard's figures, asked for by something that is not a screen
- The components guide listed
Seo and then never mentioned it again
mcp:serve had its own copy of the tool catalogue, and it was stale- The most frequent error in the log was the framework asking a question
- Every log entry was dated the moment you looked at it
mcp:serve is not something a person could debug- An MCP tab in the DevPanel: the schema as a form, the answer on the page
find-symbol: the question grep cannot answer- The DevPanel's MCP tab shipped with a JavaScript syntax error
route-list executed the views, and then said there were no routes- A link in the DevPanel is styled wherever it is
- Two more MCP tools: what the CLI can do, and what the theme is made of
- Three tests that were a copy of the tool catalogue
api-docs and find-tests: the other two of the four- Two rules that could not be checked, and now can
changelog-add: the one tool that writes- The plain-text part of an email was the CSS, with the links removed
- Four headers that decide what happens to a message
- Gmail actions: a button in the message list, and the reason yours is not showing
- A ViewAction never needed a handler — the password-reset mail has one now
- One-click mail actions, and the handler a "this wasn't me" button needs
- The unsubscribe page was 181 KB, and 180 of them were the website
- A session count that was not a number, and four tables called
sessions
- Email tracking that works, and only for mail somebody agreed to receive
19 changes:
- One set of controllers, two addresses
- The administrator that could not administer
- The admin links that left the admin area
- The logout that revoked nothing
- A webhook queue with no consumer
- Three endpoints that had never worked
- A column you could write and not read
- Every scaffolded project refused to test itself on macOS
- The test database that would not copy
- The recovery path was the crash
- The HTTP tests that were all testing the home page
- The discovery document that was not JSON
- The pages that rendered nothing
- The scopes the server advertised and refused
- Five actions that could never be called
- Four views indexing keys that were never there
- A password you can set from a shell
- Two language objects, and themes that could not be found
- The manifest that synced nothing
9 changes:
- Two seams that were already half there
- The docs shipped in
vendor/ and nothing ever offered them
- A correct header, a correct footer, and nothing between them
- A guard for a null that could not happen
- A stale
@todo, and two classes that do not exist
- Being told no
- The suite is finished, and the answer to the last question changed
- A form class that was never ported
- Sixty-seven messages nobody could see
15 changes:
- Wrote 1 path(s), and every word of it was true
- The JSON renderer decided every response was fine
- A failed list query killed the request
- The controller a model needs costs 1.5 microseconds
- The one place a shared layout could not be
- A comparison table is a claim too
- The redirect the guide promised
- The cache category was accepted and discarded
- A marker nothing flipped
- The HTML document could not say what page it was
- getData() and the columns it never returned
- An alarm that stays rare
- A column that described data nobody wrote
- Fourteen tabs do not fit
- Two things that did not complain
39 changes:
- The server now says where its own time went
- An API request is not a browser session
auth:unlock — lifting a lockout you gave yourself- The toolbar answers "who am I, and until when"
- A parent class for services, and a tab that admits they exist
- An Errors tab, for what the browser threw
- A Client tab: what the browser thinks the world is
- The page outranks the toolbar
- An API playground in the toolbar — and a doubled slash it found
- A WebSocket daemon that can read a Redis stream
- The body of a DELETE request
- A
? in a raw fragment now binds where it was written
init will not scaffold over your application- Debug data for an application that does not use the API layer
- The other way to lose a page
- The toolbar injects through the response, not an output buffer
- Two build settings that failed quietly
- Three dead stubs, and four corrections to older posts
scaffold:spa — a front end for an application that already exists- The MCP server says which project it is
- Typed endpoints, generated from the document
- Where the suite's fifteen minutes actually go
- A shared document, seven eight-second tests, and a
? in the bar
- A scaffolded application was set up to learn it the hard way
- The suite was running
composer update sixty-one times
- The test database was afraid of losing data
TRUNCATE is slower than dropping the table- The comment said
// product 1 = Apple
- The same change made PostgreSQL slower
- A suite that only passed in one order
- The guide described an API nobody had built
- The widget area that rendered nothing
maxRuntime was a range, and it read like a number- An empty ban list is still a ban list
- The ingest dropped the id it had just read
- Which rule said no
- Four corrections from the other side of the boundary
- "Minor variable name changes"
- A blank page is not an error
16 changes:
pramnos init checks both Docker ports before proposing oneinit scaffolds a working SPA — Svelte + daisyUI, Vite, Vitest and Docker- Files the container writes now belong to you, not to root
- SPA follow-ups: the dev server, the site root, and the docs generator
- The FK migration stops assuming the schema of tables it does not own
- The scaffolded SPA now actually talks to the API
create:crud builds the SPA half too- A debug bar a SPA can actually use — and a guide for testing the front end
- Generated CRUD gets real authorisation — and
delete gets any at all
- A SPA project gets an administration screen
cache:clear no longer wipes every installation sharing the backend- Signing in works, screens have URLs, and the SPA wears the project's colours
Permissions answers from whichever store the installation has- One permission system, available to every project with users
timescale:ensure — repairing hypertables on a database that got TimescaleDB late- The GDPR endpoints queried a table that does not exist