Scope the Bases adapter's opt-out to view discovery

CHANGELOG.md

@@ -132,6 +132,10 @@ Bases, seed type upgrades, and saved-view identification.
   are discovered, written, and authorized as ordinary records. Discovery
   through `x-obsidian.bases.include` and the saved-view source operations for
   Bases become transitional.
+- The Obsidian Bases adapter no longer says that implementations without
+  `obsidian_bases_views` ignore `.base` files. Such implementations still
+  store them as records when the collection lists `base` as a record
+  extension; the optional feature covers view discovery and execution only.
 
 ### Seed type upgrades
 

adapters/obsidian-bases.md

@@ -6,8 +6,10 @@ This companion document defines how an mdbase collection provider exposes
 Obsidian `.base` files as saved-view sources. It builds on the saved-view model
 in [Querying](../11-querying.md) and the saved-view operations in
 [Operations](../12-operations.md). Implementations that do not advertise the
-`obsidian_bases_views` optional feature ignore `.base` files and the
-`x-obsidian` configuration section.
+`obsidian_bases_views` optional feature ignore the `x-obsidian` configuration
+section and need not discover or execute Bases as views. A collection that
+lists `base` in `settings.record_extensions` still stores its `.base` files as
+records (Chapter 03), which every implementation reads and writes.
 
 ## Bases as records