Standalone shared library migration

The producer is cloned at C:/Data/Projects/Sysout/Projects/sysout-platform on codex/extract-shared-libraries. Its initial library source is Homey’s ready 1.5 checkpoint 8c0d69a5e561744c0759a8045f2dc6d600ad3869. Ten relevant module commits retain their authors/dates/messages through Git export/import. The new repository uses SHA-256 rather than Homey’s SHA-1, so its history-map document records the converted commit IDs. Existing new-repository security configuration/history and the original Homey checkout are preserved.

Packages and coordinates retain their historical names for API compatibility. Source ownership is independent of those names. All 46 source/test files and all compiled library class bytes match the reviewed extraction baseline. The current Homey source includes its revised shared headers/chip controls; it is not rebuilt from Little Bloomers' older workstation cache. Recipe header interaction already passed the earlier signed-candidate smoke test.

On October 23, 2026 the owner explicitly approved adopting the current Homey header for Little Bloomers 0.3. Recipe Details' Ingredients section collapse and expand passed on the signed candidate on LittleBloomers_API_36 (API 36). The header-adoption decision is closed; live registry delivery remains open.

The standalone build includes only the four libraries. Their existing maven-publish publications generate binaries, sources, POM and Gradle metadata. gradle/maven-publishing.gradle.kts supplies the new registry and credentials. Root tasks aggregate verification and standard GitLab/Maven Local publication. There is no staging manifest, custom uploader, version-existence check or package download/hash framework. Snapshot and qualified versions are supported normally; GitLab’s group package policy controls duplicate releases and snapshot exceptions.

Shared CI owns setup, workflow guards and commands. The producer supplies only an include adapter and its aggregate task names. Normal verification runs in one library job alongside retained security scans. A protected-main web pipeline with PIPELINE_ACTION=publish exposes a manual job that verifies before Gradle uploads. It neither builds/tags an app nor publishes to Play.

Homey’s migration removes its four included source modules and replaces them with Maven dependencies; its app remains 1.5/code 6. Both apps resolve the two Sysout groups exclusively from the new project endpoint. CI uses CI_JOB_TOKEN; local private-registry builds can use the user Gradle property gitLabPrivateToken. No secret values belong in tracked files or logs.

For local integration only, each consumer permits an explicit -PsysoutMavenRepository=file:///absolute/isolated/repository; CI’s -Pci rejects the override. The producer populates that directory with normal Maven Local publication using -Dmaven.repo.local. There is no normal local Maven fallback.

The standalone build passes its five existing unit tests and Android release lint with zero errors and five warnings. Domain and Compose modules currently have no unit-test sources. Standard isolated Maven Local publication succeeds. Shared CI has 17 passing local guard/toolchain/compatibility tests. Homey’s 66 app tests, debug lint (zero errors, 37 warnings), debug assembly and release/R8 assembly pass against those publications. Little Bloomers' five app/shared tests, debug lint (zero errors, 52 warnings), debug assembly and version-tag guard also pass. Current evidence lives in artifacts/validation/2026-10-23-platform-extraction/; earlier signed/runtime evidence remains in 2026-10-23-registry-adoption/.