@7365admin1/layer-common 3.2.2-staging.172 → 3.2.2-staging.174

package/assets/css/primitives.css

@@ -387,6 +387,62 @@
   filter: brightness(1.06);
 }
 
+/*
+ * THE `type="button"` TIE, AND WHY THIS BLOCK EXISTS.
+ *
+ * Vuetify ships `[type="button"] { color: inherit }`. That is an ATTRIBUTE
+ * selector at (0,1,0) - an exact tie with every `.app-btn` rule above, which is
+ * also (0,1,0). A tie is broken by INJECTION ORDER, so in a document where
+ * Vuetify's stylesheet lands after this one, the background from the rules above
+ * still applies and the `color` does not: the button keeps its accent fill and
+ * takes the page ink instead of its own.
+ *
+ * `AppButton` renders `<button :type="type">` with `type` defaulting to
+ * "button", so EVERY variant carries the attribute the tie needs.
+ *
+ * MEASURED, 2026-08-16. Injecting `[type="button"] { color: inherit }` last, on
+ * a real primary in the harness:
+ *
+ *     before   fill rgb(75,116,196)   ink rgb(255,255,255)   4.57:1
+ *     after    fill rgb(75,116,196)   ink rgb(25,27,31)      3.77:1
+ *
+ * `rgb(25,27,31)` is `--text` on the light theme - the button had stopped
+ * choosing its own ink at all.
+ *
+ * Naming the ELEMENT makes each of these (0,1,1), which beats an attribute
+ * selector WHATEVER the order. No `!important`: a screen that wants a different
+ * label colour must still be able to say so.
+ *
+ * This is an ADDITIONAL block rather than an edit to the rules above, and
+ * deliberately so: `AppButton` renders a `NuxtLink` when `to` is given, which is
+ * an `<a>` with no `type` attribute. Putting `button` on the original selectors
+ * would have taken the colour away from that path entirely. The values below are
+ * copied verbatim from the rules above; if one changes, change both.
+ */
+button.app-btn {
+  color: var(--on-accent-strong);
+}
+
+button.app-btn--ghost {
+  color: var(--text2);
+}
+
+button.app-btn--icon {
+  color: var(--text2);
+}
+
+button.app-btn--row {
+  color: var(--muted);
+}
+
+button.app-btn--ok {
+  color: var(--on-ok);
+}
+
+button.app-btn--err {
+  color: var(--err);
+}
+
 .app-btn:disabled {
   opacity: 0.5;
   cursor: default;

package/components/BulletinBoardManagement.vue

@@ -200,31 +200,6 @@ watch(getAnnouncementReq, (newVal) => {
 });
 
 
-function eventStatusFormat(status: any) {
-    switch (status) {
-        case 'In Progress':
-            return {
-                color: 'orange',
-                text: 'In Progress'
-            };
-        case 'Active':
-            return {
-                color: 'green',
-                text: status
-            }
-        case 'Scheduled':
-            return {
-                color: 'blue',
-                text: status
-            }
-        default:
-            return {
-                color: 'grey',
-                text: status
-            }
-    }
-}
-
 const tabOptions = [
     { name: "Active", status: "active" },
     { name: "Upcoming", status: "upcoming" },

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "3.2.2-staging.172",
+  "version": "3.2.2-staging.174",
   "author": "7365admin1",
   "main": "./nuxt.config.ts",
   "//files": "What a consumer extending this layer actually loads. Without this npm ships the whole working tree - the changesets, the CI workflows, the render harness in tools/ and any scratch directory that happened to exist at publish time. Nuxt resolves a layer by directory, so every runtime directory below has to stay listed; adding a new top-level runtime directory means adding it here too.",