Files
yellowjacket/.gitignore
T
yonluandClaude Opus 5 cad3d1339b fix(packaging): put the release recipes on v3's build
Neither packaging/arch/PKGBUILD nor the Homebrew formula had been run
since Phase 1, and both were still calling v2's CLI: `wails3 build`
takes -tags, -obfuscated and -garbleargs and nothing else, so
`-clean -trimpath -ldflags` fails at the flag parser. Both also
installed from build/bin/, which is v2's output path — v3 writes to
bin/, and build/ is tracked build assets now.

Three more things the tree needs that neither recipe had. The tasks
invoke `wails3` by bare name, so scripts/toolbin has to be on PATH or
the build dies at its first sub-task. `wails3 build` has no -ldflags at
all, and build:native computes BUILD_FLAGS in its own vars: so a CLI
variable cannot override it — LDFLAGS_EXTRA is appended inside the
production -ldflags string instead, on linux and darwin alike, empty by
default so make build-dev/build-prod are unchanged. And bundling is a
separate step from building: `task build` produces a bare binary on
both platforms, so the formula's macOS path runs `task package`.

The build assets were the scaffold's, not this app's. Info.plist named
CFBundleExecutable `yjref` and com.example.yjref, nfpm packaged
./bin/yjref, the .desktop template said "A yjref application" — an .app
built from that plist would not have launched. They generate from
build/config.yml, whose info block had never been filled from
wails.json either; `wails3 task common:update:build-assets` is the fix.
nfpm's homepage and license are not derived from it and are set by
hand, which is noted in place, and the refresh regenerates build/ios
and build/android, which this repo does not carry.

arch-package.yml's pacman list moves to webkitgtk-6.0/gtk4 to match the
PKGBUILD's depends(): makepkg installs nothing itself, so a mismatch
fails at link time rather than at check time.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UDCbcCZQepnpSQYJ6SxxZm
2026-08-14 23:09:24 -04:00

73 lines
1.7 KiB
Plaintext

frontend/dist
node_modules
build/bin/
test_data
test.db
# ── Agent development harness (plan 005) ──
# playwright-cli scratch output (snapshots, console logs, screenshots)
.playwright-cli/
# headless app process state: pid file + captured stdout
.dev/
# Playwright spec output: traces, screenshots and videos of failures
e2e/test-results/
e2e/playwright-report/
# Vitest browser-mode scratch (screenshot diffs, failure captures).
# The committed baselines under frontend/test/**/__screenshots__ stay.
frontend/.vitest-attachments/
.aider*
lefthook-local.yml
# Profiling artifacts
trace-*.out
*.pprof
# ── Legacy GSD planning snapshot (replaced by .planning/) ──
# Kept on disk for reference only; safe to delete once nothing relies on it.
.gsd
gsd-session-*.html
.DS_Store
Thumbs.db
*.swp
*.swo
*~
.idea/
.vscode/
*.code-workspace
.env
.env.*
!.env.example
node_modules/
.next/
dist/
# build/ holds v3 build assets and is tracked; only its output is not.
__pycache__/
*.pyc
.venv/
venv/
target/
vendor/
*.log
coverage/
.cache/
tmp/
bin/
# Task's checksum cache, written by every `wails3 task` run.
.task/
# Generated by build/linux/Taskfile.yml's generate:dotdesktop from
# build/config.yml on every build, and consumed by the deb/rpm/AppImage
# packaging tasks that depend on it. A derived file with one source.
build/linux/yellowjacket.desktop
# `wails3 task common:update:build-assets` regenerates the mobile trees
# whether or not anything asks for them. This is a desktop player and
# cannot target iOS/Android, so their includes: entries are dropped from
# Taskfile.yml and the trees themselves are not carried — ignored rather
# than deleted-and-rediscovered on every asset refresh.
build/ios/
build/android/