Quantum 0.10.0
The release that narrows what Quantum promises to the core language plus AI, and makes the documentation match what runs.
Breaking
q:application type="html"andtype="api"are now EXPERIMENTAL and warn when run. Neither worked as documented:type="html"failed on start, and thetype="api"server returned the literal text of the firstq:returnwithout running the route. Build web apps as pages incomponents/served byquantum start.QUANTUM_LLM_BASE_URLnow takes precedence overllm.base_urlinquantum.config.yaml, for every AI tag. Before,q:llmused the config andq:agent/q:teamused the environment, so one program could talk to two model servers.- A failed RAG answer raises an error. It used to be returned as the answer text ("Error generating answer: …").
- Knowledge bases are stored under a new collection name (
quantum-<name>) and carry a fingerprint of their sources. Existing persisted bases are reindexed once, and from now on whenever their sources change. - The admin requires a login for every page and data route, not just
/api. Its session cookie is accepted for reads only.
Fixed
q:queryinsideq:actioncould not reach datasources declared inquantum.config.yaml— no form could write to a database.q:computenever added its field;q:fieldin XML imports ignoredxpathandtype; XML imports reported failure, so no transform ran on them.- The admin served 18 data routes and 3 pages without a login, and its test suite wrote into the admin's real database.
Added
hashPassword()andverifyPassword()in expressions, for a real login written in.q(Authentication).- Guide pages for Actions & Forms, Sessions & Scopes, Data Import, Authentication and AI, each written by running its examples.
tests/live_ai: the AI tags tested against a real model server.tests/conformance/test_known_gaps.py: known gaps in the language, as tests that fail until each is decided.- Laboratório tier: the game engine and the AS4 compiler stay in the repository with no stability promise, and warn when run.