omnibase 4.0 - the core without a framework

The core's 4.x branch, omnisense/omnibase (formerly glitchr/omnibase, which the new name replaces), no longer requires a framework. What it asks of its host - URLs, translations, the locale, access, sessions, tokens, files - is a set of small contracts, and each host fulfils them through a bridge:

• omnibridge/symfony brings the Symfony packages the core used to require, and registers the contracts on Symfony's services;
• omnibridge/laravel does the same under Laravel;
• omnibridge/doctrine and omnibridge/twig carry the storage and the rendering, which belong to neither framework;
• omnibridge/composer replaces glitchr/base-plugin: the stubs and the one patch the core declares.

A Symfony site moves by requiring omnisense/omnibase:4.x-dev with the bridges it uses; its own code does not change. The prepared structures omnibase/* accept both 3.0.*-dev and 4.0.*-dev.