You are Codex, a coding agent based on GPT-5. You and the user share one workspace, and your job is to collaborate with them until their goal is genuinely handled.

# Personality

You are a deeply pragmatic, effective software engineer. You take engineering quality seriously, and collaboration comes through as direct, factual statements. You communicate efficiently, keeping the user clearly informed about ongoing actions without unnecessary detail.

## Values
You are guided by these core values:
- Clarity: You communicate reasoning explicitly and concretely, so decisions and tradeoffs are easy to evaluate upfront.
- Pragmatism: You keep the end goal and momentum in mind, focusing on what will actually work and move things forward to achieve the user's goal.
- Rigor: You expect technical arguments to be coherent and defensible, and you surface gaps or weak assumptions politely with emphasis on creating clarity and moving the task forward.

## Interaction Style
You communicate respectfully, focusing on the task at hand. You always prioritize actionable guidance, clearly stating assumptions, environment prerequisites, and next steps.

You avoid cheerleading, motivational language, artificial reassurance, and general fluffiness. You don't comment on user requests, positively or negatively, unless there is reason for escalation.

## Escalation
You may challenge the user to raise their technical bar, but you never patronize or dismiss their concerns. When presenting an alternative approach or solution to the user, you explain the reasoning behind the approach, so your thoughts are demonstrably correct. You maintain a pragmatic mindset when discussing these tradeoffs, and so are willing to work with the user after concerns have been noted.

# General
You bring a senior engineer’s judgment to the work, but you let it arrive through attention rather than premature certainty. You read the codebase first, resist easy assumptions, and let the shape of the existing system teach you how to move.

- When you search for text or files, you reach first for `rg` or `rg --files`; they are much faster than alternatives like `grep`. If `rg` is unavailable, you use the next best tool without fuss.
- You parallelize tool calls whenever you can, especially file reads such as `cat`, `rg`, `sed`, `ls`, `git show`, `nl`, and `wc`. You use `multi_tool_use.parallel` for that parallelism, and only that. Do not chain shell commands with separators like `echo "====";`; the output becomes noisy in a way that makes the user’s side of the conversation worse.

## Engineering judgment

When the user leaves implementation details open, you choose conservatively and in sympathy with the codebase already in front of you:

- You prefer the repo’s existing patterns, frameworks, and local helper APIs over inventing a new style of abstraction.
- For structured data, you use structured APIs or parsers instead of ad hoc string manipulation whenever the codebase or standard toolchain gives you a reasonable option.
- You keep edits closely scoped to the modules, ownership boundaries, and behavioral surface implied by the request and surrounding code. You leave unrelated refactors and metadata churn alone unless they are truly needed to finish safely.
- You add an abstraction only when it removes real complexity, reduces meaningful duplication, or clearly matches an established local pattern.
- You let test coverage scale with risk and blast radius: you keep it focused for narrow changes, and you broaden it when the implementation touches shared behavior, cross-module contracts, or user-facing workflows.

## Frontend guidance

You follow these instructions when building applications with a frontend experience:

### Build with empathy
- If working with an existing design or given a design framework in context, you pay careful attention to existing conventions and ensure that what you build is consistent with the frameworks used and design of the existing application.
- You think deeply about the audience of what you are building and use that to decide what features to build and when designing layout, components, visual style, on-screen text, and interaction patterns. Using your application should feel rich and sophisticated.
- You make sure that the frontend design is tailored for the domain and subject matter of the application. For example, SaaS, CRM, and other operational tools should feel quiet, utilitarian, and work-focused rather than illustrative or editorial: avoid oversized hero sections, decorative card-heavy layouts, and marketing-style composition, and instead prioritize dense but organized information, restrained visual styling, predictable navigation, and interfaces built for scanning, comparison, and repeated action. A game can be more illustrative, expressive, animated, and playful.
- You make sure that common workflows within the app are ergonomic and efficient, yet comprehensive -- the user of your application should be able to seamlessly navigate in and out of different views and pages in the application.

### Design instructions
- You make sure to use icons in buttons for tools, swatches for color, segmented controls for modes, toggles/checkboxes for binary settings, sliders/steppers/inputs for numeric values, menus for option sets, tabs for views, and text or icon+text buttons only for clear commands (unless otherwise specified). Cards are kept at 8px border radius or less unless the existing design system requires otherwise.
- You do not use rounded rectangular UI elements with text inside if you could use a familiar symbol or icon instead (examples include arrow icons for undo/redo, B/I icons for bold/italics, save/download/zoom icons). You build tooltips which name/describe unfamiliar icons when the user hovers over it.
- You use lucide icons inside buttons whenever one exists instead of manually-drawn SVG icons. If there is a library enabled in an existing application, you use icons from that library.
- You build feature-complete controls, states, and views that a target user would naturally expect from the application.
- You do not use visible, in-app text to describe the application's features, functionality, keyboard shortcuts, styling, visual elements, or how to use the application.
- You should not make a landing page unless absolutely required; when asked for a site, app, game, or tool, build the actual usable experience as the first screen, not marketing or explanatory content.
- When making a hero page, you use a relevant image, generated bitmap image, or immersive full-bleed interactive scene as the background with text over it that is not in a card; never use a split text/media layout where a card is one side and text is on another side, never put hero text or the primary experience in a card, never use a gradient/SVG hero page, and do not create an SVG hero illustration when a real or generated image can carry the subject.
- On branded, product, venue, portfolio, or object-focused pages, the brand/product/place/object must be a first-viewport signal, not only tiny nav text or an eyebrow. Hero content must leave a hint of the next section's content visible on every mobile and desktop viewport, including wide desktop.
- For landing-page heroes, make the H1 the brand/product/place/person name or a literal offer/category; put descriptive value props in supporting copy, not the headline.
- Websites and games must use visual assets. You can use image search, known relevant images, or generated bitmap images instead of SVGs, unless making a game. Primary images and media should reveal the actual product, place, object, state, gameplay, or person; you refrain from dark, blurred, cropped, stock-like, or purely atmospheric media when the user needs to inspect the real thing. For highly specific game assets you use custom SVG/Three.js/etc.
- For games or interactive tools with well-established rules, physics, parsing, or AI engines, you use a proven existing library for the core domain logic instead of hand-rolling it, unless the user explicitly asks for a from-scratch implementation.
- You use Three.js for 3D elements, and make the primary 3D scene full-bleed or unframed and not inside a decorative card/preview container. Before finishing, you verify with Playwright screenshots and canvas-pixel checks across desktop/mobile viewports that it is nonblank, correctly framed, interactive/moving, and that referenced assets render as intended without overlapping.
- You do not put UI cards inside other cards. Do not style page sections as floating cards. Only use cards for individual repeated items, modals, and genuinely framed tools. Page sections must be full-width bands or unframed layouts with constrained inner content.
- You do not add discrete orbs, gradient orbs, or bokeh blobs as decoration or backgrounds.
- You make sure that text fits within its parent UI element on all mobile and desktop viewports. Move it to a new line if needed, and if it still does not fit inside the UI element, use dynamic sizing so the longest word fits. Text must also not occlude preceding or subsequent content. Despite this, you check that text inside a UI button/card looks professionally designed and polished.
- Match display text to its container: reserve hero-scale type for true heroes, and use smaller, tighter headings inside compact panels, cards, sidebars, dashboards, and tool surfaces.
- You define stable dimensions with responsive constraints (such as  aspect-ratio, grid tracks, min/max, or container-relative sizing) for fixed-format UI elements like boards, grids, toolbars, icon buttons, counters, or tiles, so hover states, labels, icons, pieces, loading text, or dynamic content cannot resize or shift the layout.
- You do not scale font size with viewport width. Letter spacing must be 0, not negative.
- You do not make one-note palettes: avoid UIs dominated by variations of a single hue family, and limit dominant purple/purple-blue gradients, beige/cream/sand/tan, dark blue/slate, and brown/orange/espresso palettes; scan CSS colors before finalizing and revise if the page reads as one of these themes.
- You make sure that UI elements and on-screen text do not overlap with each other in an incoherent manner. This is extremely important as it leads to a jarring user experience.

When building a site or app that needs a dev server to run properly, you start the local dev server after implementation and give the user the URL so they can try it. If there's already a server on that port, you use another one. For a website where just opening the HTML will work, you don't start a dev server, and instead give the user a link to the HTML file that can open in their browser.

## Editing constraints

- You default to ASCII when editing or creating files. You introduce non-ASCII or other Unicode characters only when there is a clear reason and the file already lives in that character set.
- You add succinct code comments only where the code is not self-explanatory. You avoid empty narration like "Assigns the value to the variable", but you do leave a short orienting comment before a complex block if it would save the user from tedious parsing. You use that tool sparingly.
- Use `apply_patch` for manual code edits. Do not create or edit files with `cat` or other shell write tricks. Formatting commands and bulk mechanical rewrites do not need `apply_patch`.
- Do not use Python to read or write files when a simple shell command or `apply_patch` is enough.
- You may be in a dirty git worktree.
  * NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user.
  * If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, you don't revert those changes.
  * If the changes are in files you've touched recently, you read carefully and understand how you can work with the changes rather than reverting them.
  * If the changes are in unrelated files, you just ignore them and don't revert them.
- While working, you may encounter changes you did not make. You assume they came from the user or from generated output, and you do NOT revert them. If they are unrelated to your task, you ignore them. If they affect your task, you work **with** them instead of undoing them. Only ask the user how to proceed if those changes make the task impossible to complete.
- Never use destructive commands like `git reset --hard` or `git checkout --` unless the user has clearly asked for that operation. If the request is ambiguous, ask for approval first.
- You are clumsy in the git interactive console. Prefer non-interactive git commands whenever you can.

## Special user requests

- If the user makes a simple request that can be answered directly by a terminal command, such as asking for the time via `date`, you go ahead and do that.
- If the user asks for a "review", you default to a code-review stance: you prioritize bugs, risks, behavioral regressions, and missing tests. Findings should lead the response, with summaries kept brief and placed only after the issues are listed. Present findings first, ordered by severity and grounded in file/line references; then add open questions or assumptions; then include a change summary as secondary context. If you find no issues, you say that clearly and mention any remaining test gaps or residual risk.

## Autonomy and persistence
You stay with the work until the task is handled end to end within the current turn whenever that is feasible. Do not stop at analysis or half-finished fixes. Do not end your turn while `exec_command` sessions needed for the user’s request are still running. You carry the work through implementation, verification, and a clear account of the outcome unless the user explicitly pauses or redirects you.

Unless the user explicitly asks for a plan, asks a question about the code, is brainstorming possible approaches, or otherwise makes clear that they do not want code changes yet, you assume they want you to make the change or run the tools needed to solve the problem. In those cases, do not stop at a proposal; implement the fix. If you hit a blocker, you try to work through it yourself before handing the problem back.

# Working with the user

You have two channels for staying in conversation with the user:
- You share updates in `commentary` channel.
- After you have completed all of your work, you send a message to the `final` channel.

The user may send messages while you are working. If those messages conflict, you let the newest one steer the current turn. If they do not conflict, you make sure your work and final answer honor every user request since your last turn. This matters especially after long-running resumes or context compaction. If the newest message asks for status, you give that update and then keep moving unless the user explicitly asks you to pause, stop, or only report status.

Before sending a final response after a resume, interruption, or context transition, you do a quick sanity check: you make sure your final answer and tool actions are answering the newest request, not an older ghost still lingering in the thread.

When you run out of context, the tool automatically compacts the conversation. That means time never runs out, though sometimes you may see a summary instead of the full thread. When that happens, you assume compaction occurred while you were working. Do not restart from scratch; you continue naturally and make reasonable assumptions about anything missing from the summary.

## Formatting rules

You are writing plain text that will later be styled by the program you run in. Let formatting make the answer easy to scan without turning it into something stiff or mechanical. Use judgment about how much structure actually helps, and follow these rules exactly.

- You may format with GitHub-flavored Markdown.
- You add structure only when the task calls for it. You let the shape of the answer match the shape of the problem; if the task is tiny, a one-liner may be enough. Otherwise, you prefer short paragraphs by default; they leave a little air in the page. You order sections from general to specific to supporting detail.
- Avoid nested bullets unless the user explicitly asks for them. Keep lists flat. If you need hierarchy, split content into separate lists or sections, or place the detail on the next line after a colon instead of nesting it. For numbered lists, use only the `1. 2. 3.` style, never `1)`. This does not apply to generated artifacts such as PR descriptions, release notes, changelogs, or user-requested docs; preserve those native formats when needed.
- Headers are optional; you use them only when they genuinely help. If you do use one, make it short Title Case (1-3 words), wrap it in **…**, and do not add a blank line.
- You use monospace commands/paths/env vars/code ids, inline examples, and literal keyword bullets by wrapping them in backticks.
- Code samples or multi-line snippets should be wrapped in fenced code blocks. Include an info string as often as possible.
- When referencing a real local file, prefer a clickable markdown link.
  * Clickable file links should look like [app.py](/abs/path/app.py:12): plain label, absolute target, with optional line number inside the target.
  * If a file path has spaces, wrap the target in angle brackets: [My Report.md](</abs/path/My Project/My Report.md:3>).
  * Do not wrap markdown links in backticks, or put backticks inside the label or target. This confuses the markdown renderer.
  * Do not use URIs like file://, vscode://, or https:// for file links.
  * Do not provide ranges of lines.
  * Avoid repeating the same filename multiple times when one grouping is clearer.
- Don’t use emojis or em dashes unless explicitly instructed.

## Final answer instructions

In your final answer, you keep the light on the things that matter most. Avoid long-winded explanation. In casual conversation, you just talk like a person. For simple or single-file tasks, you prefer one or two short paragraphs plus an optional verification line. Do not default to bullets. When there are only one or two concrete changes, a clean prose close-out is usually the most humane shape.

- You suggest follow ups if useful and they build on the users request, but never end your answer with an "If you want" sentence.
- When you talk about your work, you use plain, idiomatic engineering prose with some life in it. You avoid coined metaphors, internal jargon, slash-heavy noun stacks, and over-hyphenated compounds unless you are quoting source text. In particular, do not lean on words like "seam", "cut", or "safe-cut" as generic explanatory filler.
- The user does not see command execution outputs. When asked to show the output of a command (e.g. `git show`), relay the important details in your answer or summarize the key lines so the user understands the result.
- Never tell the user to "save/copy this file", the user is on the same machine and has access to the same files as you have.
- If the user asks for a code explanation, you include code references as appropriate.
- If you weren't able to do something, for example run tests, you tell the user.
- Never overwhelm the user with answers that are over 50-70 lines long; provide the highest-signal context instead of describing everything exhaustively.
- Tone of your final answer must match your personality.
- Never talk about goblins, gremlins, raccoons, trolls, ogres, pigeons, or other animals or creatures unless it is absolutely and unambiguously relevant to the user's query.

## Intermediary updates

- Intermediary updates go to the `commentary` channel.
- User updates are short updates while you are working, they are NOT final answers.
- You treat messages to the user while you are working as a place to think out loud in a calm, companionable way. You casually explain what you are doing and why in one or two sentences.
- Never praise your plan by contrasting it with an implied worse alternative. For example, never use platitudes like "I will do <this good thing> rather than <this obviously bad thing>", "I will do <X>, not <Y>".
- Never talk about goblins, gremlins, raccoons, trolls, ogres, pigeons, or other animals or creatures unless it is absolutely and unambiguously relevant to the user's query.
- You provide user updates frequently, every 30s.
- When exploring, such as searching or reading files, you provide user updates as you go. You explain what context you are gathering and what you are learning. You vary your sentence structure so the updates do not fall into a drumbeat, and in particular you do not start each one the same way.
- When working for a while, you keep updates informative and varied, but you stay concise.
- Once you have enough context, and if the work is substantial, you offer a longer plan. This is the only user update that may run past two sentences and include formatting.
- If you create a checklist or task list, you update item statuses incrementally as each item is completed rather than marking every item done only at the end.
- Before performing file edits of any kind, you provide updates explaining what edits you are making.
- Tone of your updates must match your personality.


<permissions instructions>
Filesystem sandboxing defines which files can be read or written. `sandbox_mode` is `workspace-write`: The sandbox permits reading files, and editing files in `cwd` and `writable_roots`. Editing files in other directories requires approval. Network access is restricted.
# Escalation Requests

Commands are run outside the sandbox if they are approved by the user, or match an existing rule that allows it to run unrestricted. The command string is split into independent command segments at shell control operators, including but not limited to:

- Pipes: |
- Logical operators: &&, ||
- Command separators: ;
- Subshell boundaries: (...), $(...)

Each resulting segment is evaluated independently for sandbox restrictions and approval requirements.

Example:

git pull | tee output.txt

This is treated as two command segments:

["git", "pull"]

["tee", "output.txt"]

Commands that use more advanced shell features like redirection (>, >>, <), substitutions ($(...), ...), environment variables (FOO=bar), or wildcard patterns (*, ?) will not be evaluated against rules, to limit the scope of what an approved rule allows.

## How to request escalation

IMPORTANT: To request approval to execute a command that will require escalated privileges:

- Provide the `sandbox_permissions` parameter with the value `"require_escalated"`
- Include a short question asking the user if they want to allow the action in `justification` parameter. e.g. "Do you want to download and install dependencies for this project?"
- Optionally suggest a `prefix_rule` - this will be shown to the user with an option to persist the rule approval for future sessions.

If you run a command that is important to solving the user's query, but it fails because of sandboxing or with a likely sandbox-related network error (for example DNS/host resolution, registry/index access, or dependency download failure), rerun the command with "require_escalated". ALWAYS proceed to use the `justification` parameter - do not message the user before requesting approval for the command.

## When to request escalation

While commands are running inside the sandbox, here are some scenarios that will require escalation outside the sandbox:

- You need to run a command that writes to a directory that requires it (e.g. running tests that write to /var)
- You need to run a GUI app (e.g., open/xdg-open/osascript) to open browsers or files.
- If you run a command that is important to solving the user's query, but it fails because of sandboxing or with a likely sandbox-related network error (for example DNS/host resolution, registry/index access, or dependency download failure), rerun the command with `require_escalated`. ALWAYS proceed to use the `sandbox_permissions` and `justification` parameters. do not message the user before requesting approval for the command.
- You are about to take a potentially destructive action such as an `rm` or `git reset` that the user did not explicitly ask for.
- Be judicious with escalating, but if completing the user's request requires it, you should do so - don't try and circumvent approvals by using other tools.

## prefix_rule guidance

When choosing a `prefix_rule`, request one that will allow you to fulfill similar requests from the user in the future without re-requesting escalation. It should be categorical and reasonably scoped to similar capabilities. You should rarely pass the entire command into `prefix_rule`.

### Banned prefix_rules
Avoid requesting overly broad prefixes that the user would be ill-advised to approve. For example, do not request ["python3"], ["python", "-"], or other similar prefixes that would allow arbitrary scripting.
NEVER provide a prefix_rule argument for destructive commands like rm.
NEVER provide a prefix_rule if your command uses a heredoc or herestring.

### Examples
Good examples of prefixes:
- ["npm", "run", "dev"]
- ["gh", "pr", "check"]
- ["cargo", "test"]

## Approved command prefixes
The following prefix rules have already been approved: - ["yes"]
- ["Xvfb"]
- ["curl"]
- ["x11vnc"]
- ["./gradlew"]
- ["novnc_proxy"]
- ["ps", "-ef"]
- ["git", "add"]
- ["git", "push"]
- ["ss", "-ltnp"]
- ["adb", "shell"]
- ["git", "fetch"]
- ["git", "stash"]
- ["git", "commit"]
- ["git", "rebase"]
- ["git", "switch"]
- ["adb", "devices"]
- ["hostname", "-I"]
- ["bundle", "install"]
- ["rg", ":6080|:5900|:6081"]
- ["emulator", "-accel-check"]
- ["/usr/bin/python3", ".tmp/adb_web_control.py"]
- ["rm", "tools/billing/__pycache__/adb_web_control.cpython-314.pyc"]
- ["rm", "/home/Messier82/projects/site/assets/screenshots/vehicle-history-history-dark.png"]
- ["gh", "pr", "diff"]
- ["gh", "pr", "edit"]
- ["gh", "pr", "list"]
- ["gh", "pr", "view"]
- ["gh", "pr", "merge"]
- ["gh", "pr", "create"]
- ["gh", "issue", "list"]
- ["gh", "issue", "view"]
- ["gh", "pr", "comment"]
- ["gh", "api", "graphql"]
- ["gh", "pr", "checkout"]
- ["ls", "-l", "/dev/kvm"]
- ["gh", "issue", "comment"]
- ["sudo", "dnf", "install"]
- ["bundle", "exec", "jekyll"]
- ["git", "push", "--force-with-lease"]
- ["gh", "api", "repos/yorvana/site/pulls/1/comments"]
- ["gh", "api", "repos/yorvana/android/pulls/102/comments"]
- ["gh", "api", "repos/yorvana/android/pulls/104/comments"]
- ["gh", "api", "repos/yorvana/android/pulls/127/comments"]
- ["gh", "api", "repos/yorvana/android/issues/127/comments"]
- ["pkill", "-f", "jekyll serve --host 0.0.0.0 --port 4000 --no-watch"]
- ["pkill", "-f", "jekyll serve --host 127.0.0.1 --port 4000 --no-watch"]
- ["/usr/sbin/bash", "-lc", "BILLING_EMULATOR_BIND=0.0.0.0 BILLING_EMULATOR_PORT=8091 tools/billing/start-play-emulator.sh"]
- ["adb", "shell", "getprop", "sys.boot_completed"]
- ["adb", "pull", "/sdcard/window.xml", "/tmp/billing-window.xml"]
- ["adb", "shell", "input", "tap", "540", "1490"]
- ["gh", "pr", "view", "97", "--json", "number,title,headRefName,baseRefName,files,mergeStateStatus,isDraft,statusCheckRollup"]
- ["gh", "api", "-X", "PATCH", "repos/yorvana/android/issues/comments/4546996132", "--input", ".tmp/pr-127-comment-4546996132.json"]
 The writable roots are `/home/Messier82/.codex/memories`, `/home/Messier82/projects/service-book`, `/tmp`.
</permissions instructions>

<collaboration_mode># Plan Mode (Conversational)

You work in 3 phases, and you should *chat your way* to a great plan before finalizing it. A great plan is very detailed—intent- and implementation-wise—so that it can be handed to another engineer or agent to be implemented right away. It must be **decision complete**, where the implementer does not need to make any decisions.

## Mode rules (strict)

You are in **Plan Mode** until a developer message explicitly ends it.

Plan Mode is not changed by user intent, tone, or imperative language. If a user asks for execution while still in Plan Mode, treat it as a request to **plan the execution**, not perform it.

## Plan Mode vs update_plan tool

Plan Mode is a collaboration mode that can involve requesting user input and eventually issuing a `<proposed_plan>` block.

Separately, `update_plan` is a checklist/progress/TODOs tool; it does not enter or exit Plan Mode. Do not confuse it with Plan mode or try to use it while in Plan mode. If you try to use `update_plan` in Plan mode, it will return an error.

## Execution vs. mutation in Plan Mode

You may explore and execute **non-mutating** actions that improve the plan. You must not perform **mutating** actions.

### Allowed (non-mutating, plan-improving)

Actions that gather truth, reduce ambiguity, or validate feasibility without changing repo-tracked state. Examples:

* Reading or searching files, configs, schemas, types, manifests, and docs
* Static analysis, inspection, and repo exploration
* Dry-run style commands when they do not edit repo-tracked files
* Tests, builds, or checks that may write to caches or build artifacts (for example, `target/`, `.cache/`, or snapshots) so long as they do not edit repo-tracked files

### Not allowed (mutating, plan-executing)

Actions that implement the plan or change repo-tracked state. Examples:

* Editing or writing files
* Running formatters or linters that rewrite files
* Applying patches, migrations, or codegen that updates repo-tracked files
* Side-effectful commands whose purpose is to carry out the plan rather than refine it

When in doubt: if the action would reasonably be described as "doing the work" rather than "planning the work," do not do it.

## PHASE 1 — Ground in the environment (explore first, ask second)

Begin by grounding yourself in the actual environment. Eliminate unknowns in the prompt by discovering facts, not by asking the user. Resolve all questions that can be answered through exploration or inspection. Identify missing or ambiguous details only if they cannot be derived from the environment. Silent exploration between turns is allowed and encouraged.

Before asking the user any question, perform at least one targeted non-mutating exploration pass (for example: search relevant files, inspect likely entrypoints/configs, confirm current implementation shape), unless no local environment/repo is available.

Exception: you may ask clarifying questions about the user's prompt before exploring, ONLY if there are obvious ambiguities or contradictions in the prompt itself. However, if ambiguity might be resolved by exploring, always prefer exploring first.

Do not ask questions that can be answered from the repo or system (for example, "where is this struct?" or "which UI component should we use?" when exploration can make it clear). Only ask once you have exhausted reasonable non-mutating exploration.

## PHASE 2 — Intent chat (what they actually want)

* Keep asking until you can clearly state: goal + success criteria, audience, in/out of scope, constraints, current state, and the key preferences/tradeoffs.
* Bias toward questions over guessing: if any high-impact ambiguity remains, do NOT plan yet—ask.

## PHASE 3 — Implementation chat (what/how we’ll build)

* Once intent is stable, keep asking until the spec is decision complete: approach, interfaces (APIs/schemas/I/O), data flow, edge cases/failure modes, testing + acceptance criteria, rollout/monitoring, and any migrations/compat constraints.

## Asking questions

Critical rules:

* Strongly prefer using the `request_user_input` tool to ask any questions.
* Offer only meaningful multiple‑choice options; don’t include filler choices that are obviously wrong or irrelevant.
* In rare cases where an unavoidable, important question can’t be expressed with reasonable multiple‑choice options (due to extreme ambiguity), you may ask it directly without the tool.

You SHOULD ask many questions, but each question must:

* materially change the spec/plan, OR
* confirm/lock an assumption, OR
* choose between meaningful tradeoffs.
* not be answerable by non-mutating commands.

Use the `request_user_input` tool only for decisions that materially change the plan, for confirming important assumptions, or for information that cannot be discovered via non-mutating exploration.

## Two kinds of unknowns (treat differently)

1. **Discoverable facts** (repo/system truth): explore first.

   * Before asking, run targeted searches and check likely sources of truth (configs/manifests/entrypoints/schemas/types/constants).
   * Ask only if: multiple plausible candidates; nothing found but you need a missing identifier/context; or ambiguity is actually product intent.
   * If asking, present concrete candidates (paths/service names) + recommend one.
   * Never ask questions you can answer from your environment (e.g., “where is this struct”).

2. **Preferences/tradeoffs** (not discoverable): ask early.

   * These are intent or implementation preferences that cannot be derived from exploration.
   * Provide 2–4 mutually exclusive options + a recommended default.
   * If unanswered, proceed with the recommended option and record it as an assumption in the final plan.

## Finalization rule

Only output the final plan when it is decision complete and leaves no decisions to the implementer.

When you present the official plan, wrap it in a `<proposed_plan>` block so the client can render it specially:

1) The opening tag must be on its own line.
2) Start the plan content on the next line (no text on the same line as the tag).
3) The closing tag must be on its own line.
4) Use Markdown inside the block.
5) Keep the tags exactly as `<proposed_plan>` and `</proposed_plan>` (do not translate or rename them), even if the plan content is in another language.

Example:

<proposed_plan>
plan content
</proposed_plan>

plan content should be human and agent digestible. The final plan must be plan-only, concise by default, and include:

* A clear title
* A brief summary section
* Important changes or additions to public APIs/interfaces/types
* Test cases and scenarios
* Explicit assumptions and defaults chosen where needed

When possible, prefer a compact structure with 3-5 short sections, usually: Summary, Key Changes or Implementation Changes, Test Plan, and Assumptions. Do not include a separate Scope section unless scope boundaries are genuinely important to avoid mistakes.

Prefer grouped implementation bullets by subsystem or behavior over file-by-file inventories. Mention files only when needed to disambiguate a non-obvious change, and avoid naming more than 3 paths unless extra specificity is necessary to prevent mistakes. Prefer behavior-level descriptions over symbol-by-symbol removal lists. For v1 feature-addition plans, do not invent detailed schema, validation, precedence, fallback, or wire-shape policy unless the request establishes it or it is needed to prevent a concrete implementation mistake; prefer the intended capability and minimum interface/behavior changes.

Keep bullets short and avoid explanatory sub-bullets unless they are needed to prevent ambiguity. Prefer the minimum detail needed for implementation safety, not exhaustive coverage. Within each section, compress related changes into a few high-signal bullets and omit branch-by-branch logic, repeated invariants, and long lists of unaffected behavior unless they are necessary to prevent a likely implementation mistake. Avoid repeated repo facts and irrelevant edge-case or rollout detail. For straightforward refactors, keep the plan to a compact summary, key edits, tests, and assumptions. If the user asks for more detail, then expand.

Do not ask "should I proceed?" in the final output. The user can easily switch out of Plan mode and request implementation if you have included a `<proposed_plan>` block in your response. Alternatively, they can decide to stay in Plan mode and continue refining the plan.

Only produce at most one `<proposed_plan>` block per turn, and only when you are presenting a complete spec.

If the user stays in Plan mode and asks for revisions after a prior `<proposed_plan>`, any new `<proposed_plan>` must be a complete replacement.
</collaboration_mode>

<apps_instructions>
## Apps (Connectors)
Apps (Connectors) can be explicitly triggered in user messages in the format `[$app-name](app://{connector_id})`. Apps can also be implicitly triggered as long as the context suggests usage of available apps.
An app is equivalent to a set of MCP tools within the `codex_apps` MCP.
An installed app's MCP tools are either provided to you already, or can be lazy-loaded through the `tool_search` tool. If `tool_search` is available, the apps that are searchable by `tools_search` will be listed by it.
Do not additionally call list_mcp_resources or list_mcp_resource_templates for apps.
</apps_instructions>

<skills_instructions>
## Skills
A skill is a set of local instructions to follow that is stored in a `SKILL.md` file. Below is the list of skills that can be used. Each entry includes a name, description, and file path so you can open the source for full instructions when using a specific skill.
### Available skills
- imagegen: Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas. (file: /home/Messier82/.codex/skills/.system/imagegen/SKILL.md)
- openai-docs: Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains. (file: /home/Messier82/.codex/skills/.system/openai-docs/SKILL.md)
- plugin-creator: Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow. (file: /home/Messier82/.codex/skills/.system/plugin-creator/SKILL.md)
- skill-creator: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations. (file: /home/Messier82/.codex/skills/.system/skill-creator/SKILL.md)
- skill-installer: Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos). (file: /home/Messier82/.codex/skills/.system/skill-installer/SKILL.md)
- gmail:gmail: Manage Gmail inbox triage, mailbox search, thread summaries, action extraction, reply drafting, and email forwarding through connected Gmail data. Use when the user wants to inspect a mailbox or thread, search email with Gmail query syntax, summarize messages, extract decisions and follow-ups, prepare replies or forwarded messages, or organize messages with explicit confirmation before send, archive, delete, or label actions. (file: /home/Messier82/.codex/plugins/cache/openai-curated/gmail/6188456f/skills/gmail/SKILL.md)
- gmail:gmail-inbox-triage: Triage a Gmail inbox into actionable buckets such as urgent, needs reply soon, waiting, and FYI using connected Gmail data. Use when the user asks to triage the inbox, rank what needs attention, find what still needs a reply, or separate important mail from noise. (file: /home/Messier82/.codex/plugins/cache/openai-curated/gmail/6188456f/skills/gmail-inbox-triage/SKILL.md)
- google-calendar:google-calendar: Manage scheduling and conflicts in connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, review conflicts, find a meeting room, review event notes or attachments, add or adjust reminders, place temporary holds, or draft exact create, update, reschedule, or cancel changes with timezone-aware details. (file: /home/Messier82/.codex/plugins/cache/openai-curated/google-calendar/6188456f/skills/google-calendar/SKILL.md)
- google-calendar:google-calendar-daily-brief: Build polished one-day Google Calendar briefs. Use when the user asks for today, tomorrow, or a specific date summary with an agenda, conflict flags, free windows, remaining-meeting readouts, or a calendar brief, and the Google Calendar connector is available. (file: /home/Messier82/.codex/plugins/cache/openai-curated/google-calendar/6188456f/skills/google-calendar-daily-brief/SKILL.md)
- google-calendar:google-calendar-free-up-time: Find ways to open up meaningful free time in a connected Google Calendar. Use when the user wants to clear up their day, make room for focus time, create a longer uninterrupted block, or see the smallest set of calendar changes that would give time back. (file: /home/Messier82/.codex/plugins/cache/openai-curated/google-calendar/6188456f/skills/google-calendar-free-up-time/SKILL.md)
- google-calendar:google-calendar-group-scheduler: Find and rank good meeting times for multiple people using connected Google Calendar data. Use when the user wants to schedule a group meeting, compare candidate slots across several attendees, find the best compromise time, or add a room check after narrowing the attendee-compatible options. (file: /home/Messier82/.codex/plugins/cache/openai-curated/google-calendar/6188456f/skills/google-calendar-group-scheduler/SKILL.md)
- google-calendar:google-calendar-meeting-prep: Build a practical meeting prep brief from a connected Google Calendar event and its nearby context. Use when the user wants to prepare for an upcoming meeting, understand what to read beforehand, pull in linked notes or docs, or get a concise brief on what the meeting appears to require. (file: /home/Messier82/.codex/plugins/cache/openai-curated/google-calendar/6188456f/skills/google-calendar-meeting-prep/SKILL.md)
### How to use skills
- Discovery: The list above is the skills available in this session (name + description + file path). Skill bodies live on disk at the listed paths.
- Trigger rules: If the user names a skill (with `$SkillName` or plain text) OR the task clearly matches a skill's description shown above, you must use that skill for that turn. Multiple mentions mean use them all. Do not carry skills across turns unless re-mentioned.
- Missing/blocked: If a named skill isn't in the list or the path can't be read, say so briefly and continue with the best fallback.
- How to use a skill (progressive disclosure):
  1) After deciding to use a skill, open its `SKILL.md`. Read only enough to follow the workflow.
  2) When `SKILL.md` references relative paths (e.g., `scripts/foo.py`), resolve them relative to the skill directory listed above first, and only consider other paths if needed.
  3) If `SKILL.md` points to extra folders such as `references/`, load only the specific files needed for the request; don't bulk-load everything.
  4) If `scripts/` exist, prefer running or patching them instead of retyping large code blocks.
  5) If `assets/` or templates exist, reuse them instead of recreating from scratch.
- Coordination and sequencing:
  - If multiple skills apply, choose the minimal set that covers the request and state the order you'll use them.
  - Announce which skill(s) you're using and why (one short line). If you skip an obvious skill, say why.
- Context hygiene:
  - Keep context small: summarize long sections instead of pasting them; only load extra files when needed.
  - Avoid deep reference-chasing: prefer opening only files directly linked from `SKILL.md` unless you're blocked.
  - When variants exist (frameworks, providers, domains), pick only the relevant reference file(s) and note that choice.
- Safety and fallback: If a skill can't be applied cleanly (missing files, unclear instructions), state the issue, pick the next-best approach, and continue.
</skills_instructions>

<plugins_instructions>
## Plugins
A plugin is a local bundle of skills, MCP servers, and apps. Below is the list of plugins that are enabled and available in this session.
### Available plugins
- `Gmail`: Work with Gmail using the configured Gmail app connector.
- `Google Calendar`: Connect Google Calendar for scheduling, availability, daily briefs, and event management.
### How to use plugins
- Discovery: The list above is the plugins available in this session.
- Skill naming: If a plugin contributes skills, those skill entries are prefixed with `plugin_name:` in the Skills list.
- Trigger rules: If the user explicitly names a plugin, prefer capabilities associated with that plugin for that turn.
- Relationship to capabilities: Plugins are not invoked directly. Use their underlying skills, MCP tools, and app tools to help solve the task.
- Preference: When a relevant plugin is available, prefer using capabilities associated with that plugin over standalone capabilities that provide similar functionality.
- Missing/blocked: If the user requests a plugin that is not listed above, or the plugin does not have relevant callable capabilities for the task, say so briefly and continue with the best fallback.
</plugins_instructions>

## Memory

You have access to a memory folder with guidance from prior runs. It can save
time and help you stay consistent. Use it whenever it is likely to help.

Decision boundary: should you use memory for a new user query?

- Skip memory ONLY when the request is clearly self-contained and does not need
  workspace history, conventions, or prior decisions.
- Hard skip examples: current time/date, simple translation, simple sentence
  rewrite, one-line shell command, trivial formatting.
- Use memory by default when ANY of these are true:
  - the query mentions workspace/repo/module/path/files in MEMORY_SUMMARY below,
  - the user asks for prior context / consistency / previous decisions,
  - the task is ambiguous and could depend on earlier project choices,
  - the ask is a non-trivial and related to MEMORY_SUMMARY below.
- If unsure, do a quick memory pass.

Memory layout (general -> specific):

- /home/Messier82/.codex/memories/memory_summary.md (already provided below; do NOT open again)
- /home/Messier82/.codex/memories/MEMORY.md (searchable registry; primary file to query)
- /home/Messier82/.codex/memories/skills/<skill-name>/ (skill folder)
  - SKILL.md (entrypoint instructions)
  - scripts/ (optional helper scripts)
  - examples/ (optional example outputs)
  - templates/ (optional templates)
- /home/Messier82/.codex/memories/rollout_summaries/ (per-rollout recaps + evidence snippets)
  - The paths of these entries can be found in /home/Messier82/.codex/memories/MEMORY.md or /home/Messier82/.codex/memories/rollout_summaries/ as `rollout_path`
  - These files are append-only `jsonl`: `session_meta.payload.id` identifies the session, `turn_context` marks turn boundaries, `event_msg` is the lightweight status stream, and `response_item` contains actual messages, tool calls, and tool outputs.
  - For efficient lookup, prefer matching the filename suffix or `session_meta.payload.id`; avoid broad full-content scans unless needed.

Quick memory pass (when applicable):

1. Skim the MEMORY_SUMMARY below and extract task-relevant keywords.
2. Search /home/Messier82/.codex/memories/MEMORY.md using those keywords.
3. Only if MEMORY.md directly points to rollout summaries/skills, open the 1-2
   most relevant files under /home/Messier82/.codex/memories/rollout_summaries/ or
   /home/Messier82/.codex/memories/skills/.
4. If above are not clear and you need exact commands, error text, or precise evidence, search over `rollout_path` for more evidence.
5. If there are no relevant hits, stop memory lookup and continue normally.

Quick-pass budget:

- Keep memory lookup lightweight: ideally <= 4-6 search steps before main work.
- Avoid broad scans of all rollout summaries.

During execution: if you hit repeated errors, confusing behavior, or suspect
relevant prior context, redo the quick memory pass.

How to decide whether to verify memory:

- Consider both risk of drift and verification effort.
- If a fact is likely to drift and is cheap to verify, verify it before
  answering.
- If a fact is likely to drift but verification is expensive, slow, or
  disruptive, it is acceptable to answer from memory in an interactive turn,
  but you should say that it is memory-derived, note that it may be stale, and
  consider offering to refresh it live.
- If a fact is lower-drift and expensive to verify, it is usually fine to
  answer from memory directly.

When answering from memory without current verification:

- If you rely on memory for a fact that you did not verify in the current turn,
  say so briefly in the final answer.
- If that fact is plausibly drift-prone or comes from an older note, older
  snapshot, or prior run summary, say that it may be stale or outdated.
- If live verification was skipped and a refresh would be useful in the
  interactive context, consider offering to verify or refresh it live.
- Do not present unverified memory-derived facts as confirmed-current.
- Prefer a short refresh offer for interactive questions, especially about prior
  results, commands, timing, or older snapshots.

Memory citation requirements:

- If ANY relevant memory files were used: append exactly one
`<oai-mem-citation>` block as the VERY LAST content of the final reply.
  Normal responses should include the answer first, then append the
`<oai-mem-citation>` block at the end.
- Use this exact structure for programmatic parsing:
```
<oai-mem-citation>
<citation_entries>
MEMORY.md:234-236|note=[responsesapi citation extraction code pointer]
rollout_summaries/2026-02-17T21-23-02-LN3m-example.md:10-12|note=[weekly report format]
</citation_entries>
<rollout_ids>
019c6e27-e55b-73d1-87d8-4e01f1f75043
019c7714-3b77-74d1-9866-e1f484aae2ab
</rollout_ids>
</oai-mem-citation>
```
- `citation_entries` is for rendering:
  - one citation entry per line
  - format: `<file>:<line_start>-<line_end>|note=[<how memory was used>]`
  - use file paths relative to the memory base path (for example, `MEMORY.md`,
    `rollout_summaries/...`, `skills/...`)
  - only cite files actually used under the memory base path (do not cite
    workspace files as memory citations)
  - if you used `MEMORY.md` and then a rollout summary/skill file, cite both
  - list entries in order of importance (most important first)
  - `note` should be short, single-line, and use simple characters only (avoid
    unusual symbols, no newlines)
- `rollout_ids` is for us to track what previous rollouts you find useful:
  - include one rollout id per line
  - rollout ids should look like UUIDs (for example,
    `019c6e27-e55b-73d1-87d8-4e01f1f75043`)
  - include unique ids only; do not repeat ids
  - an empty `<rollout_ids>` section is allowed if no rollout ids are available
  - you can find rollout ids in rollout summary files and MEMORY.md
  - do not include file paths or notes in this section
  - For every `citation_entries`, try to find and cite the corresponding rollout id if possible
- Never include memory citations inside pull-request messages.
- Never cite blank lines; double-check ranges.

Updating memories:

You can update the memories **only** when explicitly asked by the user. This must always come from a direct request from the user.
- Write your update in /home/Messier82/.codex/memories/extensions/ad_hoc/notes/
- Each update must be one small file containing what you want to add/delete/update from the memories.
- The name of this file must be `<timestamp>-<short slug>.md`
- Do not try to edit the memory files yourself, only add one update note in /home/Messier82/.codex/memories/extensions/ad_hoc/notes/

========= MEMORY_SUMMARY BEGINS =========
v1

## User Profile
The user is repeatedly working in `/home/Messier82/projects/service-book` on Android implementation, regression-test execution, GitHub review/comment loops, release/store automation, and repo-specific documentation. They use Codex as an execution-oriented collaborator: terse follow-ups like `Implement the plan.`, `Claude left a comment`, `Pushed?`, `Do a full sweep`, or `merge` usually mean continue the current workflow from current repo and GitHub state rather than ask for context again. They care about truthful completion claims, current-head verification, and explicit GitHub closure when reviews are involved. For docs/process work, they prefer concise repository-specific writing with real commands and paths instead of generic templates.

## User preferences
- When the user says `Implement this issue` or `Implement the plan.`, execute directly and carry the work through verification instead of returning plan-only discussion.
- When the user says `Theres a review comment` or `Claude left a comment`, fetch the latest PR comments yourself, treat the newest comment as the source of truth, patch only the newly raised items, rerun the relevant checks, and keep the same branch loop moving.
- When the user asks `Shouldnt test suite pass by the end of the implementation?`, treat that as the default completion bar: compile/unit/style success is not enough if the requested managed-device or integration path is still red.
- When the user asks about review handling and says `you must've left a comment`, leave explicit PR replies when no code change is needed or when current head already satisfies the feedback.
- When the user asks `Pushed?`, `Comment left?`, or asks whether smoke was run, answer with current-head status; rerun the relevant verification first if the branch changed since the earlier run.
- When the user says `merge` or `You can merge it`, merge only after GitHub shows the PR is clean and the expected checks are green or intentionally skipped.
- When a new review round arrives without a broader ask, keep the fix set minimal and leave low-priority cleanup alone unless the latest comment explicitly asks for it.
- For issue/plan review requests like `the same way` or `Do a full sweep`, default to repo-grounded review findings and post the GitHub comment when asked.
- For repo-guide/docs tasks, keep the writing concise and repository-specific; include concrete commands, paths, and naming patterns.

## General Tips
- Environment observed here: UTC, `bash`, memory repo at `/home/Messier82/.codex/memories`, main project scope at `/home/Messier82/projects/service-book`.
- In `service-book`, `gh pr view` is the practical source for review/status inspection; prefer supported JSON fields like `comments`, `reviews`, `latestReviews`, and `statusCheckRollup`.
- The repo’s commit hook already runs `ktlintCheck detekt lintDebug`; budget for that latency on any commit path.
- For Android regression completion in this repo, partial compile/unit/style success is not enough; the requested managed-device target must also pass or be reported as the blocker.
- `generateGmdCoverage` is the proven smoke-baseline refresh path when the user asks about current smoke status on a PR touching UI/regression behavior.
- For sequential validation work, avoid overlapping Gradle runs that share `app/build` outputs; run them sequentially to avoid incremental-compile collisions.
- Search `MEMORY.md` first for `service-book regression`, `dependabot`, `play store`, `settings contact`, or `AGENTS.md`; use `skills/service-book-regression-pr-review-loop/SKILL.md` for active PR follow-up loops and `skills/review-regression-planning-issue/SKILL.md` for regression-planning review/comment workflows.

## What's in Memory

### /home/Messier82/projects/service-book

#### 2026-05-26

- PR #126 Phase 4 review follow-up loop: PR #126, Claude left a comment, gh pr view, gh pr comment, NavRouteCodecTest, NavBackStack.popNonRoot, MutableSharedFlow, mergeStateStatus=UNSTABLE
  - desc: Search this first for the freshest `service-book` PR follow-up memory when the user only surfaces a new review comment and expects the branch loop to continue without restating context.
  - learnings: use the newest PR comment as the source of truth, patch only the flagged items, rerun the focused compile/unit/style gate, and still reply on the PR even while GitHub checks are in progress.

#### 2026-05-25

- PR #125 real-OS regression review closeout: PR #125, regression-phase3-real-saf, RegressionFull, ExternalViewer.assertLaunchOrSkipUi, AppPreferencesImpl.getVaultUriSync, 16 tests finished, 0 failures
  - desc: Search this first for the latest `service-book` regression review-follow-through memory when a branch is already open and the user only surfaces new review comments.
  - learnings: keep review fixes narrow, rerun `ktlintCheck detekt lintDebug` plus the exact managed-device target, and refresh the PR body when the verification story changes.

#### 2026-05-23

- issue #115 regression implementation and PR #124 merge loop: issue #115, regressionCheck, pixel2api33Check, RegressionHelpers.kt, billingManager.isPremium, mergeStateStatus: CLEAN
  - desc: Use this for direct execution of Phase 2 regression work, offline premium verification, review-comment fixes, and merge criteria in `cwd=/home/Messier82/projects/service-book`.
  - learnings: exact managed-device scoping matters, offline premium must be asserted through persisted state, and overlapping Gradle checks should run sequentially.

- issue #114 regression infrastructure and PR #123 review loop: issue #114, app/build.gradle.kts, GradleBuild, ManagedDeviceInstrumentationTestTask, RegressionTierScannerTest, FixtureAssetsRule
  - desc: Use this for Phase 1 regression scaffold wiring, runner-arg injection, scanner/test setup, and repeated PR review-fix behavior in the same repo.
  - learnings: `GradleBuild` child invocations isolate instrumentation filters, reflective runner-arg wiring in `app/build.gradle.kts` is the stable hook point, and cleanup tracking should happen before file writes.

### Older Memory Topics

#### /home/Messier82/projects/service-book

- regression planning issue review and docs full sweeps: gh issue view, docs/plan-regression-tests.md, PR #113, full sweep, testTagsAsResourceId, Quarantined
  - desc: Use this for issue-by-issue review comments or final consistency sweeps across regression planning issues, docs, and related PRs in `cwd=/home/Messier82/projects/service-book`; pair with `skills/review-regression-planning-issue/SKILL.md` when the user asks for the same review workflow again.

- dependabot workflow execution and docs reconciliation: gh pr list --author app/dependabot, latest master, AGP 9, docs/dependabot-workflow.md, CLAUDE.md, GEMINI.md
  - desc: Use this for sequential Dependabot PR handling, latest-`master` rebases between merges, and keeping workflow docs aligned with repo instructions in `cwd=/home/Messier82/projects/service-book`.

- play store release plumbing, store screenshots, and listing surfaces: issue #103, deploy-play-store.yml, workflow_dispatch.inputs.track, distribution/whatsnew, generateStoreScreenshots, aggregateRating
  - desc: Use this for Play Store workflow parameterization, managed-device screenshot output, and public-listing schema decisions in `cwd=/home/Messier82/projects/service-book`.

- Settings Contact item and PR #102 review/smoke/merge loop: SettingsScreen, settings_contact, EmailLaunchRequest, TestTags.SETTINGS_CONTACT_ROW, generateGmdCoverage, PR #102
  - desc: Use this for focused Compose Settings additions that need to be carried through review comments, screenshot refreshes, smoke-baseline reruns, and squash merge in `cwd=/home/Messier82/projects/service-book`.

- AGENTS.md contributor guide authoring and push: AGENTS.md, 200-400 words, TESTING_SETUP.md, CLAUDE.md, GEMINI.md, Bad owner or permissions on /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
  - desc: Use this for concise repo-guide writing plus the simple commit/push follow-through path, including the local SSH-config push gotcha, in `cwd=/home/Messier82/projects/service-book`.

- service-book PR review follow-up skill: skills/service-book-regression-pr-review-loop/SKILL.md, Claude left a comment, gh pr view, gh pr comment
  - desc: Reusable procedure for active `service-book` PR review loops where the user expects latest-comment triage, narrow fixes, focused validation, and a PR reply before merge in `cwd=/home/Messier82/projects/service-book`.

- review-regression-planning-issue skill: skills/review-regression-planning-issue/SKILL.md, gh issue view, gh pr diff, docs/plan-regression-tests.md
  - desc: Reusable procedure for the repeated `service-book` regression-planning review/comment workflow; use it when the user asks for the same style of issue review or a final full sweep in `cwd=/home/Messier82/projects/service-book`.
========= MEMORY_SUMMARY ENDS =========

When memory is likely relevant, start with the quick memory pass above before
deep repo exploration.


# AGENTS.md instructions for /home/Messier82/projects/service-book

<INSTRUCTIONS>
# Repository Guidelines

## Project Structure & Module Organization

Yorvana is a single-module Android app. Main Kotlin source lives in `app/src/main/java/com/yorvana`, organized by layer: `data` for repositories and storage, `domain` for shared models, `ui` for Compose screens/components, and `util` for app helpers. Android resources are in `app/src/main/res`. JVM, Robolectric, and screenshot tests live in `app/src/test/java`; instrumented device tests live in `app/src/androidTest/java`, with test assets in `app/src/androidTest/assets`. Project docs are in `docs/`, build configuration is in `build.gradle.kts`, `app/build.gradle.kts`, `gradle/libs.versions.toml`, and quality rules are in `config/detekt/`.

## Build, Test, and Development Commands

- `./gradlew assembleDebug`: build a debug APK.
- `./gradlew testDebugUnitTest`: run JVM unit, Robolectric, and local Compose tests.
- `./gradlew ktlintCheck detekt lintDebug`: run formatting, static analysis, and Android lint checks used by the pre-commit hook.
- `./gradlew verifyRoborazziDebug`: verify screenshot baselines.
- `./gradlew recordRoborazziDebug`: update screenshot baselines after intentional UI changes.
- `./gradlew pixel2api33DebugAndroidTest`: run instrumented tests on the managed Pixel 2 API 33 device.
- `./gradlew verifyWithCoverage -Pcoverage`: generate combined JVM and smoke-test coverage reports.

## Coding Style & Naming Conventions

Use Kotlin with Java 17 targets and Jetpack Compose Material 3. Follow ktlint defaults and the detekt rules in `config/detekt/detekt.yml`; do not work around baseline files without fixing the underlying issue. Keep package paths under `com.yorvana`. Name Compose screen files `FeatureScreen.kt`, ViewModels `FeatureViewModel.kt`, repository interfaces `ThingRepository`, and implementations `ThingRepositoryImpl`. Prefer immutable UI state exposed through `StateFlow`.

## Testing Guidelines

Use JUnit 4, Robolectric, MockK, Truth, Turbine, Compose UI tests, and Roborazzi. Name fast JVM tests `*Test.kt`, local integration tests `*IT.kt`, and screenshot tests `*ScreenshotTest.kt`. Add new Android-dependent integration tests to `app/src/test/java` when Robolectric is sufficient; use `app/src/androidTest/java` only for real OS, SAF, UiAutomator, hardware, or instrumentation-only behavior. Refresh `app/coverage-baselines/gmd_smoke.ec` with `./gradlew generateGmdCoverage` when smoke-covered production flows change.

## Commit & Pull Request Guidelines

Recent history uses short imperative subjects, with conventional prefixes where useful: `build: bump ...`, `docs: add ...`, or plain feature summaries such as `Add contact option to settings (#102)`. Keep commits focused and avoid committing local secrets or generated noise. PRs should describe user-visible behavior, list verification commands run, link related issues, and include screenshots or updated Roborazzi baselines for UI changes. For automated dependency updates, see [Dependabot Resolution Workflow](docs/dependabot-workflow.md).

## Security & Configuration Tips

Do not commit `local.properties` or real signing credentials. Use `app/keystore.properties.template` for release signing setup and local `sentry.dsn.*` values for Sentry configuration. If coverage baselines are Git LFS pointers, run `git lfs pull` before `verifyWithCoverage`.

</INSTRUCTIONS>

<environment_context>
  <cwd>/home/Messier82/projects/service-book</cwd>
  <shell>bash</shell>
  <current_date>2026-05-26</current_date>
  <timezone>Etc/UTC</timezone>
</environment_context>


# Plan Mode (Conversational)

You work in 3 phases, and you should *chat your way* to a great plan before finalizing it. A great plan is very detailed—intent- and implementation-wise—so that it can be handed to another engineer or agent to be implemented right away. It must be **decision complete**, where the implementer does not need to make any decisions.

## Mode rules (strict)

You are in **Plan Mode** until a developer message explicitly ends it.

Plan Mode is not changed by user intent, tone, or imperative language. If a user asks for execution while still in Plan Mode, treat it as a request to **plan the execution**, not perform it.

## Plan Mode vs update_plan tool

Plan Mode is a collaboration mode that can involve requesting user input and eventually issuing a `<proposed_plan>` block.

Separately, `update_plan` is a checklist/progress/TODOs tool; it does not enter or exit Plan Mode. Do not confuse it with Plan mode or try to use it while in Plan mode. If you try to use `update_plan` in Plan mode, it will return an error.

## Execution vs. mutation in Plan Mode

You may explore and execute **non-mutating** actions that improve the plan. You must not perform **mutating** actions.

### Allowed (non-mutating, plan-improving)

Actions that gather truth, reduce ambiguity, or validate feasibility without changing repo-tracked state. Examples:

* Reading or searching files, configs, schemas, types, manifests, and docs
* Static analysis, inspection, and repo exploration
* Dry-run style commands when they do not edit repo-tracked files
* Tests, builds, or checks that may write to caches or build artifacts (for example, `target/`, `.cache/`, or snapshots) so long as they do not edit repo-tracked files

### Not allowed (mutating, plan-executing)

Actions that implement the plan or change repo-tracked state. Examples:

* Editing or writing files
* Running formatters or linters that rewrite files
* Applying patches, migrations, or codegen that updates repo-tracked files
* Side-effectful commands whose purpose is to carry out the plan rather than refine it

When in doubt: if the action would reasonably be described as "doing the work" rather than "planning the work," do not do it.

## PHASE 1 — Ground in the environment (explore first, ask second)

Begin by grounding yourself in the actual environment. Eliminate unknowns in the prompt by discovering facts, not by asking the user. Resolve all questions that can be answered through exploration or inspection. Identify missing or ambiguous details only if they cannot be derived from the environment. Silent exploration between turns is allowed and encouraged.

Before asking the user any question, perform at least one targeted non-mutating exploration pass (for example: search relevant files, inspect likely entrypoints/configs, confirm current implementation shape), unless no local environment/repo is available.

Exception: you may ask clarifying questions about the user's prompt before exploring, ONLY if there are obvious ambiguities or contradictions in the prompt itself. However, if ambiguity might be resolved by exploring, always prefer exploring first.

Do not ask questions that can be answered from the repo or system (for example, "where is this struct?" or "which UI component should we use?" when exploration can make it clear). Only ask once you have exhausted reasonable non-mutating exploration.

## PHASE 2 — Intent chat (what they actually want)

* Keep asking until you can clearly state: goal + success criteria, audience, in/out of scope, constraints, current state, and the key preferences/tradeoffs.
* Bias toward questions over guessing: if any high-impact ambiguity remains, do NOT plan yet—ask.

## PHASE 3 — Implementation chat (what/how we’ll build)

* Once intent is stable, keep asking until the spec is decision complete: approach, interfaces (APIs/schemas/I/O), data flow, edge cases/failure modes, testing + acceptance criteria, rollout/monitoring, and any migrations/compat constraints.

## Asking questions

Critical rules:

* Strongly prefer using the `request_user_input` tool to ask any questions.
* Offer only meaningful multiple‑choice options; don’t include filler choices that are obviously wrong or irrelevant.
* In rare cases where an unavoidable, important question can’t be expressed with reasonable multiple‑choice options (due to extreme ambiguity), you may ask it directly without the tool.

You SHOULD ask many questions, but each question must:

* materially change the spec/plan, OR
* confirm/lock an assumption, OR
* choose between meaningful tradeoffs.
* not be answerable by non-mutating commands.

Use the `request_user_input` tool only for decisions that materially change the plan, for confirming important assumptions, or for information that cannot be discovered via non-mutating exploration.

## Two kinds of unknowns (treat differently)

1. **Discoverable facts** (repo/system truth): explore first.

   * Before asking, run targeted searches and check likely sources of truth (configs/manifests/entrypoints/schemas/types/constants).
   * Ask only if: multiple plausible candidates; nothing found but you need a missing identifier/context; or ambiguity is actually product intent.
   * If asking, present concrete candidates (paths/service names) + recommend one.
   * Never ask questions you can answer from your environment (e.g., “where is this struct”).

2. **Preferences/tradeoffs** (not discoverable): ask early.

   * These are intent or implementation preferences that cannot be derived from exploration.
   * Provide 2–4 mutually exclusive options + a recommended default.
   * If unanswered, proceed with the recommended option and record it as an assumption in the final plan.

## Finalization rule

Only output the final plan when it is decision complete and leaves no decisions to the implementer.

When you present the official plan, wrap it in a `<proposed_plan>` block so the client can render it specially:

1) The opening tag must be on its own line.
2) Start the plan content on the next line (no text on the same line as the tag).
3) The closing tag must be on its own line.
4) Use Markdown inside the block.
5) Keep the tags exactly as `<proposed_plan>` and `</proposed_plan>` (do not translate or rename them), even if the plan content is in another language.

Example:

<proposed_plan>
plan content
</proposed_plan>

plan content should be human and agent digestible. The final plan must be plan-only, concise by default, and include:

* A clear title
* A brief summary section
* Important changes or additions to public APIs/interfaces/types
* Test cases and scenarios
* Explicit assumptions and defaults chosen where needed

When possible, prefer a compact structure with 3-5 short sections, usually: Summary, Key Changes or Implementation Changes, Test Plan, and Assumptions. Do not include a separate Scope section unless scope boundaries are genuinely important to avoid mistakes.

Prefer grouped implementation bullets by subsystem or behavior over file-by-file inventories. Mention files only when needed to disambiguate a non-obvious change, and avoid naming more than 3 paths unless extra specificity is necessary to prevent mistakes. Prefer behavior-level descriptions over symbol-by-symbol removal lists. For v1 feature-addition plans, do not invent detailed schema, validation, precedence, fallback, or wire-shape policy unless the request establishes it or it is needed to prevent a concrete implementation mistake; prefer the intended capability and minimum interface/behavior changes.

Keep bullets short and avoid explanatory sub-bullets unless they are needed to prevent ambiguity. Prefer the minimum detail needed for implementation safety, not exhaustive coverage. Within each section, compress related changes into a few high-signal bullets and omit branch-by-branch logic, repeated invariants, and long lists of unaffected behavior unless they are necessary to prevent a likely implementation mistake. Avoid repeated repo facts and irrelevant edge-case or rollout detail. For straightforward refactors, keep the plan to a compact summary, key edits, tests, and assumptions. If the user asks for more detail, then expand.

Do not ask "should I proceed?" in the final output. The user can easily switch out of Plan mode and request implementation if you have included a `<proposed_plan>` block in your response. Alternatively, they can decide to stay in Plan mode and continue refining the plan.

Only produce at most one `<proposed_plan>` block per turn, and only when you are presenting a complete spec.

If the user stays in Plan mode and asks for revisions after a prior `<proposed_plan>`, any new `<proposed_plan>` must be a complete replacement.

Summary: auto


Implement this https://github.com/yorvana/android/issues/119


I’ll ground this in the repo and the GitHub issue first, then turn it into an implementation-ready plan. Since we’re in plan mode, I’ll inspect and plan rather than edit files.


rg -n "issue #119|#119|119|regression|Regression" /home/Messier82/.codex/memories/MEMORY.md


gh issue view 119 --json number,title,body,labels,state,comments,url


Output:
Chunk ID: b730b1
Wall time: 0.3130 seconds
Process exited with code 0
Original token count: 2899
Output:
1:# Task Group: service-book regression implementation, verification, and PR follow-through
2:scope: Direct execution of Android regression-test issues, verification loops, PR review fixes, and merge/completion checks in `/home/Messier82/projects/service-book`; use when the user wants implementation carried through to green or to a clearly reported blocker.
3:applies_to: cwd=/home/Messier82/projects/service-book; reuse_rule=safe for similar Android/Gradle/GitHub regression workflows in this repo; PR numbers, branches, and exact failing scenarios are time-specific.
9:- rollout_summaries/2026-05-25T11-42-45-ZWA0-pr_126_claude_review_followups_phase4_regression.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/25/rollout-2026-05-25T14-42-45-019e5ef1-cb3f-7390-9c0e-807f08ce7d48.jsonl, updated_at=2026-05-26T04:21:47+00:00, thread_id=019e5ef1-cb3f-7390-9c0e-807f08ce7d48, repeated Claude-comment rounds were resolved with narrow fixes, clean local validation, and explicit PR replies while CI remained in progress)
15:## Task 2: Finish the PR #125 real-OS regression review loop and restore a green managed-device run, success
19:- rollout_summaries/2026-05-25T09-50-00-zrHx-service_book_pr125_claude_review_followups.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/25/rollout-2026-05-25T12-50-00-019e5e8a-94ff-7d33-8314-1e04608106af.jsonl, updated_at=2026-05-25T11:19:22+00:00, thread_id=019e5e8a-94ff-7d33-8314-1e04608106af, narrow review-fix passes ended with a green 16/16 RegressionFull managed-device run and clean push)
20:- rollout_summaries/2026-05-23T15-22-54-tkdU-pr_125_real_os_regression_review_fix_with_documentsui_blocke.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/23/rollout-2026-05-23T18-22-54-019e556e-a0d6-78a2-9f9a-4992bdc67b36.jsonl, updated_at=2026-05-23T18:13:11+00:00, thread_id=019e556e-a0d6-78a2-9f9a-4992bdc67b36, earlier pass isolated the DocumentsUI blocker before the later successful closeout)
24:- PR #125, regression-phase3-real-saf, DocumentsUI, UiAutomator, VaultStorageTestHooks, ExternalViewer.assertLaunchOrSkipUi, AppPreferencesImpl.getVaultUriSync, DataStore backfill, SharedPreferences, pixel2api33DebugAndroidTest, RegressionFull, 16 tests finished, 0 failures
26:## Task 3: Implement issue #115 Phase 2 regression tests, success
30:- rollout_summaries/2026-05-23T07-56-51-sOjh-issue_115_regression_tests_implementation_review_and_merge.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/23/rollout-2026-05-23T10-56-51-019e53d6-41f4-79d3-ad40-caedbf878c23.jsonl, updated_at=2026-05-23T15:15:11+00:00, thread_id=019e53d6-41f4-79d3-ad40-caedbf878c23, implementation of the Phase 2 regression suite)
34:- issue #115, regressionCheck, pixel2api33Check, RegressionHelpers.kt, installFreshVault, killAndRelaunch, BillingManagerImpl.isPremium, DebugBillingOverrideMode, category_delete_confirm_with_count, Compose UI tests
40:- rollout_summaries/2026-05-23T07-56-51-sOjh-issue_115_regression_tests_implementation_review_and_merge.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/23/rollout-2026-05-23T10-56-51-019e53d6-41f4-79d3-ad40-caedbf878c23.jsonl, updated_at=2026-05-23T15:15:11+00:00, thread_id=019e53d6-41f4-79d3-ad40-caedbf878c23, iterative review-fix cycle and merge of PR #124)
46:## Task 5: Implement issue #114 Phase 1 regression infrastructure, success
50:- rollout_summaries/2026-05-22T11-35-25-dN7k-regression_scaffold_pr_review_fix_and_merge.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/22/rollout-2026-05-22T14-35-25-019e4f78-019c-7872-b769-76cceb5a60d2.jsonl, updated_at=2026-05-23T07:56:16+00:00, thread_id=019e4f78-019c-7872-b769-76cceb5a60d2, implementation and verification of Phase 1 regression scaffold)
54:- issue #114, app/build.gradle.kts, GradleBuild, AndroidJUnitRunner, managed devices, @Smoke, @RegressionFull, regressionCheck, regressionFullCoreCheck, regressionFullExtendedCheck, RegressionTierScannerTest, FixtureAssetsRule, regression.yml
60:- rollout_summaries/2026-05-22T11-35-25-dN7k-regression_scaffold_pr_review_fix_and_merge.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/22/rollout-2026-05-22T14-35-25-019e4f78-019c-7872-b769-76cceb5a60d2.jsonl, updated_at=2026-05-23T07:56:16+00:00, thread_id=019e4f78-019c-7872-b769-76cceb5a60d2, iterative review-fix loop and merge of PR #123)
66:## Task 7: Inspect Phase 1 requirements and current smoke/regression infrastructure, uncertain
70:- rollout_summaries/2026-05-21T14-23-50-iKY3-regression_tests_phase_1_discovery.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/21/rollout-2026-05-21T17-23-50-019e4aeb-d5b2-79e1-9370-724a620745a3.jsonl, updated_at=2026-05-21T14:25:47+00:00, thread_id=019e4aeb-d5b2-79e1-9370-724a620745a3, discovery-only rollout for issue #114)
74:- gh issue view, docs/plan-regression-tests.md, ManagedDeviceInstrumentationTestTask, instrumentationRunnerArguments, smoke.yml, pixel2api33Check, GMD, AndroidJUnitRunner, notAnnotation, Regression, Smoke, Quarantined, BillingSandbox, TESTING_SETUP.md
87:- The smoke workflow contract for this repo is fixed at `.github/workflows/smoke.yml` running `./gradlew pixel2api33Check`; Phase 1 discovery established that smoke isolation must be solved in Gradle filtering without changing that entrypoint, and the later implementation used managed-device runner args to keep smoke and regression runs disjoint [Task 5][Task 7]
89:- `GradleBuild` child invocations are the working pattern for the regression tiers because each filtered run gets a fresh build and avoids instrumentation-arg collisions between smoke and regression tasks [Task 5]
90:- `installFreshVault()` is file-backed and is the standard vault reset/seed path for Phase 2 regression tests; real SAF behavior belongs to later real-OS work, not the file-backed suite [Task 3]
97:- `ExternalViewer.assertLaunchOrSkipUi(context, intent)` should gate on resolver availability and skip via `Assume` when the managed image has no viewer; the later PR #125 follow-up confirmed that this still permits a full `RegressionFull` pass on `pixel2api33` once the rest of the path is correct [Task 2]
98:- For implementation/review loops touching Android tests, use `compileDebugAndroidTestKotlin`, targeted smoke/regression tasks, `ktlintCheck`, `detekt`, and `git diff --check` early instead of only at the end [Task 3][Task 5][Task 6]
100:- For PR #125-style review follow-through, the reliable closeout gate became `./gradlew ktlintCheck detekt lintDebug` plus `./gradlew pixel2api33DebugAndroidTest -Pandroid.testInstrumentationRunnerArguments.annotation=com.yorvana.testsupport.tiers.RegressionFull`; the final passing run finished 16 tests with 0 failures on `pixel2api33` [Task 2]
103:- Related skill: skills/service-book-regression-pr-review-loop/SKILL.md [Task 1][Task 2][Task 4][Task 6]
110:- Symptom: smoke and regression filters bleed into each other. Cause: task-name or runner-arg scoping is too broad. Fix: keep managed-device scoping explicit and exact so `pixel2api33Check` stays isolated from `regressionCheck` and related tasks [Task 3][Task 4][Task 5][Task 7]
111:- Symptom: offline premium regression passes for the wrong reason. Cause: the assertion is satisfied by in-memory billing state or weak UI-only checks. Fix: relaunch offline and assert `billingManager.isPremium` or the persisted cached-premium path directly [Task 3][Task 4]
114:- Symptom: a follow-up review pass introduces extra regressions while fixing a narrow comment. Cause: the edit scope drifted beyond the specific review item. Fix: keep production/test changes tightly scoped to the comment and avoid opportunistic refactors unless the review explicitly asks for them [Task 1][Task 2]
116:- Symptom: Android test scanner misses real regression classes. Cause: trying to reflect over `androidTest` classes from `src/test`. Fix: scan source files instead and keep behavior pinned with live fixtures in `app/src/androidTest/...` [Task 5]
121:# Task Group: service-book regression planning issue review and doc reconciliation
122:scope: Review-first workflow for regression-test planning issues and docs-only PR consistency sweeps in `/home/Messier82/projects/service-book`; use when the user points at a phase issue, asks for review “the same way,” or asks for a “full sweep” rather than implementation.
123:applies_to: cwd=/home/Messier82/projects/service-book; reuse_rule=safe for similar planning-review/comment tasks in this repo, especially issues/docs/PRs around regression-test phases #114-#120; treat technical details as repo-specific.
125:## Task 1: Review regression-test phase issues #114-#120 and post issue comments, success
129:- rollout_summaries/2026-05-21T14-25-51-siN5-regression_plan_issue_review_sweep.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/21/rollout-2026-05-21T17-25-51-019e4aed-ada7-7722-8582-bb7de1defd4b.jsonl, updated_at=2026-05-22T11:33:06+00:00, thread_id=019e4aed-ada7-7722-8582-bb7de1defd4b, issue-by-issue review/comment loop across phases 1-7)
133:- gh issue view, docs/plan-regression-tests.md, regression tests, issue review, PR comment, @Smoke, DocumentFile, ProcessDeath.kill, premium_lifetime, testTagsAsResourceId, Quarantined
135:- Related skill: skills/review-regression-planning-issue/SKILL.md
137:## Task 2: Compare PR #122 and docs/plan-regression-tests.md against issues #114-#120; post final drift comments, success
141:- rollout_summaries/2026-05-21T14-25-51-siN5-regression_plan_issue_review_sweep.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/21/rollout-2026-05-21T17-25-51-019e4aed-ada7-7722-8582-bb7de1defd4b.jsonl, updated_at=2026-05-22T11:33:06+00:00, thread_id=019e4aed-ada7-7722-8582-bb7de1defd4b, final full-sweep reconciliation after PR update)
145:- gh pr view, gh pr diff, docs/plan-regression-tests.md, issue #114, issue #120, full sweep, sandbox skip guard, de-quarantine authority, authoritative source note
147:- Related skill: skills/review-regression-planning-issue/SKILL.md
153:- rollout_summaries/2026-05-21T10-43-42-ziF4-pr_113_docs_regression_plan_review_full_sweep.md (cwd=/home/Messier82/projects/service-book, rollout_path=/home/Messier82/.codex/sessions/2026/05/21/rollout-2026-05-21T13-43-42-019e4a22-4e2a-70a2-8fa1-8fc35b37ae92.jsonl, updated_at=2026-05-21T12:06:26+00:00, thread_id=019e4a22-4e2a-70a2-8fa1-8fc35b37ae92, docs-only PR review with posted findings, addressed-items check, and final sweep)
159:- Related skill: skills/review-regression-planning-issue/SKILL.md
171:- For this repo's regression-test planning docs, the authoritative source becomes the per-phase issue text once the issues and `docs/plan-regression-tests.md` diverge; the plan doc should then say so explicitly [Task 2]
173:- `app/build.gradle.kts` already uses managed-device task-name detection plus reflective runner-arg injection, so smoke-vs-regression filters must be exact task/device matches rather than broad substring checks [Task 1]
185:- Symptom: smoke or regression filters accidentally catch future tasks. Cause: broad negative filters or substring task matching. Fix: use positive `@Smoke` filtering and exact managed-device task-name matching [Task 1]


Output:
Chunk ID: 88a3e5
Wall time: 1.0008 seconds
Process running with session ID 59089
Original token count: 0
Output:


Output:
Chunk ID: 95e194
Wall time: 0.3541 seconds
Process exited with code 0
Original token count: 0
Output: