altair823-org/inkling
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 18 Wiki Activity

chore/post-slice-followups #1

Merged
altair823 merged 6 commits from chore/post-slice-followups into main 2026-04-25 08:29:18 +00:00
Conversation 0 Commits 6 Files Changed 7 +636 -7
altair823 commented 2026-04-25 08:29:07 +00:00
Owner
Copy Link
No description provided.
altair823 added 6 commits 2026-04-25 08:29:08 +00:00
fix(e2e): rebuild better-sqlite3 per ABI + select inbox window by title c7e9463adb 
- Vitest needs the node-ABI prebuilt sqlite binary; Electron 41 needs ABI 145.
  Add `rebuild:node` / `rebuild:electron` scripts and wire them as
  pre-hooks for `test`, `test:e2e`, `start`, `dev`, `test:integration`.
- Smoke test was racing on `firstWindow()`, which non-deterministically
  returned the quickcapture window. Strip ELECTRON_RUN_AS_NODE from the
  launch env, wait for both windows to register, then pick the inbox by
  title and assert the heading via `getByRole`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
docs: add Korean README + 2-week dogfood strategy f9b0e67ec5 
- README.md: Korean project intro, prereqs (Volta + VS Build Tools 2022 +
  LAN Ollama), npm scripts, ABI/ELECTRON_RUN_AS_NODE gotchas, slice
  invariants, doc map.
- docs/superpowers/strategy/dogfood-strategy.md: 2-week self-dogfood plan
  to satisfy slice exit condition (spec §1.3). Covers Day 0 checklist,
  daily triggers tied to strategy §3 if-then implementation intentions,
  weekly continuity tracking, friction-vs-backlog triage rule, and a
  Pass/Conditional/Fail verdict at Day 14.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
feat(diag): log resolved Ollama endpoint + surface health reason in banner df56661f4f 
When the OllamaBanner appears, it was generic enough that the user
couldn't tell whether the env var was missing, the LAN host was
unreachable, the model was uninstalled, or DNS was failing. Log the
resolved endpoint at startup with a `fromEnv` flag so we can confirm
INKLING_OLLAMA_ENDPOINT was actually read, and render the underlying
health-check reason as a small subtitle under the banner copy.

The user-facing primary message still avoids the forbidden tone words
("실패"/"끊김"/"연속 실패"); the diagnostic line is technical and only
appears when status.reason is set.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
docs(spec): stub due-date extraction spec for post-slice work c5e5975a12 
Captures the design skeleton, hypotheses, and open questions for the
hybrid (rule-based first → AI fallback) Korean date-phrase extractor.
Schema impact, prompt change, UX copy, and library tradeoffs are
sketched but deferred — formalization waits for slice v0.4 dogfood
Pass and the H1 (time-phrase frequency ≥ 30%) check in week-1 retro.

Cross-link added to dogfood-strategy daily-metric table so the H1
data is collected during dogfood, and to README docs map.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
docs: decouple due-date spec from dogfood strategy doc 1fb6670e67 
The due-date extraction work originated as feedback during dogfood, but
the dogfood strategy doc itself should stay feature-agnostic — it's the
generic operating manual for the 2-week dogfood, not a feedback log.

- Remove the "시간 표현 포함 노트 수" row from dogfood-strategy §3.1.
- Rephrase the due-date spec stub so H1 / §7 / §9 reference the spec's
  own sample-collection plan instead of relying on the dogfood retro.
- Spec is now framed as "independent of slice exit"; entry timing is a
  separate decision once an accumulated sample meets H1.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
docs(spec): convert due-date stub into dogfood-feedback collection fac019e8a0 
Reframe the file as a living register for in-flight dogfood feedback
rather than a single-feature stub. Each item carries a status label
(raw / drafting / ready-for-spec / promoted / rejected) and a fixed
six-slot template (관찰 / 제안 방향 / 결정 대기 / 가설·측정 / 범위 /
영향). Items graduate to their own spec file once mature; the entry
here then collapses to a one-line link.

- F1: Due-date 추출 (drafting) — content from the previous stub
  normalized to the new template.
- F2: 태그 클릭 = 즉시 삭제 + undo 부재 (raw) — NoteCard.tsx:110
  binds chip onClick to removeTag, no confirm or undo, and there is
  no "filter by tag" affordance to match the user's mental model.
  Direction: split click=filter, ✕-icon=remove with 5s undo toast.

README docs map updated to point at the new path.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
altair823 merged commit 8eeba97a3a into main 2026-04-25 08:29:18 +00:00
altair823 deleted branch chore/post-slice-followups 2026-04-25 08:29:21 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
altair823 claude-reviewer-01
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: altair823-org/inkling#1
Delete Branch "chore/post-slice-followups"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?