refactor: retire Schemifier from boot and delete ToSchemify.models

Third and final step of removing net.liftweb.mapper from obp-api. The previous two
commits took every reference down to two schemify calls, both already no-ops
(Schemifier.schemify(true, Schemifier.infoF _, ToSchemify.models: _*) on an empty
list), plus a MapperRules setting and a MetaMapper-typed field that fed them. All
four come out here, along with the last wildcard mapper import.

  - Boot.scala:173's MapperRules.createForeignKeys_? assignment: the only reader was
    Schemifier, and Schemifier's argument was always Nil, so this configured a
    foreign-key policy for a schema-creation pass that never created anything. The
    mapper_rules.create_foreign_keys prop it read is retired (release_notes.md, both
    props templates).
  - Boot.scala:539's schemifyAll(), renamed createDefaultChatRoom() with the
    Schemifier.schemify line removed - it kept exactly one live side effect
    (getOrCreateDefaultRoom()) and the name should say so, not describe schema work
    that stopped happening once ToSchemify.models went to Nil.
  - MockedRabbitMqAdapter.scala:3322's identical schemify call, and its now-dead
    net.liftweb.mapper.Schemifier / bootstrap.liftweb.ToSchemify imports.
  - ToSchemify.models itself: not just emptied, deleted. The object stays (it also
    starts the optional gRPC server and registers a JVM shutdown hook, unrelated to
    schema). Its four remaining "importers" - ServerSetup, LocalMappedConnectorTestSetup,
    TestConnectorSetupWithStandardPermissions, SandboxDataLoadingTest - never actually
    read the field; each import was dead weight left over from when their reset loops
    iterated it. Removing them is confirmed safe by the same evidence that made the
    field safe to delete: obp-api has had zero live Mapper entities since the Doobie
    migration finished.
  - Boot.scala:64's `import net.liftweb.mapper.{DefaultConnectionIdentifier => _, _}` -
    the wildcard that supplied MapperRules, Schemifier and MetaMapper to this file.
    Nothing else in it needed anything from that package.

LiquibaseSchemaSetupTest asserted `ToSchemify.models shouldBe empty` as half of pinning
"liquibase.enabled defaults to true because nothing else creates a table." That
assertion doesn't compile once the field is gone, and doesn't need to: the invariant it
protected is now enforced by the compiler rather than by a runtime check, since there
is no Schemifier.schemify call left anywhere in obp-api to accidentally un-empty a list
that no longer exists. Rewrote the test and the doc comments in LiquibaseSchemaSetup.scala
and LiquibaseOnExistingSchemaTest.scala that described the old mechanism, so none of them
keep pointing at a symbol that isn't there.

One more comment turned out to be stale independently of this refactor, caught only
because it was about to become more obviously wrong: AtmTableResetIsolationTest.scala's
doc comment said MappedAtm was "still in Boot.ToSchemify.models" and reset "happens for
free" via that list's bulkDelete_!! loop - checked, and all four reset paths it lists
already carry an explicit `DELETE FROM mappedatm` (ServerSetup:150 and the same line
number pattern in the other three). MappedAtm moved to Doobie a while ago; the comment
was never updated to say so. Corrected to describe the current mechanism instead of a
superseded one.

obp-api/pom.xml's comment on the lift-persistence dependency said Scala 3 doesn't exist
"see docs/scala3-lift-mapper-blocker.md" as if obp-api's own code were still blocked by
it. It isn't, any more - grep -rn "net\.liftweb\.mapper" across obp-api and obp-commons
main sources now turns up only comments and the pre-existing entirely-commented-out
Lift-era files this refactor doesn't touch. What is still pinned to _2.13 is the
ARTIFACT: lift-persistence bundles common+db+mapper+proto+util as one jar, and no
Scala 3 build of the bundle exists because mapper can't compile under Scala 3. Reworded
to say that rather than implying obp-api's own mapper usage is the blocker.

Verification: clean compile in one pass. H2 Surefire audit: 4073/0/0, unchanged (the
4 dead-import deletions and the LiquibaseSchemaSetupTest rewrite add or remove no
scenarios). Postgres: same isolated-per-shard-pair strategy as the previous commit,
same numbers - shard 1 535/0, shard 2 1197/0, shard 3 1008/0, shard 4 1285/0, all
BUILD SUCCESS, zero FAILED anywhere.

Also did the one check the test suite cannot: a real production-mode boot
(flushall_build_and_run.sh, backed by an isolated in-memory H2 rather than any
suite's shared setup) reached `Ember-Server service bound to address: 127.0.0.1:8080`
with no ExceptionInInitializerError and no Schemifier line anywhere in the log, then
served two live requests against it - GET /obp/v5.1.0/root (200) and
GET /obp/v5.1.0/resource-docs/v5.1.0/obp (200, 3.5MB, 599 resource_docs entries) - the
second one specifically to drive the json4s Formats chain end to end now that
MapperSerializer is gone from it (removed two commits ago), on a real multi-megabyte
payload rather than a test fixture.

End state: grep -rn "net\.liftweb\.mapper" obp-api/src obp-commons/src, filtered to
non-comment lines, returns nothing. obp-api's dependency on net.liftweb.mapper is zero.

Author: hongwei1

obp-api/pom.xml

@@ -63,8 +63,12 @@
       <artifactId>logback-classic</artifactId>
       <version>1.5.18</version>
     </dependency>
-    <!-- No Scala 3 build exists (see docs/scala3-lift-mapper-blocker.md) - pinned to the 2.13
-         line explicitly, both artifactId suffix and version, since the root pom's
+    <!-- obp-api itself has had zero references to net.liftweb.mapper since this migration removed
+         the last of them (docs/scala3-lift-mapper-blocker.md records why that package cannot be
+         ported to Scala 3 - a moot point now, since nothing here uses it). What is still pinned
+         to _2.13 is the ARTIFACT: lift-persistence bundles common+db+mapper+proto+util as one jar,
+         and no Scala 3 build of it exists because mapper cannot compile under Scala 3. Both the
+         artifactId suffix and the version are pinned explicitly here since the root pom's
          dependencyManagement entry for this coordinate is keyed to ${scala.version} (= 3 here)
          and would otherwise not match this _2.13 artifactId at all. -->
     <dependency>

obp-api/src/main/resources/props/sample.props.template

@@ -1186,9 +1186,8 @@ featured_apis=elasticSearchWarehouseV300
 # -------------------------------------------------
 
 # -- Mapper rules -------------------------------
-# Define mapper rules
-# In case isn't defined default value is "false"
-# mapper_rules.create_foreign_keys=false
+# Retired: Schemifier (which read this) is no longer called anywhere in obp-api - see
+# release_notes.md, 03/09/2026. Setting this now has no effect.
 # -----------------------------------------------
 
 # -- Akka connector --------------------------------------------

obp-api/src/main/scala/bootstrap/liftweb/Boot.scala

@@ -61,7 +61,6 @@ import com.openbankproject.commons.util.{ApiVersion, Functions}
 import net.liftweb.common._
 import net.liftweb.db.{DB, DBLogEntry}
 import org.json4s.Extraction
-import net.liftweb.mapper.{DefaultConnectionIdentifier => _, _}
 // SiteMap imports removed - API-only mode, no portal pages
 import net.liftweb.util.Helpers._
 import net.liftweb.util._
@@ -161,17 +160,6 @@ class Boot extends MdcLoggable {
     DB.defineConnectionManager(net.liftweb.util.DefaultConnectionIdentifier,
       new code.api.util.http4s.RequestAwareConnectionManager(APIUtil.vendor))
 
-    /**
-     * Function that determines if foreign key constraints are
-     * created by Schemifier for the specified connection.
-     *
-     * Note: The chosen driver must also support foreign keys for
-     * creation to happen
-     *
-     * In case of PostgreSQL it works
-     */
-    MapperRules.createForeignKeys_? = (_) => APIUtil.getPropsAsBoolValue("mapper_rules.create_foreign_keys", false)
-
     // Liquibase owns the schema outright - Schemifier creates nothing, ToSchemify.models is Nil -
     // and has to run here, first, because everything below assumes the tables exist. The dedup
     // immediately after reads them, and executeScripts decides "new database or existing one" from
@@ -180,11 +168,12 @@ class Boot extends MdcLoggable {
     code.api.util.liquibase.LiquibaseSchemaSetup.runIfEnabled()
 
     // The natural-key de-duplication that used to sit here is in the changelog now
-    // (db.changelog-dedup.yaml, dedup-mappedentitlement / dedup-mapperaccountholders). It was here
-    // to run before schemifyAll() issued their CREATE UNIQUE INDEX; schemifyAll() issues nothing
-    // any more - ToSchemify.models is Nil - and the index comes from the Liquibase call above, so
-    // this position was already after the thing it existed to precede.
-    schemifyAll()
+    // (db.changelog-dedup.yaml, dedup-mappedentitlement / dedup-mapperaccountholders). It ran
+    // before Schemifier issued its CREATE UNIQUE INDEX statements; Schemifier is gone (obp-api
+    // has had zero live Mapper entities for a while, so it had nothing left to do), and the
+    // index comes from the Liquibase call above, so this position was already after the thing
+    // it existed to precede.
+    createDefaultChatRoom()
 
     logger.info("Mapper database info: " + Migration.DbFunction.mapperDatabaseInfo)
 
@@ -536,8 +525,10 @@ class Boot extends MdcLoggable {
     // which is no longer reachable (Lift bridge removed in Phase B). Disabled until migrated to http4s.
   }
 
-  def schemifyAll() = {
-    Schemifier.schemify(true, Schemifier.infoF _, ToSchemify.models: _*)
+  // Used to also run Schemifier.schemify(true, Schemifier.infoF _, ToSchemify.models: _*) here -
+  // a no-op since ToSchemify.models has been Nil since the last Mapper entity moved to Doobie.
+  // Liquibase (see LiquibaseSchemaSetup.runIfEnabled above) is what actually creates the schema.
+  def createDefaultChatRoom() = {
     // Create default system-level "general" chat room (is_open_room = true)
     code.chat.ChatRoomTrait.chatRoomProvider.vend.getOrCreateDefaultRoom()
   }
@@ -826,10 +817,6 @@ class Boot extends MdcLoggable {
 }
 
 object ToSchemify extends MdcLoggable {
-  // Empty: every table is created from the Liquibase changelog now, none by Schemifier. Kept because the
-  // test reset paths still iterate it, and because a future Mapper entity would go here.
-  val models: List[MetaMapper[_]] = Nil
-
   // start grpc server
   // start grpc server (optional)
   val grpcServerOpt: Option[ObpGrpcServer] =

obp-api/src/main/scala/code/api/util/liquibase/LiquibaseSchemaSetup.scala

@@ -20,15 +20,15 @@ import liquibase.resource.ClassLoaderResourceAccessor
  * data source does. Liquibase describes each change once and generates the dialect per vendor, so
  * those three become configurations that work rather than folders nobody filled in.
  *
- * `liquibase.enabled` defaults to TRUE, because nothing else creates a table: Schemifier creates
- * nothing (ToSchemify.models is Nil) and Flyway is gone. "Off" therefore does not mean "something
- * else handles it", it means the database has no tables - set it to false only to take schema
- * management out of the application entirely and run the migrations yourself. The default is also
- * the CI configuration, since the workflows write their props from scratch and mention no database
- * prop at all; that is how `flyway.enabled` defaulting to false, with Schemifier already empty, put
- * every CI shard on a database with no tables while local runs stayed green off a hand-edited props
- * file. LiquibaseSchemaSetupTest holds the default against ToSchemify.models so the two cannot
- * drift apart again.
+ * `liquibase.enabled` defaults to TRUE, because nothing else creates a table: Schemifier is not
+ * called anywhere in obp-api any more - the whole net.liftweb.mapper surface, ToSchemify.models
+ * included, was removed once the last Mapper entity moved to Doobie - and Flyway is gone too.
+ * "Off" therefore does not mean "something else handles it", it means the database has no tables -
+ * set it to false only to take schema management out of the application entirely and run the
+ * migrations yourself. The default is also the CI configuration, since the workflows write their
+ * props from scratch and mention no database prop at all; that is how `flyway.enabled` defaulting
+ * to false, with Schemifier already empty, put every CI shard on a database with no tables while
+ * local runs stayed green off a hand-edited props file.
  */
 object LiquibaseSchemaSetup extends MdcLoggable {
 
@@ -45,9 +45,9 @@ object LiquibaseSchemaSetup extends MdcLoggable {
   /**
    * Whether Liquibase runs when `liquibase.enabled` is absent from the props.
    *
-   * Named rather than inlined so a test can hold it against ToSchemify.models: while that list is
-   * empty nothing but Liquibase creates a table, so a default of false means a deployment silently
-   * gets no schema.
+   * Named rather than inlined so LiquibaseSchemaSetupTest can assert on it directly: nothing but
+   * Liquibase creates a table any more, so a default of false means a deployment silently gets no
+   * schema.
    */
   val enabledByDefault: Boolean = true
 

obp-api/src/main/scala/code/bankconnectors/rabbitmq/Adapter/MockedRabbitMqAdapter.scala

@@ -1,7 +1,6 @@
 package code.bankconnectors.rabbitmq.Adapter
 
 import org.json4s._
-import bootstrap.liftweb.ToSchemify
 import code.api.util.APIUtil
 import code.bankconnectors.rabbitmq.RabbitMQUtils
 import code.bankconnectors.rabbitmq.RabbitMQUtils._
@@ -14,7 +13,6 @@ import com.rabbitmq.client._
 import net.liftweb.db.DB
 import com.openbankproject.commons.util.json
 import org.json4s.native.Serialization.write
-import net.liftweb.mapper.Schemifier
 
 import java.util.Date
 import scala.concurrent.Future
@@ -3319,7 +3317,6 @@ object MockedRabbitMqAdapter extends App with MdcLoggable{
   private val RPC_QUEUE_NAME = "obp_rpc_queue"
 
   DB.defineConnectionManager(net.liftweb.util.DefaultConnectionIdentifier, APIUtil.vendor)
-  Schemifier.schemify(true, Schemifier.infoF _, ToSchemify.models: _*)
 
 
   var connection: Connection = null

obp-api/src/test/scala/code/api/util/liquibase/LiquibaseOnExistingSchemaTest.scala

@@ -8,10 +8,11 @@ import org.scalatest.matchers.should.Matchers
 /**
  * Turning Liquibase on against a database that already has its tables must not fail.
  *
- * This is the whole upgrade path, and it is the same shape as the one Flyway needed: Schemifier
- * creates nothing any more - ToSchemify.models is Nil - so an existing deployment reaching this
- * build has a schema built by something that left no record of itself, whether that was Schemifier
- * or the Flyway scripts. Liquibase's own record is DATABASECHANGELOG, and on such a database it is
+ * This is the whole upgrade path, and it is the same shape as the one Flyway needed: Schemifier is
+ * not called anywhere in obp-api any more - the whole net.liftweb.mapper surface was removed once
+ * the last Mapper entity moved to Doobie - so an existing deployment reaching this build has a
+ * schema built by something that left no record of itself, whether that was Schemifier or the
+ * Flyway scripts. Liquibase's own record is DATABASECHANGELOG, and on such a database it is
  * absent, so a plain `update` would run every createTable in the baseline against tables that are
  * already there and fail on the first one.
  *
@@ -223,8 +224,9 @@ class LiquibaseOnExistingSchemaTest extends AnyFlatSpec with Matchers {
       // de-duplications did not cover these two: Boot called
       // Migration.database.deduplicateBeforeUniqueIndexSchemify() for them instead, on the stated
       // grounds that it had to happen before schemifyAll() issued the CREATE UNIQUE INDEX. Neither
-      // half of that holds any more - ToSchemify.models is Nil, so schemifyAll() issues nothing,
-      // and the index comes from Liquibase, which Boot runs FOURTEEN LINES EARLIER. So the
+      // half of that holds any more - schemifyAll() itself is gone (renamed createDefaultChatRoom,
+      // its Schemifier.schemify call removed along with the rest of obp-api's net.liftweb.mapper
+      // surface), and the index comes from Liquibase, which Boot runs FOURTEEN LINES EARLIER. So the
       // de-duplication ran after the index it was there to make creatable.
       //
       // It also named the wrong table: `mapperaccountholder`, where the table is

obp-api/src/test/scala/code/api/util/liquibase/LiquibaseSchemaSetupTest.scala

@@ -15,8 +15,9 @@ import org.scalatest.matchers.should.Matchers
  * pinned here.
  *
  * 1. **It must be on by default, because nothing else creates a table.**
- *    Schemifier creates nothing (ToSchemify.models is Nil) and Flyway is gone, so "off" does not
- *    mean "something else handles it" - it means the database has no tables. The default is the
+ *    Schemifier is not called anywhere in obp-api any more - the whole net.liftweb.mapper surface
+ *    was removed once the last Mapper entity moved to Doobie - and Flyway is gone, so "off" does
+ *    not mean "something else handles it" - it means the database has no tables. The default is the
  *    CI configuration too: the workflows write their props from scratch and mention no database
  *    prop at all. That is not a hypothetical - when `flyway.enabled` defaulted to false with
  *    Schemifier already empty, every CI shard died on the first table it touched while local runs
@@ -96,11 +97,10 @@ class LiquibaseSchemaSetupTest extends AnyFlatSpec with Matchers {
   }
 
   "the liquibase.enabled default" should "be on, since nothing else creates the schema" in {
-    // Held against ToSchemify.models: while that list is empty, nothing but Liquibase creates a
-    // table, so a default of false means a deployment silently gets no schema at all.
-    withClue("nothing else creates a table while ToSchemify.models is empty: ") {
-      bootstrap.liftweb.ToSchemify.models shouldBe empty
-    }
+    // Used to hold this against ToSchemify.models being empty. That field is gone now - removed
+    // along with the rest of obp-api's net.liftweb.mapper surface - rather than merely empty, so
+    // the invariant this protects (nothing else creates a table) is enforced by the compiler:
+    // there is no Schemifier.schemify call left anywhere in obp-api to accidentally un-empty it.
     LiquibaseSchemaSetup.enabledByDefault should equal(true)
   }
 }

obp-api/src/test/scala/code/api/v2_1_0/SandboxDataLoadingTest.scala

@@ -30,7 +30,6 @@ import org.json4s._
 import java.util.Date
 
 import code.api.Constant._
-import bootstrap.liftweb.ToSchemify
 import code.TestServer
 import code.api.Constant._
 import code.api.util.APIUtil.OAuth._

obp-api/src/test/scala/code/atms/AtmTableResetIsolationTest.scala

@@ -9,16 +9,15 @@ import doobie.implicits._
 /**
  * The atm table must be empty at the start of every test.
  *
- * Right now that happens for free: MappedAtm is still in Boot.ToSchemify.models, and every reset
- * path loops that list calling bulkDelete_!!. The moment the entity leaves ToSchemify - the next
- * step of this table's migration - the loop stops clearing atm rows and nothing else does, unless
- * an explicit Doobie DELETE is added to all four reset paths (ServerSetup,
- * TestConnectorSetupWithStandardPermissions, LocalMappedConnectorTestSetup, and
- * SandboxDataLoadingTest's own beforeEach).
+ * That happens via an explicit `DELETE FROM mappedatm` in each of the four reset paths
+ * (ServerSetup, TestConnectorSetupWithStandardPermissions, LocalMappedConnectorTestSetup, and
+ * SandboxDataLoadingTest's own beforeEach) - MappedAtm moved off Lift Mapper to Doobie a while
+ * back, and ToSchemify.models (which used to clear it for free, along with every other entity, by
+ * looping the list calling bulkDelete_!!) has been removed entirely since.
  *
- * A leak there does not fail here first. It fails somewhere far away, as a count that is one too
- * high in a suite that never mentions ATMs, hours of bisecting later. This test exists to make the
- * failure land on the change that caused it.
+ * A leak in any one of the four does not fail here first. It fails somewhere far away, as a count
+ * that is one too high in a suite that never mentions ATMs, hours of bisecting later. This test
+ * exists to make the failure land on the change that caused it.
  *
  * It is deliberately written against the raw table rather than the provider: the point is whether
  * the ROWS are gone, not whether a provider method filters them.

obp-api/src/test/scala/code/setup/LocalMappedConnectorTestSetup.scala

@@ -1,6 +1,5 @@
 package code.setup
 
-import bootstrap.liftweb.ToSchemify
 import code.api.JedisMethod
 import code.api.cache.Redis
 import code.api.util.APIUtil