[Flagship] Document the local flag store for wrangler dev

[akshitsinha]

Summary

Documents the local flag store that Flagship bindings now use during wrangler dev.

The Flagship configuration page currently states the opposite of the new behaviour:

Local Workers use the live Flagship app configured by app_id. There is no local flag store.

Bindings now resolve against a local, persisted store by default, so wrangler dev works offline and local changes no longer touch production flags. Flags fall back to the default passed at the call site until the store is populated, so the pull step needs to be discoverable.

Changes:

• Flagship configuration — replaced the "Local development" section with the local store workflow: wrangler flagship flags pull, --local flag commands, remote: true, and Local Explorer.
• Flagship get started — added a short "Test locally" step before deploy.
• Flagship Wrangler commands — added a "Local flag store" section, and scoped the authentication note to commands that target the remote app.
• Wrangler flagship command page — added a --local note, matching the existing Workflows pattern.
• Wrangler configuration — added the flagship binding (binding, app_id, remote) to the bindings reference and the non-inheritable keys list.
• Local development — added Flagship to the Local Explorer supported bindings table, the "Adding local data" page, and the bindings-per-environment tables.
• Changelog — new entry for the local flag store.

Implementation PR: cloudflare/workers-sdk#15268

Documentation checklist

• Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
• The change adheres to the documentation style guide.

[cloudflare-docs-bot]

Review

⚠️ 2 warnings found in commit e6d2a45.

👉 Fix in your agent 👈

Fix the following review findings in PR #32879 (https://github.com/cloudflare/cloudflare-docs/pull/32879).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Code Review

### Warnings (1)

#### CR-ee227d7b6682 · Undefined technical terminology
- **File:** `src/content/docs/flagship/configuration.mdx` line 104
- **Issue:** `pull` also seeds the account tag used for [percentage rollout](/flagship/targeting/percentage-rollouts/) bucketing" introduces "account tag," a term that is never defined elsewhere in the Flagship documentation and is not used by the linked percentage-rollouts page, which explains bucketing via attributes such as `targetingKey` or `userId`.
- **Fix:** Reword the sentence using documented concepts or remove the implementation detail. For example, say that `pull` copies the account-level bucketing seed so local percentage-rollout assignments match the remote app, after confirming the exact user-facing behavior with the product team.

---

## Style Guide Review

### Warnings (1)

#### SG-1708d7618285 · Do not bold program or tool names; use monospace
- **File:** `src/content/changelog/flagship/2026-08-28-local-flag-store.mdx` line 9
- **Issue:** Line adds `**[Wrangler](/workers/wrangler/)**`, bolding the Wrangler tool name
- **Fix:** Remove the bold or refer to Wrangler in plain text/link without bold formatting

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (1)

File

Issue

flagship/configuration.mdx line 104

Undefined technical terminology — pull also seeds the account tag used for percentage rollout bucketing" introduces "account tag," a term that is never defined elsewhere in the Flagship documentation and is not used by the linked percentage-rollouts page, which explains bucketing via attributes such as targetingKey or userId. Fix: Reword the sentence using documented concepts or remove the implementation detail. For example, say that pull copies the account-level bucketing seed so local percentage-rollout assignments match the remote app, after confirming the exact user-facing behavior with the product team.

Conventions

_{No convention issues found.}

Style Guide Review

Warnings (1)

File	Issue
changelog/flagship/2026-08-28-local-flag-store.mdx line 9	Do not bold program or tool names; use monospace — Line adds \*\*[Wrangler](/workers/wrangler/)\*\*, bolding the Wrangler tool name Fix: Remove the bold or refer to Wrangler in plain text/link without bold formatting

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.