docs: add suggested next steps as tasks

[matta]

Added docs/pebble/decide-the-storage-merge-strategy.md and docs/pebble/pick-the-mvp-command-surface-for-daily-use.md to track suggested next steps using the Pebble CLI.

---

PR created automatically by Jules for task 7845926241541802105 started by @matta

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces new documentation to outline critical next steps for the Pebble CLI project. These documents serve as task trackers, guiding future development efforts by defining key decisions and implementations required for the project's progression, specifically focusing on storage strategy and the MVP command surface.

Highlights

• New Documentation Files: Two new Markdown files were added to the docs/pebble directory to track suggested next steps for the Pebble CLI project.

Changelog

• docs/pebble/decide-the-storage-merge-strategy.md
  • Added a new documentation file outlining the decision process for storage/merge strategy.
• docs/pebble/pick-the-mvp-command-surface-for-daily-use.md
  • Added a new documentation file detailing the selection of the MVP command surface for daily use.

Activity

• The pull request was automatically created by Jules for task 7845926241541802105 initiated by @matta.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds two new task files to track suggested next steps for the Pebble project. My review focuses on ensuring the new tasks are clear and consistent with the project's existing documentation, particularly the RFCs and CLI contract. I've identified a couple of areas where the task descriptions could be clarified to better reflect the decisions already made in the project's specifications, which should help avoid confusion for anyone picking up these tasks.

[gemini-code-assist]

The title and body of this task suggest a decision about the storage strategy is yet to be made. However, docs/rfcs/001-reimagining-pebble.md already specifies that the storage strategy is "per-issue Markdown files". This could cause confusion. If this task is about defining a merge strategy for concurrent edits to a single file, the title and body should be updated to reflect this, rather than relitigating the storage format decision.

Suggested change

	title: Decide the storage/merge strategy
	status: todo
	created_at: 2026-03-14T05:09:13.767464617+00:00
	---
	Decide the storage/merge strategy (CRDT op-log vs per-issue files vs JSONL snapshot) so the deterministic merge work can start.
	title: Define the merge strategy for concurrent edits
	status: todo
	created_at: 2026-03-14T05:09:13.767464617+00:00
	---
	Define the merge strategy for concurrent edits to a single task file. The storage format is decided (per-issue files), but this task is to determine how to handle concurrent edits to the same file (e.g., CRDTs, op-log) so that deterministic merge work can start.

[gemini-code-assist]

The title and body of this task suggest that the MVP command surface still needs to be chosen. However, docs/cli-contract.md and docs/rfcs/001-reimagining-pebble.md already provide a detailed specification for the CLI, including search, update, list with filters, and the --json and help-json flags. To avoid confusion, the task should be rephrased to focus on the implementation of the already-defined command surface.

Suggested change

	title: Pick the MVP command surface for daily use
	status: todo
	created_at: 2026-03-14T05:09:18.735076984+00:00
	---
	Pick the MVP command surface for daily use (search, update, list filters) and implement --json + --help-json across commands.
	title: Implement the MVP command surface for daily use
	status: todo
	created_at: 2026-03-14T05:09:18.735076984+00:00
	---
	Implement the MVP command surface as defined in `docs/cli-contract.md`, focusing on `search`, `update`, `list` with filters, and ensuring --json and --help-json are available across all relevant commands.