new koins logo + publish permission rule

2026-08-02 12:41:42 +08:00
parent 1cccdc70e0
commit 9df8ce1867
11 changed files with 1 additions and 0 deletions
@@ -4,4 +4,5 @@
 - Never manually edit `.router/router.ts` — sv-router auto-generates it from the filesystem. Just create the route file in the correct filesystem location.
 - Only commit when explicitly told to do so. When asked to commit, always write a single simple line commit message.
 - When asked to publish, always rebuild the DMG first (`bun run build:stable` from `apps/desktop`), wait for notarization to complete, verify with `xcrun stapler validate`, then publish the fresh DMG. Never publish a stale build.
 - Never publish without explicit permission. Before any publish action — running `bun run build:stable`, `gh release upload`, updating the Homebrew cask, or pushing the tap repo — describe the intended action (what will be built, what SHA, which release) and wait for a clear "yes" / "go" from the user. This rule has no exceptions: even if the user has just said "publish", treat that as a request to prepare and ask, not an automatic go-ahead. Always confirm the specific publish step before executing.
 - At the end of every response, always surface a "Pending from you" section listing anything you need from the user (decisions, permissions, credentials, confirming a plan, etc.). If nothing is pending, say "Nothing pending."