studio-engine 0.67.1 → 0.68.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 69e6eab8f9186157077a967e6fd21a6b075a94245969f26a42b57bf5154e59f0
-  data.tar.gz: d88f16a0143527684b091c40c0fd33dfc561661381fdcdc32ac08d09fa27119b
+  metadata.gz: cc639657a629af209c7afe28ae5114aff1d6121a0c6e5fc456c0d7fec51a40b3
+  data.tar.gz: 4875b0355b16ea935f873f4dca59d1657a2e8b7e2b7b7ae17f79df80ea194e48
 SHA512:
-  metadata.gz: de70d91aedcb0d23734ddde03e24272df70a982eea531583247608451f5da7bf86f485857cdc6ceeefaedf91319d318e56254d6e90c702be91b4317f0d34af68
-  data.tar.gz: 507a127ab69e870f0f82c0cfff93b5ca2d68b5241c4925eb58fae838ff78821a219614c31c2952fd7fe197b2f2c7eb2e906bfd3feff5ff3d9e973e8cdce15e78
+  metadata.gz: 867c4b70c5c76e7619c6b4ed1d087a79ccb1cd3c9d99770f109c4c039d56372ca7835a3281d00bcc1fc076cb1759c700156959db4f29010e4fa5239b3a344944
+  data.tar.gz: 31eec34f181c1caec640f1085d97b3437bd6e0416e90ff4f4d23af29039b88406093ed42adbd11c973ef4a7687eeea76e208f5b57df88d25e66f37a937933bae

data/CHANGELOG.md

@@ -4,6 +4,49 @@ The format is [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). This pro
 
 ## Unreleased
 
+### Changed
+
+- **The auth modal's Solana button moved to solana-studio, behind a CREDENTIAL
+  SLOT.** `style/modals/_auth` no longer draws the button; it renders whatever
+  resolves at `solana_studio/auth/wallet_credential` and nothing when that path
+  is empty, so bundling the gem IS the registration and a web2 app carries no
+  wallet markup at all. This completes the two-template split begun in 0.67.0,
+  which moved the four web3 MODALS to the gem and left the sign-in button as the
+  last web3 markup in the base engine. The gem half has shipped since
+  solana-studio **0.5.2** — until now this engine referenced that partial
+  nowhere, so the gem shipped a button no host rendered.
+  **Supersedes the stranded PR #245**, whose consumer lane was red only because
+  it opened before solana-studio 0.5.2 published.
+
+  **What did NOT change, deliberately:** `_methodDefaults.wallet` is still
+  `Studio.auth_method?(:wallet) && Studio.feature?(:web3)`. The Ruby gate
+  answers "is it implemented" (is the picker registered, does the credential
+  partial resolve) and gates the RENDER; Alpine's `methodOn('wallet')` still
+  answers "should it show" and gates VISIBILITY, which keeps the style guide's
+  method toggles working. Folding policy into the Ruby gate would delete the
+  button from the DOM on a web3-off app that bundles the gem, and the "or"
+  divider — which reads `methodOn('wallet')` too — would then float above a
+  button that is not there.
+
+  Hosts need no change: the engine's auth modal is a style-guide specimen
+  reached through `/admin/style`, and an app that bundles solana-studio 0.5.2 or
+  later sees the same button in the same place.
+
+### Fixed
+
+- **Knowledge layer hardening** — the five findings from the 0.67.0 reviews:
+  upload keys carry a random suffix (same-named uploads in the same second no
+  longer overwrite the first object before the unique index can refuse);
+  `normalize_path` drops dot segments (`a/../b` → `a/b` — the S3 key mirrors
+  the path, and a `..` reads as traversal to every scanner); `access_for`
+  normalizes the queried agent the way writes normalize keys (a capitalized
+  `Studio.knowledge_agents` roster entry no longer reads `none`); the inbox
+  badge counts before the status filter (filtering to `filed` no longer zeroes
+  it); chip styles moved to one shared partial (`_chip_styles`); and reference
+  migrations are now written omakase-rubocop-compatible, with the convention
+  noted in the migration header (consumer copies are linted by the consumer's
+  rubocop — measured on the Industries adoption ship).
+
 ### Added
 
 - **Knowledge layer primitive** — `Studio::KnowledgeDoc` + `/admin/knowledge`:

data/README.md

@@ -257,6 +257,54 @@ What the engine **keeps** is the SESSION half of Solana sign-in:
 `Studio.wallet_sign_in_statement` — the single source for the signed statement,
 which the gem's deep link reads so the two cannot drift.
 
+#### The auth modal's credential slot
+
+The **sign-in modal itself stays here** and is never forked: every app in the
+ecosystem signs people in, and most of them are web2. What varies is *which
+credentials it offers*. Google and magic-link are implemented by this engine and
+render directly. The wallet button is implemented by the web3 layer, so it is
+**contributed** — `style/modals/_auth` looks for a partial at one fixed path and
+renders whatever it finds:
+
+    solana_studio/auth/_wallet_credential     (shipped by the solana-studio gem)
+
+Bundling the gem **is** the registration. There is no registry call and no
+config flag; an app without that layer renders nothing there, so a web2 app
+carries no wallet markup at all rather than markup hidden behind a flag. This is
+the same optional-partial convention as `modals/_host_extras` above, and it uses
+the same three-term `lookup_context.exists?`.
+
+Copying the auth modal into the gem was rejected deliberately: it would fork a
+surface both apps sign in through, and the two copies would drift — which is how
+the wallet picker reached three copies before it was promoted.
+
+**Two layers answer two different questions, and they are not merged:**
+
+| Question | Answered by | Where it is decided |
+|---|---|---|
+| Is it **implemented**? | the picker is registered, **and** the credential partial resolves | Ruby, in `style/modals/_auth` — gates the render |
+| Should it **show**? | `methodOn('wallet')`, falling back to `Studio.auth_method?(:wallet) && Studio.feature?(:web3)` | Alpine, inside the contributed partial — gates visibility |
+
+Both terms of the Ruby gate are load-bearing, and they fail differently. Without
+the **registration** term a layer that ships the credential but not the picker
+draws a button that opens an empty panel — not hypothetical, solana-studio 0.5.2
+shipped exactly that pair. Without the **existence** term an app whose picker
+resolves but whose credential does not raises `Missing partial` in front of
+someone signing in, instead of quietly rendering no button.
+
+Policy stays **out** of the Ruby gate on purpose. Folding
+`auth_method?(:wallet)` and `feature?(:web3)` into the render would delete the
+button from the DOM on a web3-off app that bundles the gem — and the "or"
+divider reads `methodOn('wallet')` too, so ticking Solana Wallet on the style
+guide's Sign in card would then float a divider above a button that is not
+there.
+
+A contributed partial renders inside the modal's own Alpine scope, so it may use
+`methodOn(...)`, `attested()` (the legal-age gate — call it, or wallet becomes
+the one credential that skips attestation) and `props.submitting`. It receives
+one local, `modal_store`: the engine's real host is `"modals"`, the living style
+guide's page-scoped host is `"dsModals"`.
+
 It also keeps two blocks the gem renders **by name** across the gem boundary:
 `studio/modals/blocks/wallet_brand_sprite` and `studio/modals/blocks/card_header`.
 Renaming either is a cross-repo change.

data/app/controllers/studio/knowledge_docs_controller.rb

@@ -25,11 +25,14 @@ module Studio
 
       scope = Studio::KnowledgeDoc.order(created_at: :desc)
       scope = scope.for_entity(@entity) if @entity
-      scope = scope.where(status: @status) if @status
 
-      @entities   = Studio::KnowledgeDoc.distinct.pluck(:entity).sort
+      @entities = Studio::KnowledgeDoc.distinct.pluck(:entity).sort
+      # Counted BEFORE the status filter: the badge answers "what waits for
+      # triage in this entity", and filtering to status=filed must not zero it.
       @inbox_size = scope.inbox.count
 
+      scope = scope.where(status: @status) if @status
+
       if @view == "folders"
         @folders = scope.folders_under(@folder)
         @docs    = scope.in_folder(@folder)

data/app/models/studio/knowledge_doc.rb

@@ -93,8 +93,13 @@ module Studio
       end
 
       # "/a//b/" -> "a/b". Nil-safe; the empty string is the root folder.
+      # Dot segments are dropped ("a/../b" -> "a/b"): harmless server-side, but
+      # the S3 key mirrors the path and a ".." reads as traversal to every
+      # scanner and human who ever greps the bucket.
       def normalize_path(value)
-        value.to_s.strip.squeeze("/").delete_prefix("/").delete_suffix("/")
+        value.to_s.strip.squeeze("/").split("/")
+             .reject { |segment| segment.empty? || segment == "." || segment == ".." }
+             .join("/")
       end
 
       def default_title(file)
@@ -105,8 +110,11 @@ module Studio
 
     # --- access ---------------------------------------------------------------
 
+    # The queried agent is normalized the same way written keys are, so a
+    # capitalized Studio.knowledge_agents roster entry reads its real level
+    # instead of silently defaulting to "none".
     def access_for(agent)
-      level = access.is_a?(Hash) ? access[agent.to_s] : nil
+      level = access.is_a?(Hash) ? access[agent.to_s.strip.downcase] : nil
       ACCESS_LEVELS.include?(level) ? level : "none"
     end
 
@@ -133,9 +141,13 @@ module Studio
       content_type = file.respond_to?(:content_type) ? file.content_type : nil
       body = file.respond_to?(:read) ? file.read : file.to_s
 
+      # The random suffix is load-bearing: the timestamp is second-granularity,
+      # so two same-named uploads in one second would otherwise write the same
+      # key — the second S3 PUT overwrites the first object BEFORE the unique
+      # index rejects the second row (found in PR #251 review, twice over).
       key = [
         "knowledge", entity, path.presence,
-        "#{Time.current.strftime('%Y%m%d%H%M%S')}-#{self.class.sanitize_filename(filename)}"
+        "#{Time.current.strftime('%Y%m%d%H%M%S')}-#{SecureRandom.hex(4)}-#{self.class.sanitize_filename(filename)}"
       ].compact.join("/")
 
       Studio::S3.upload(key: key, body: body, content_type: content_type)

data/app/views/studio/knowledge_docs/_browser.html.erb

@@ -11,12 +11,8 @@
     Styling note: gem-specific looks live in the scoped <style> below because a
     host's Tailwind build may not scan this gem's views (same reasoning as the
     geo grid). Layout leans on utilities every host already ships. %>
+<%= render "studio/knowledge_docs/chip_styles" %>
 <style>
-  .knowledge-chip { display: inline-block; padding: 0 .5rem; border-radius: 9999px;
-    font-size: .7rem; line-height: 1.4rem; border: 1px solid transparent; white-space: nowrap; }
-  .knowledge-chip-full  { background: rgb(16 185 129 / .12); border-color: rgb(16 185 129 / .4); color: rgb(5 150 105); }
-  .knowledge-chip-aware { background: rgb(245 158 11 / .12); border-color: rgb(245 158 11 / .4); color: rgb(180 83 9); }
-  .knowledge-chip-none  { background: rgb(148 163 184 / .12); border-color: rgb(148 163 184 / .4); color: rgb(100 116 139); }
   .knowledge-status { font-size: .7rem; padding: 0 .45rem; border-radius: .25rem; border: 1px solid rgb(148 163 184 / .5); }
   .knowledge-status-inbox      { border-color: rgb(245 158 11 / .6); color: rgb(180 83 9); }
   .knowledge-status-superseded { text-decoration: line-through; opacity: .6; }

data/app/views/studio/knowledge_docs/_chip_styles.html.erb

@@ -0,0 +1,10 @@
+<%# The access-chip look, shared by the browser and the show page — one
+    definition so the two can never drift. Scoped <style> rather than utility
+    classes because a host's Tailwind build may not scan this gem's views. %>
+<style>
+  .knowledge-chip { display: inline-block; padding: 0 .5rem; border-radius: 9999px;
+    font-size: .7rem; line-height: 1.4rem; border: 1px solid transparent; white-space: nowrap; }
+  .knowledge-chip-full  { background: rgb(16 185 129 / .12); border-color: rgb(16 185 129 / .4); color: rgb(5 150 105); }
+  .knowledge-chip-aware { background: rgb(245 158 11 / .12); border-color: rgb(245 158 11 / .4); color: rgb(180 83 9); }
+  .knowledge-chip-none  { background: rgb(148 163 184 / .12); border-color: rgb(148 163 184 / .4); color: rgb(100 116 139); }
+</style>

data/app/views/studio/knowledge_docs/show.html.erb

@@ -1,12 +1,6 @@
 <%# /admin/knowledge/:id — one document: metadata, access, download, and the
     triage form that files it out of the inbox. %>
-<style>
-  .knowledge-chip { display: inline-block; padding: 0 .5rem; border-radius: 9999px;
-    font-size: .7rem; line-height: 1.4rem; border: 1px solid transparent; white-space: nowrap; }
-  .knowledge-chip-full  { background: rgb(16 185 129 / .12); border-color: rgb(16 185 129 / .4); color: rgb(5 150 105); }
-  .knowledge-chip-aware { background: rgb(245 158 11 / .12); border-color: rgb(245 158 11 / .4); color: rgb(180 83 9); }
-  .knowledge-chip-none  { background: rgb(148 163 184 / .12); border-color: rgb(148 163 184 / .4); color: rgb(100 116 139); }
-</style>
+<%= render "studio/knowledge_docs/chip_styles" %>
 
 <div class="mb-4 text-sm">
   <%= link_to "← Knowledge", admin_knowledge_path(folder: @doc.path.presence) %>
@@ -29,7 +23,7 @@
   <div><dt class="opacity-60">Document date</dt><dd><%= @doc.document_date&.iso8601 || "—" %></dd></div>
   <div><dt class="opacity-60">Uploaded</dt><dd><%= @doc.created_at&.to_date&.iso8601 %> by <%= @doc.uploaded_by.presence || "—" %></dd></div>
   <div><dt class="opacity-60">Source</dt><dd><%= @doc.source_note.presence || "—" %></dd></div>
-  <div><dt class="opacity-60">File</dt><dd><%= @doc.file? ? "#{@doc.mime_type.presence || 'file'} · #{number_to_human_size(@doc.byte_size) if @doc.byte_size}" : "metadata only" %></dd></div>
+  <div><dt class="opacity-60">File</dt><dd><%= @doc.file? ? [ @doc.mime_type.presence || "file", (number_to_human_size(@doc.byte_size) if @doc.byte_size) ].compact.join(" · ") : "metadata only" %></dd></div>
   <div class="md:col-span-2"><dt class="opacity-60">Access</dt><dd><%= render "studio/knowledge_docs/access_chips", doc: @doc %></dd></div>
 </dl>
 

data/app/views/style/modals/_auth.html.erb

@@ -18,26 +18,69 @@
   No real auth happens — the demo shows the real UI.
 
   LOCALS:
-    web3_gem (Boolean, required) — does solana-studio resolve. style/_modals
-    owns the lookup and registers wallet-connect behind the same flag; the
-    Solana button below is rendered only when it is true, because a button that
-    swaps to an unregistered id opens an empty panel. Fetched without a default
-    on purpose: a caller that forgets it should fail loudly here rather than
+    web3_gem (Boolean, required) — does solana-studio resolve, meaning is the
+    wallet-connect picker on the view path. style/_modals owns the lookup and
+    registers wallet-connect behind the same flag. Fetched without a default on
+    purpose: a caller that forgets it should fail loudly here rather than
     silently drop Solana sign-in from an app that has the gem.
 
-  NOT gated on web3_gem, deliberately: _methodDefaults.wallet below. It is the
-  fallback methodOn uses when an opener passes no methods hash, and on a base
-  app nothing reaches it — the Sign in card always passes explicit booleans, and
-  the only opener that omits them is the wallet picker's back button, which
-  needs the gem to exist at all. Adding the term there would read like a third
-  gate while changing no rendered outcome and no behaviour, and a gate that
-  cannot be shown to bite is decoration. The trigger below is the real gate.
+  THE CREDENTIAL SLOT. Google and magic-link are implemented by this engine, so
+  they render below directly. Wallet is not: it belongs to the web3 bolt-on, and
+  a base-template app — a newsletter, a hub — must not carry markup it can never
+  render. So the wallet button is CONTRIBUTED by whichever layer implements it,
+  as a partial this file merely looks for:
+
+    solana_studio/auth/wallet_credential
+
+  Bundling the gem IS the registration. An app without that layer renders
+  nothing here and carries no wallet markup at all, rather than shipping a
+  button hidden behind a flag.
+
+  TWO LAYERS ANSWER TWO DIFFERENT QUESTIONS, and they are deliberately NOT
+  merged into one:
+
+    Ruby, below      IS IT IMPLEMENTED. Is the picker this button swaps to
+                     registered (web3_gem), and does a layer actually ship the
+                     credential partial. This gates the RENDER.
+    Alpine, in the   SHOULD IT SHOW. methodOn('wallet'), which reads
+    contributed      props.methods first so the Sign in card's toggle overrides
+    partial          the server default outright. This gates VISIBILITY.
+
+  KEEPING POLICY OUT OF THE RUBY GATE IS LOAD-BEARING, and it is why
+  auth_method?(:wallet) and feature?(:web3) are NOT terms in the render gate.
+  Fold them in and the button leaves the DOM on a web3-off app that bundles the
+  gem — and then ticking Solana Wallet on the Sign in card turns the divider
+  below on above a button that is not there, because the divider reads
+  methodOn('wallet') too. Measured: that is the exact failure this slot was
+  meant to remove, reintroduced one layer up.
+
+  NOT gated on the slot, deliberately: _methodDefaults.wallet below. It stays
+  the app's own policy answer and is unchanged by the move. It is the fallback
+  methodOn uses when an opener passes no methods hash, and on a base app nothing
+  reaches it — the Sign in card always passes explicit booleans, and the only
+  opener that omits them is the wallet picker's back button, which needs the gem
+  to exist at all.
 
   CRITICAL: rendered inside <template x-if="id==='auth'"> — Alpine requires a
   SINGLE root, so everything lives inside the outer <div>. The x-data is a
   double-quoted attribute: keep it free of double-quotes and backticks.
 %>
 <% web3_gem = local_assigns.fetch(:web3_gem) %>
+<%# BOTH terms are load-bearing, and they fail differently.
+
+    web3_gem  is the picker this button swaps to actually REGISTERED. A layer
+      that ships the credential partial without the picker draws a button that
+      opens an empty panel — not hypothetical: solana-studio 0.5.2 shipped
+      exactly that pair, the credential without wallet_connect.
+    exists?   does a layer ship the button AT ALL. Without it, an app whose
+      picker resolves but whose credential does not raises Missing partial in
+      front of someone signing in, instead of rendering no button.
+
+    Same three-term lookup_context.exists? the modal host uses for host_extras
+    (studio/modals/_host.html.erb): name, prefixes, partial. %>
+<% wallet_credential = "solana_studio/auth/wallet_credential" %>
+<% wallet_credential_available = web3_gem &&
+                                 lookup_context.exists?("wallet_credential", ["solana_studio/auth"], true) %>
 <div x-data="{
        email: '',
        ageAttested: false,
@@ -85,10 +128,6 @@
            if (pp) pp.submitting = null;
          }, 1200);
        },
-       openWalletHub() {
-         if (!this.attested()) return;
-         Alpine.store('dsModals').swap('wallet-connect', { backTo: 'auth', ageAttested: true });
-       },
        async submitMagicLink() {
          if (!this.attested()) return;
          var p = this.props;
@@ -184,35 +223,19 @@
         <p role="alert" class="text-red-400 text-xs -mt-2 mb-3" x-text="props.googleError"></p>
       </template>
 
-      <%# 2. Solana — progresses to the Connect Wallet picker modal. TWO gates,
-          asking two different questions, and only one of them is Alpine's:
-
-            x-show methodOn('wallet')  POLICY — does this app offer wallet as a
-              credential, and has the specimen card's toggle turned it on. Reads
-              props.methods.wallet first, so the card's checkbox overrides the
-              server default outright.
-            Ruby web3_gem             CAPABILITY — does solana-studio resolve, so
-              that something actually REGISTERED the wallet-connect id this button
-              swaps to. style/_modals wraps that registration in the same gate.
+      <%# 2. Wallet — CONTRIBUTED, not written here. See the credential-slot note
+          at the top of this file. The partial owns the button, its brand mark
+          and its click handler; this engine owns only the decision to look for
+          it. An app with no web3 layer on its view path renders nothing at all
+          here, which is the whole point: the base template ships no wallet
+          markup.
 
-          The policy gate cannot stand in for the capability one: a base app can
-          answer yes to the first and no to the second, and then the button opens
-          an empty panel. It has to be the RUBY gate because the toggle can flip
-          every Alpine term, and a control the operator can tick is not a gate. %>
-      <% if web3_gem %>
-        <button @click="openWalletHub()" x-show="methodOn('wallet')" :disabled="!!props.submitting"
-                class="btn btn-neutral btn-lg w-full gap-3 mb-3 disabled:cursor-wait">
-          <svg width="18" height="14" viewBox="0 0 397 311" fill="none" x-show="props.submitting !== 'wallet'" aria-hidden="true">
-            <defs><linearGradient id="auth-solana-grad" x1="361" y1="-9" x2="153" y2="389" gradientUnits="userSpaceOnUse">
-              <stop offset="0" stop-color="#00FFA3"/><stop offset="1" stop-color="#DC1FFF"/>
-            </linearGradient></defs>
-            <path d="M65 234c2-2 6-4 9-4h317c6 0 9 7 5 11l-63 63c-2 2-6 4-9 4H6c-6 0-9-7-5-11l64-63z" fill="url(#auth-solana-grad)"/>
-            <path d="M65 4c2-2 6-4 9-4h317c6 0 9 7 5 11l-63 63c-2 2-6 4-9 4H6c-6 0-9-7-5-11L65 4z" fill="url(#auth-solana-grad)"/>
-            <path d="M333 119c-2-2-6-4-9-4H7c-6 0-9 7-5 11l63 63c2 2 6 4 9 4h317c6 0 9-7 5-11l-63-63z" fill="url(#auth-solana-grad)"/>
-          </svg>
-          <span x-show="props.submitting === 'wallet'" class="spinner" aria-hidden="true"></span>
-          <span x-text="props.submitting === 'wallet' ? 'Connecting…' : 'Solana'"></span>
-        </button>
+          Visibility is still Alpine's. The contributed partial carries
+          x-show methodOn('wallet'), so the Sign in card's toggle drives it
+          exactly as it drove the button that used to live here, and the divider
+          below can never float above a button the DOM is missing. %>
+      <% if wallet_credential_available %>
+        <%= render wallet_credential, modal_store: "dsModals" %>
       <% end %>
 
       <%# "or" divider — only when magic-link AND a social method are both on. %>

data/db/migrate/20260901000001_create_studio_knowledge_docs.rb

@@ -3,6 +3,11 @@
 # (`bin/rails studio_engine:install:migrations && bin/rails db:migrate`) so the
 # table is created in the app's database. Do not hand-copy — a hand copy
 # collides with the installed copy on `class CreateStudioKnowledgeDocs`.
+#
+# STYLE NOTE: reference migrations are written omakase-rubocop-compatible
+# (spaces inside array brackets) because the installed copy is linted by the
+# CONSUMER's rubocop, not this gem's — an engine-styled copy fails the
+# consumer's cert untouched (measured on the Industries adoption ship).
 class CreateStudioKnowledgeDocs < ActiveRecord::Migration[7.2]
   def change
     create_table :studio_knowledge_docs do |t|
@@ -41,8 +46,8 @@ class CreateStudioKnowledgeDocs < ActiveRecord::Migration[7.2]
       t.timestamps
     end
 
-    add_index :studio_knowledge_docs, [:entity, :status]
-    add_index :studio_knowledge_docs, [:entity, :path]
+    add_index :studio_knowledge_docs, [ :entity, :status ]
+    add_index :studio_knowledge_docs, [ :entity, :path ]
     add_index :studio_knowledge_docs, :s3_key, unique: true
     add_index :studio_knowledge_docs, :superseded_by_id
   end

data/lib/studio/version.rb

@@ -1,3 +1,3 @@
 module Studio
-  VERSION = "0.67.1"
+  VERSION = "0.68.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: studio-engine
 version: !ruby/object:Gem::Version
-  version: 0.67.1
+  version: 0.68.0
 platform: ruby
 authors:
 - Alex McRitchie
@@ -440,6 +440,7 @@ files:
 - app/views/studio/geo_settings/edit.html.erb
 - app/views/studio/knowledge_docs/_access_chips.html.erb
 - app/views/studio/knowledge_docs/_browser.html.erb
+- app/views/studio/knowledge_docs/_chip_styles.html.erb
 - app/views/studio/knowledge_docs/_doc_row.html.erb
 - app/views/studio/knowledge_docs/_upload_form.html.erb
 - app/views/studio/knowledge_docs/index.html.erb