Wails v2 デスクトップ配布ビルドを実地検証する

[terisuke]

目的

Note Maker を、非開発者がインストールして起動できる Wails v2 デスクトップアプリとして配布する。Tier 1 launcher と同じデータディレクトリを使い、既存の Go handlers と static/ UI を再利用する。

現在の状態

ソース側の準備は develop に入っている。

• Wails v2 は cmd/desktop/go.mod で pin 済み
• make desktop-build は macOS arm64 で成功済み
• desktop-release.yml に dry-run / release / checksum / signing gate がある
• scripts/release-readiness-check.sh で workflow visibility と signing secret 状態を記録できる
• 詳細手順は docs/handoffs/open-issues-field-validation-2026-05-04.md と docs/operations/desktop-release-runbook.md にある

現在の外部 blocker:

• repository default branch は main
• 新しい workflow は develop にあり、main に到達するまで manual dispatch できない
• 2026-05-04 時点で visible secrets は FIREBASE_TOKEN, GCP_SA_KEY, GEMINI_API_KEY のみ
• Apple / Windows signing secret は未設定

ローカル確認

git checkout develop
git pull --ff-only origin develop
(cd cmd/desktop && go test ./... && go test -tags wails ./...)
make desktop-check
make desktop-build
RUN_MULTI_ARCH_BUILD=0 RUN_TAILSCALE_STARTUP=0 ./scripts/release-readiness-check.sh
git diff --check

build/ は検証後に git 管理へ入れない。artifact として残す場合は GitHub Actions artifact か別保存にする。

GitHub Actions dry-run

workflow files が main に到達してから実行する。

gh workflow run desktop-release.yml --repo terisuke/note_maker --ref main \
  -f dry_run=1 \
  -f release=0

確認:

gh run list --repo terisuke/note_maker --workflow 'Desktop Release' --limit 5
gh run view --repo terisuke/note_maker <run-id> --log

記録すること:

• macOS job の artifact 名
• Windows job の artifact 名
• Linux job の artifact 名
• 各 .sha256
• dry-run command log

署名つき release

release=1 の前に以下を設定する。

• APPLE_CERTIFICATE
• APPLE_CERTIFICATE_PASSWORD
• APPLE_TEAM_ID
• APP_STORE_CONNECT_KEY_ID
• APP_STORE_CONNECT_ISSUER_ID
• APP_STORE_CONNECT_KEY
• WINDOWS_CERTIFICATE
• WINDOWS_CERTIFICATE_PASSWORD

実行:

gh workflow run desktop-release.yml --repo terisuke/note_maker --ref main \
  -f dry_run=0 \
  -f release=1

実機 smoke

macOS / Windows / Linux それぞれで確認する。

• アプリが起動する
• 既存 UI が表示される
• 初回起動で Tier 1 と同じデータディレクトリを作る
• 既存 Tier 1 データを migration なしで読める
• Open Data Folder が動く
• LLM Diagnostics が開ける
• アプリ自体は internet なしで起動する
• 終了が clean に完了する

Close 条件

次をすべて満たしたら close する。

• GitHub Actions の dry-run workflow で macOS / Windows / Linux artifact と checksum が生成される
• macOS build が Apple Developer ID で署名・notarize される
• Windows build が署名される
• Linux artifact と checksum が取得できる
• 3 platform の実機 smoke が pass する
• app startup が internet 必須ではない
• Wails v2 pin が維持されている

Close してはいけない条件

• workflow が main に無く dispatch できない
• dry-run artifact しかなく署名・notarization が未実施
• macOS だけ、または開発機だけの検証で終わっている
• Windows / Linux の実機 smoke が未実施

[terisuke]

2026-05-04 progress: Wails desktop scaffold

Branch: feat/d2-3-grid-scaffold

Implemented:

• cmd/desktop scaffold that reuses the existing internal/handlers HTTP handlers and existing static/ asset tree.
• Dependency-free desktop preview entrypoint for local route/asset validation.
• Wails-tagged entrypoint using Wails v2 AssetServer.Handler once the Wails module is added.
• wails.json with frontend:dir set to static and no npm/Vite build step.
• Makefile desktop targets: desktop-preview, desktop-check, desktop-dev, desktop-build.

Validation:

• go test ./cmd/desktop passed.
• go test ./... passed.
• python3 -m json.tool wails.json passed.
• git diff --check passed.
• make desktop-check fails as expected in this scaffold cut because the Wails CLI is not installed and github.com/wailsapp/wails/v2 is not yet pinned in go.mod.

Validation artifact:

• docs/validation/issue-92-wails-desktop-scaffold-2026-05-04.md

Not closing this issue yet. Remaining acceptance includes Wails v2 dependency pinning, wails dev, wails build, first-run data-dir validation, signing/notarization, release workflow, and platform smoke tests.

[terisuke]

PR #98 advances the Wails desktop packaging track but this issue remains open.\n\nImplemented locally:\n- Wails v2 pinned in cmd/desktop/go.mod\n- embedded desktop frontend assets\n- launcher-compatible first-run data/config/workflow bootstrap\n- native menu actions for opening the data folder and LLM diagnostics\n- pinned Makefile desktop targets\n- release workflow dry-run artifacts/checksum path\n\nValidation run locally:\n- go test ./cmd/desktop\n- (cd cmd/desktop && go test ./... && go test -tags wails ./...)\n- make desktop-check\n- make desktop-build on macOS darwin/arm64\n- Wails dry-run build command\n\nNot closing yet: remaining acceptance still needs real platform distribution evidence, especially signing/notarization, Windows signing/MSI or equivalent packaging, Linux artifact verification, release workflow evidence, and platform smoke validation.

[terisuke]

PR follow-up branch codex/close-runtime-desktop-deployment removes the remaining source-tree release blockers for #92, but I am not closing the issue because external field validation is still required by the acceptance criteria.

Implemented:

• hardened desktop-release.yml dry-run/checksum behavior across macOS, Linux, and Windows shells
• added scripts/release-readiness-check.sh to collect release evidence and default-branch workflow visibility
• documented the default-branch promotion condition, dry-run release path, and signing secret gates
• recorded validation in docs/validation/issue-92-93-release-deployment-close-blockers-2026-05-04.md

Validation passed:

(cd cmd/desktop && go test ./... && go test -tags wails ./...)
RUN_MULTI_ARCH_BUILD=0 RUN_TAILSCALE_STARTUP=1 ./scripts/release-readiness-check.sh
go run github.com/rhysd/actionlint/cmd/actionlint@latest .github/workflows/desktop-release.yml .github/workflows/docker-publish.yml

Observed external blockers:

• repo default branch is still main, and the default-branch workflow list only shows CI and Dependency Graph
• Apple/Windows signing secret names are not configured; visible secrets were FIREBASE_TOKEN, GCP_SA_KEY, and GEMINI_API_KEY

Remaining field validation only: get the workflow files onto main, run Desktop Release dry_run=1, configure signing/notarization secrets, and smoke the produced macOS/Windows/Linux artifacts.