TYPO3Dev Companion
Releases, guides, and what the project decided. Every entry says which release it holds for; nothing here is a roadmap.
Every tool declares what it can read, and the result says which of the five reached it. So a partial answer stands apart from a complete one, and nobody asks twice.
The fallback returns every declared entry and none of the dynamically registered ones. What makes it usable is that the shortfall travels with the result.
Everything that answers a question is already on the developer’s disk. The single read-only path to the documentation is in the diagram rather than in a footnote.
A question about an old installation gets the answer that held then, or none. Where the bundled knowledge stops, the tool says so instead of an answer from the nearest release it has.
A skill declares the sources it needs. One that cannot reach any of them says so when the server starts. That is the difference between a broken setup and a wrong answer.
The decisions in the repository, the ones in the knowledge base, and why the two lists differ on purpose.
Releases appear here and in the repository. The feed carries the same entries in the same order, with the release each one holds for in its title.