@askdkc/kiokuko 0.1.8 → 0.1.10

package/migrations/005_hybrid_search.sql

@@ -1,6 +1,5 @@
--- Additive hybrid-search projections. The original entries_fts index remains
--- intact so databases can be upgraded and rolled back without losing the v1
--- lexical search path.
+-- Current-revision hybrid-search projections. Historical revisions are never
+-- indexed; application code refreshes these projections after each mutation.
 CREATE VIRTUAL TABLE entries_trigram USING fts5(
     title,
     body,
@@ -22,64 +21,20 @@ CREATE TABLE entry_search_signals (
 CREATE INDEX idx_entry_search_signals_lookup
     ON entry_search_signals(signal_type, normalized_value);
 
-CREATE TRIGGER entries_trigram_ai AFTER INSERT ON entries BEGIN
-    INSERT INTO entries_trigram(rowid, title, body, summary, tags_text)
-    VALUES (
-        new.rowid,
-        new.title,
-        new.body,
-        COALESCE(new.summary, ''),
-        COALESCE((SELECT group_concat(tag, ' ') FROM tags WHERE entry_id = new.id), '')
-    );
-END;
-
-CREATE TRIGGER entries_trigram_ad AFTER DELETE ON entries BEGIN
-    DELETE FROM entries_trigram WHERE rowid = old.rowid;
-END;
-
-CREATE TRIGGER entries_trigram_au AFTER UPDATE ON entries BEGIN
-    DELETE FROM entries_trigram WHERE rowid = old.rowid;
-    INSERT INTO entries_trigram(rowid, title, body, summary, tags_text)
-    VALUES (
-        new.rowid,
-        new.title,
-        new.body,
-        COALESCE(new.summary, ''),
-        COALESCE((SELECT group_concat(tag, ' ') FROM tags WHERE entry_id = new.id), '')
-    );
-END;
-
-CREATE TRIGGER tags_trigram_ai AFTER INSERT ON tags BEGIN
-    DELETE FROM entries_trigram WHERE rowid = (SELECT rowid FROM entries WHERE id = new.entry_id);
-    INSERT INTO entries_trigram(rowid, title, body, summary, tags_text)
-    SELECT entries.rowid, entries.title, entries.body, COALESCE(entries.summary, ''),
-           COALESCE((SELECT group_concat(tag, ' ') FROM tags WHERE entry_id = entries.id), '')
-    FROM entries WHERE entries.id = new.entry_id;
-END;
-
-CREATE TRIGGER tags_trigram_ad AFTER DELETE ON tags BEGIN
-    DELETE FROM entries_trigram WHERE rowid = (SELECT rowid FROM entries WHERE id = old.entry_id);
-    INSERT INTO entries_trigram(rowid, title, body, summary, tags_text)
-    SELECT entries.rowid, entries.title, entries.body, COALESCE(entries.summary, ''),
-           COALESCE((SELECT group_concat(tag, ' ') FROM tags WHERE entry_id = entries.id), '')
-    FROM entries WHERE entries.id = old.entry_id;
-END;
-
-CREATE TRIGGER tags_trigram_au AFTER UPDATE OF tag ON tags BEGIN
-    DELETE FROM entries_trigram WHERE rowid = (SELECT rowid FROM entries WHERE id = old.entry_id);
-    INSERT INTO entries_trigram(rowid, title, body, summary, tags_text)
-    SELECT entries.rowid, entries.title, entries.body, COALESCE(entries.summary, ''),
-           COALESCE((SELECT group_concat(tag, ' ') FROM tags WHERE entry_id = entries.id), '')
-    FROM entries WHERE entries.id = new.entry_id;
-END;
-
 INSERT INTO entries_trigram(rowid, title, body, summary, tags_text)
-SELECT entries.rowid,
-       entries.title,
-       entries.body,
-       COALESCE(entries.summary, ''),
-       COALESCE((SELECT group_concat(tag, ' ') FROM tags WHERE entry_id = entries.id), '')
-FROM entries;
+SELECT e.rowid,
+       r.title,
+       r.body,
+       COALESCE(r.summary, ''),
+       COALESCE((SELECT group_concat(tag, ' ')
+                   FROM entry_revision_tags
+                  WHERE entry_id = e.id AND revision = e.current_revision), '')
+  FROM entries AS e
+  JOIN entry_revisions AS r
+    ON r.entry_id = e.id AND r.revision = e.current_revision;
 
 INSERT INTO entry_search_signals(entry_id, signal_type, normalized_value)
-SELECT entry_id, 'tag', lower(trim(tag)) FROM tags WHERE length(trim(tag)) > 0;
+SELECT t.entry_id, 'tag', lower(trim(t.tag))
+  FROM entry_revision_tags AS t
+  JOIN entries AS e ON e.id = t.entry_id AND e.current_revision = t.revision
+ WHERE length(trim(t.tag)) > 0;

package/migrations/007_akinator_reasoning.sql

@@ -50,9 +50,10 @@ BEGIN
            AND a.workspace = NEW.workspace
     ) OR NOT EXISTS (
         SELECT 1
-          FROM entries AS e
+        FROM entries AS e
+        JOIN entry_revisions AS er
+          ON er.entry_id = e.id AND er.revision = NEW.entry_revision
          WHERE e.id = NEW.entry_id
-           AND e.revision = NEW.entry_revision
-           AND e.workspace IN (NEW.workspace, 'global')
+           AND er.workspace IN (NEW.workspace, 'global')
     );
 END;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@askdkc/kiokuko",
-  "version": "0.1.8",
+  "version": "0.1.10",
   "description": "Model-agnostic external memory for AI coding agents",
   "type": "module",
   "bin": {
@@ -15,6 +15,7 @@
   "files": [
     "dist/",
     "migrations/",
+    "skills/",
     "templates/",
     "README.md",
     "README.ja.md",

package/skills/kiokuko-ui-design-soul/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: kiokuko-ui-design-soul
+description: Apply HIG principles to app and web UI design, implementation, and review.
+---
+
+<!-- KIOKUKO MANAGED STANDARD SKILL: kiokuko-ui-design-soul -->
+
+# UI design soul
+
+Use this skill when designing, implementing, or reviewing application and web interfaces. Do not invoke it for backend-only work, image generation alone, or tasks unrelated to an interface.
+
+Treat Purpose, Agency, Responsibility, Familiarity, Flexibility, Simplicity, Craft, and Delight as decision principles, not as a mandate to copy Apple's visual style. Product requirements, the existing design system, accessibility standards, and safety and privacy requirements take precedence.
+
+## Establish the intent
+
+Before choosing components or styling, state or infer from evidence:
+
+- the interface's purpose;
+- the people it serves;
+- their primary task;
+- how they should feel while completing it.
+
+If any of these would materially change the design and cannot be inferred, ask one focused question. Otherwise, proceed and state the assumption.
+
+## Design the interaction contract
+
+For every relevant action, cover the states that can occur: actionable, pressed or focused, processing, success, empty, failure, offline, permission denied, destructive confirmation, and recovered. Omit only states that are genuinely impossible.
+
+- Give buttons immediate press and focus feedback.
+- Keep asynchronous feedback in the action's context: update its label or status, show progress, and prevent accidental duplicate execution.
+- Use determinate progress when completion can be measured and indeterminate progress otherwise.
+- If progress stalls, explain why and identify the next action. Offer cancellation when the operation can be interrupted safely.
+- Preserve input and completed work on failure. Provide a recovery path such as retry, undo, or back.
+- Match confirmation strength to risk. Prefer undo for safely reversible actions; require explicit confirmation when recovery is unavailable or harm is material.
+- Use motion only to clarify state, continuity, or causality. Never make animation the only carrier of information, and respect Reduced Motion.
+
+## Adapt to the platform
+
+For web interfaces, do not force an Apple-like appearance. Follow the existing design system, semantic HTML, WCAG 2.2, and the conventions of the target platform. Support keyboard, screen reader, touch, pointer, responsive layouts, and relevant system preferences.
+
+Treat Delight as the combined result of task completion, confidence, recoverability, and careful detail—not as an amount of decoration.
+
+## Deliver and verify
+
+1. Identify the primary flow and interaction states before polishing the happy path.
+2. Implement feedback and recovery beside the action that triggers them.
+3. Test with real input methods and accessibility settings, not screenshots alone.
+4. Report covered states, verified behaviors, and any known gaps.
+
+Read [references/ui-checklist.md](references/ui-checklist.md) when producing or reviewing a concrete interface, when asynchronous or destructive behavior is involved, or when accessibility validation is in scope.

package/skills/kiokuko-ui-design-soul/references/ui-checklist.md

@@ -0,0 +1,71 @@
+<!-- KIOKUKO MANAGED STANDARD SKILL: kiokuko-ui-design-soul -->
+
+# UI design and review checklist
+
+Last reviewed against the official sources: 2026-08-22.
+
+This checklist paraphrases decision principles. It does not reproduce Apple text or require Apple-styled visuals.
+
+## Eight-principle map
+
+| Principle | Practical question |
+| --- | --- |
+| Purpose | Does every important element help the user complete the primary task? |
+| Agency | Can the user understand, initiate, interrupt where safe, and recover from actions? |
+| Responsibility | Does the interface protect privacy, attention, safety, and user-created work? |
+| Familiarity | Do labels, controls, navigation, and feedback follow the target platform's conventions? |
+| Flexibility | Does the flow adapt to ability, input method, device, content size, and context? |
+| Simplicity | Is the next meaningful action clear without hiding necessary information or control? |
+| Craft | Are states, spacing, copy, timing, focus, and edge cases implemented consistently? |
+| Delight | Does successful, calm, recoverable use feel better because the details work together? |
+
+## State coverage
+
+For each primary action, verify the applicable states:
+
+- **Actionable:** the label predicts the result; enabled and disabled states are distinguishable without color alone.
+- **Pressed and focused:** feedback is immediate; keyboard focus is visible; focus order follows the task.
+- **Processing:** status remains near the initiating control; duplicate submission is prevented without trapping the user.
+- **Progress:** measurable work uses a determinate value; unmeasurable work uses an indeterminate indicator and an accessible status message.
+- **Long or stalled work:** expectations are updated; a reason and next step are shown; cancellation is available only when it is safe and real.
+- **Success:** completion is perceivable visually and programmatically; the interface moves focus only when that helps the next task.
+- **Empty:** the state explains what is absent and offers a relevant next action rather than presenting a dead end.
+- **Failure:** input and completed work are retained; the message says what happened in actionable language; retry, undo, or back is available where meaningful.
+- **Offline:** unavailable behavior is explicit; queued or local work is not implied unless it is actually preserved.
+- **Permission denied:** explain the missing capability and provide a safe route to settings, an alternative, or back.
+- **Destructive:** communicate scope and consequence; prefer undo for reversible actions and use explicit confirmation for material irreversible harm.
+- **Recovered:** clear stale errors and busy states; restore a coherent focus position; avoid re-running the action unexpectedly.
+
+## Accessibility and adaptation
+
+- Use semantic HTML or native controls before recreating their behavior.
+- Verify the full primary flow with keyboard only, including visible focus and escape from overlays.
+- Verify names, roles, values, errors, progress, and status announcements with a screen reader.
+- Test touch, pointer, keyboard, and relevant alternate input; do not require hover, precise pointing, or a single gesture.
+- Test narrow and wide layouts, zoom or text resizing, longer translated copy, and dynamic content.
+- Do not encode meaning with color, motion, shape, or sound alone.
+- Respect Reduced Motion and provide equivalent state information without animation.
+- Keep time limits adjustable or avoid them unless the task itself requires one.
+- On the web, apply the existing design system and WCAG 2.2; do not imitate iOS merely because these principles originated in Apple HIG.
+
+## Async-action spot check
+
+For a save, upload, generation, import, or other asynchronous action, confirm:
+
+1. Press or focus feedback is immediate.
+2. The busy state names the ongoing action and blocks accidental duplicates.
+3. Progress type matches what the system can measure.
+4. Cancellation has defined semantics and leaves data consistent.
+5. Success and failure are announced in the same task context.
+6. A failure keeps user input and provides a tested recovery path.
+
+## Official sources
+
+- Apple Human Interface Guidelines — Design principles: https://developer.apple.com/design/human-interface-guidelines/design-principles
+- Apple Human Interface Guidelines — Buttons: https://developer.apple.com/design/human-interface-guidelines/buttons
+- Apple Human Interface Guidelines — Loading: https://developer.apple.com/design/human-interface-guidelines/loading
+- Apple Human Interface Guidelines — Progress indicators: https://developer.apple.com/design/human-interface-guidelines/progress-indicators
+- Apple Human Interface Guidelines — Feedback: https://developer.apple.com/design/human-interface-guidelines/feedback
+- Apple Human Interface Guidelines — Motion: https://developer.apple.com/design/human-interface-guidelines/motion
+- Apple Human Interface Guidelines — Accessibility: https://developer.apple.com/design/human-interface-guidelines/accessibility
+- W3C Web Content Accessibility Guidelines 2.2: https://www.w3.org/TR/WCAG22/