Skip to content

Chore/release screenshot skill#9

Open
forcingfx wants to merge 4 commits into
mainfrom
chore/release-screenshot-skill
Open

Chore/release screenshot skill#9
forcingfx wants to merge 4 commits into
mainfrom
chore/release-screenshot-skill

Conversation

@forcingfx

Copy link
Copy Markdown
Owner

No description provided.

github.sudoku and others added 4 commits May 17, 2026 10:54
…L folders

Adds the 0.9.0 release entry to releases.mjs and rebuilds the Atom feed
and accordion. Captures the eight-PR consolidation arc shipped in the
sister repo this week:

  Added
    - Log in wizard for license holders on a fresh device (license token
      + optional sync passphrase, surfaced alongside Subscribe so paying
      users don't re-purchase)
    - Five Settings tabs reachable from a single sidebar button
    - OPML folder structure preserved on import and export
    - Reading and Help tabs inside Settings

  Changed
    - One in-app upgrade chokepoint (every Upgrade button opens Account)
    - Floating tier pill removed from sidebar
    - Simpler If-you-lose-access card (drops the recovery-sheet download)
    - Sidebar default widened 14rem -> 18rem
    - Mobile breakpoint raised 768px -> 1024px

  Fixed
    - Sidebar visibly changing width on navigation (single stable
      panel-group id across routes)
    - Canvas going blank between 530-767px window widths
    - Sync passphrase reveal overflowing the dialog
    - Paid users orphaning Stripe subscription via Delete all data

Also two copy fixes in index.html:
  - OPML feature now mentions folder preservation (matches the 0.9.0 add)
  - Sync feature copy: "Subscribe and save the four-word passphrase the
    app generates for you" — was "Subscribe and pick a four-word
    passphrase" which misrepresented the flow (the app generates it; the
    user doesn't pick).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…atured article

Adds a "landing" scene to take-screenshot.mjs that seeds the app's encrypted
store directly (4 folders, 20 feeds, a featured article with a hero image)
so the marketing screenshot looks like a real reading session.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Dismiss the "feeds stored locally" sidebar warning in the seed step so
  marketing screenshots come out clean.
- Add .claude/skills/release-screenshot/SKILL.md so Claude can find and
  run the landing-scene capture on demand during /release.
- Refresh screenshot.png with the warning suppressed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Add the missing operational reality that left a self-hoster bouncing
through three feedback issues (forcingfx/feedzero#88, #97, #98):

- HTTPS / secure-context warning at the top: the Web Crypto API
  refuses to run without a secure context, and plain http://<lan-ip>
  is the most common self-host mistake. Now called out before any
  setup step.
- Minimal Caddyfile that solves both TLS and reverse-proxy in 3 lines.
- Troubleshooting section: the 5 problems self-hosters actually hit
  (secure-context, feed-fetch failures vs hosted, vault-not-found,
  cross-device sync origin mismatch, lingering Subscribe UI).
- Master-switch documentation: VITE_SELF_HOSTED=1 + SELF_HOSTED=1
  is sufficient. VITE_PAID_TIER_VISIBLE / LAUNCH_PAID_TIER are now
  forced off by the master switch.
- FEED_USER_AGENT escape hatch for operators who want to identify
  their instance honestly with contact info.
- "What you give up vs the hosted deployment": honest list of what
  self-host lacks (upstream rate-limit smoothing, IP reputation,
  automatic TLS, managed backups, stats popular-feeds widget).

Quick Start updated to reflect the single master switch.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented May 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
feedzero-landing Ready Ready Preview, Comment May 17, 2026 0:44am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant