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: - ["curl"]
- ["./gradlew"]
- ["git", "add"]
- ["git", "push"]
- ["ss", "-ltnp"]
- ["git", "fetch"]
- ["git", "commit"]
- ["git", "rebase"]
- ["git", "switch"]
- ["hostname", "-I"]
- ["bundle", "install"]
- ["rm", "/home/Messier82/projects/site/assets/screenshots/vehicle-history-history-dark.png"]
- ["gh", "pr", "list"]
- ["gh", "pr", "view"]
- ["gh", "pr", "merge"]
- ["gh", "pr", "create"]
- ["gh", "issue", "view"]
- ["gh", "pr", "comment"]
- ["gh", "api", "graphql"]
- ["gh", "pr", "checkout"]
- ["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"]
- ["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"]
- ["gh", "pr", "view", "97", "--json", "number,title,headRefName,baseRefName,files,mergeStateStatus,isDraft,statusCheckRollup"]
 The writable roots are `/home/Messier82/.codex/memories`, `/home/Messier82/projects/service-book`, `/tmp`.
</permissions instructions>

<collaboration_mode># Collaboration Mode: Default

You are now in Default mode. Any previous instructions for other modes (e.g. Plan mode) are no longer active.

Your active mode changes only when new developer instructions with a different `<collaboration_mode>...</collaboration_mode>` change it; user requests or tool descriptions do not change mode by themselves. Known mode names are Default and Plan.

## request_user_input availability

Use the `request_user_input` tool only when it is listed in the available tools for this turn.

In Default mode, strongly prefer making reasonable assumptions and executing the user's request rather than stopping to ask questions. If you absolutely must ask a question because the answer cannot be discovered from local context and a reasonable assumption would be risky, ask the user directly with a concise plain-text question. Never write a multiple choice question as a textual assistant message.
</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, or generate or update marketplace entries for plugin ordering and availability metadata. (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/0d4f5414/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/0d4f5414/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/0d4f5414/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/0d4f5414/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/0d4f5414/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/0d4f5414/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/0d4f5414/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>


# 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.

## 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-21</current_date>
  <timezone>Etc/UTC</timezone>
</environment_context>


# Collaboration Mode: Default

You are now in Default mode. Any previous instructions for other modes (e.g. Plan mode) are no longer active.

Your active mode changes only when new developer instructions with a different `<collaboration_mode>...</collaboration_mode>` change it; user requests or tool descriptions do not change mode by themselves. Known mode names are Default and Plan.

## request_user_input availability

Use the `request_user_input` tool only when it is listed in the available tools for this turn.

In Default mode, strongly prefer making reasonable assumptions and executing the user's request rather than stopping to ask questions. If you absolutely must ask a question because the answer cannot be discovered from local context and a reasonable assumption would be risky, ask the user directly with a concise plain-text question. Never write a multiple choice question as a textual assistant message.

# 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.

## 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`.


Review current open github pr


I’ll inspect the open PR metadata and diff first, then read the touched files locally so the review is grounded in line-level behavior.


gh pr list --state open --json number,title,headRefName,baseRefName,isDraft,mergeStateStatus,statusCheckRollup

Do you want to query GitHub for the current open pull requests?


Output:
Chunk ID: dd7882
Wall time: 0.1243 seconds
Process exited with code 0
Original token count: 17
Output:
## implement-store-screenshots...origin/implement-store-screenshots


Output:
Chunk ID: b8b822
Wall time: 1.0010 seconds
Process running with session ID 4177
Original token count: 0
Output:


Output:
Chunk ID: 3f0ad7
Wall time: 0.0000 seconds
Process exited with code 0
Original token count: 193
Output:
[{"baseRefName":"master","headRefName":"chore/document-dependabot-workflow","isDraft":false,"mergeStateStatus":"CLEAN","number":121,"statusCheckRollup":[{"__typename":"CheckRun","completedAt":"2026-05-21T14:08:38Z","conclusion":"SKIPPED","detailsUrl":"https://github.com/yorvana/android/actions/runs/26231229341/job/77191902242","name":"ci","startedAt":"2026-05-21T14:08:38Z","status":"COMPLETED","workflowName":"CI (Manual Label)"},{"__typename":"CheckRun","completedAt":"2026-05-21T14:09:24Z","conclusion":"SUCCESS","detailsUrl":"https://github.com/yorvana/android/actions/runs/26231229340/job/77191902725","name":"Semgrep Scan","startedAt":"2026-05-21T14:08:42Z","status":"COMPLETED","workflowName":"Semgrep"}],"title":"docs: document dependabot resolution workflow"}]


There is one open PR: `#121 docs: document dependabot resolution workflow`, targeting `master`, with passing Semgrep and a skipped label-gated CI job. I’m fetching the branch and comparing it to `master` without touching the current working tree.


gh pr view 121 --json number,title,author,headRefName,baseRefName,body,files,commits,reviews,statusCheckRollup

Do you want to fetch detailed metadata for PR #121 from GitHub?


git fetch origin master chore/document-dependabot-workflow

Do you want to fetch the PR branch and base branch for local diff review?


Output:
Chunk ID: 6f0569
Wall time: 1.0005 seconds
Process running with session ID 50891
Original token count: 0
Output:


Output:
Chunk ID: 5c224f
Wall time: 1.0010 seconds
Process running with session ID 14248
Original token count: 0
Output:


Output:
Chunk ID: 93dd2d
Wall time: 1.0067 seconds
Process exited with code 0
Original token count: 907
Output:
{"author":{"id":"MDQ6VXNlcjMyODY3NzM1","is_bot":false,"login":"Mesya82","name":"Igor Vinogradov"},"baseRefName":"master","body":"This PR adds a standard workflow for agents to handle Dependabot PRs, ensuring consistent testing and style enforcement.","commits":[{"authoredDate":"2026-05-21T13:21:53Z","authors":[{"email":"mesya82@users.noreply.github.com","id":"MDQ6VXNlcjMyODY3NzM1","login":"Mesya82","name":"Mesya82"}],"committedDate":"2026-05-21T13:21:53Z","messageBody":"","messageHeadline":"docs: document dependabot resolution workflow","oid":"5445308e2e6369aa61f111a455921a68485700f2"},{"authoredDate":"2026-05-21T13:23:57Z","authors":[{"email":"mesya82@users.noreply.github.com","id":"MDQ6VXNlcjMyODY3NzM1","login":"Mesya82","name":"Mesya82"}],"committedDate":"2026-05-21T13:23:57Z","messageBody":"","messageHeadline":"docs: add step to pull latest master in dependabot workflow","oid":"d24c6ed7dd3ae7141a8fcb48984e2a24551293aa"},{"authoredDate":"2026-05-21T13:25:29Z","authors":[{"email":"mesya82@users.noreply.github.com","id":"MDQ6VXNlcjMyODY3NzM1","login":"Mesya82","name":"Mesya82"}],"committedDate":"2026-05-21T13:25:29Z","messageBody":"","messageHeadline":"docs: refine dependabot workflow to merge master into PR branch first","oid":"0e37bf8ee10ac25e56fedb2e94d3f67a1dbf4a0a"},{"authoredDate":"2026-05-21T13:26:35Z","authors":[{"email":"mesya82@users.noreply.github.com","id":"MDQ6VXNlcjMyODY3NzM1","login":"Mesya82","name":"Mesya82"}],"committedDate":"2026-05-21T13:26:35Z","messageBody":"","messageHeadline":"docs: streamline dependabot workflow to pull origin/master directly","oid":"da99b93fea1e15484f0abddb58e54918493d08ba"},{"authoredDate":"2026-05-21T13:32:49Z","authors":[{"email":"mesya82@users.noreply.github.com","id":"MDQ6VXNlcjMyODY3NzM1","login":"Mesya82","name":"Mesya82"}],"committedDate":"2026-05-21T13:32:49Z","messageBody":"","messageHeadline":"docs: include PR review procedure for fixes in dependabot workflow","oid":"a0d2a00125dfda1c44b4e43b55d68d67550a4abc"},{"authoredDate":"2026-05-21T13:50:16Z","authors":[{"email":"mesya82@users.noreply.github.com","id":"MDQ6VXNlcjMyODY3NzM1","login":"Mesya82","name":"Mesya82"}],"committedDate":"2026-05-21T13:50:16Z","messageBody":"","messageHeadline":"docs: address review comments on dependabot workflow","oid":"876fcc86fcdf645cdb9fec0b2c2d57cb21f61c53"},{"authoredDate":"2026-05-21T14:08:25Z","authors":[{"email":"mesya82@users.noreply.github.com","id":"MDQ6VXNlcjMyODY3NzM1","login":"Mesya82","name":"Mesya82"}],"committedDate":"2026-05-21T14:08:25Z","messageBody":"","messageHeadline":"docs: tighten pre-authorized fixes scope in dependabot workflow","oid":"5c513a7f31183176d1376386738ebdaeb52c895f"}],"files":[{"path":"AGENTS.md","additions":1,"deletions":1},{"path":"CLAUDE.md","additions":1,"deletions":0},{"path":"GEMINI.md","additions":1,"deletions":0},{"path":"docs/dependabot-workflow.md","additions":70,"deletions":0}],"headRefName":"chore/document-dependabot-workflow","number":121,"reviews":[],"statusCheckRollup":[{"__typename":"CheckRun","completedAt":"2026-05-21T14:08:38Z","conclusion":"SKIPPED","detailsUrl":"https://github.com/yorvana/android/actions/runs/26231229341/job/77191902242","name":"ci","startedAt":"2026-05-21T14:08:38Z","status":"COMPLETED","workflowName":"CI (Manual Label)"},{"__typename":"CheckRun","completedAt":"2026-05-21T14:09:24Z","conclusion":"SUCCESS","detailsUrl":"https://github.com/yorvana/android/actions/runs/26231229340/job/77191902725","name":"Semgrep Scan","startedAt":"2026-05-21T14:08:42Z","status":"COMPLETED","workflowName":"Semgrep"}],"title":"docs: document dependabot resolution workflow"}


Output:
Chunk ID: a70da8
Wall time: 0.0000 seconds
Process exited with code 0
Original token count: 37
Output:
From github.com:yorvana/android
 * branch            master     -> FETCH_HEAD
 * branch            chore/document-dependabot-workflow -> FETCH_HEAD


The PR only changes repository guidance and adds a new Dependabot workflow doc. I’m reading the exact diff plus the surrounding doc context to catch process-level contradictions rather than code defects.


git diff --stat origin/master...origin/chore/document-dependabot-workflow


git diff --find-renames --find-copies origin/master...origin/chore/document-dependabot-workflow


Output:
Chunk ID: ec783c
Wall time: 0.3033 seconds
Process exited with code 0
Original token count: 60
Output:
 AGENTS.md                   |  2 +-
 CLAUDE.md                   |  1 +
 GEMINI.md                   |  1 +
 docs/dependabot-workflow.md | 70 +++++++++++++++++++++++++++++++++++++++++++++
 4 files changed, 73 insertions(+), 1 deletion(-)


Output:
Chunk ID: 0e1990
Wall time: 0.2779 seconds
Process exited with code 0
Original token count: 1543
Output:
diff --git a/AGENTS.md b/AGENTS.md
index d28148c..e8718d3 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -24,7 +24,7 @@ Use JUnit 4, Robolectric, MockK, Truth, Turbine, Compose UI tests, and Roborazzi

 ## 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.
+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

diff --git a/CLAUDE.md b/CLAUDE.md
index 491166e..6aa5d21 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -83,5 +83,6 @@ A test **must** stay in `src/androidTest` if it uses `ActivityScenario`, `create

 - `GEMINI.md` — project overview and tech stack
 - `TESTING_SETUP.md` — detailed GMD/GPU setup and Robolectric migration checklist
+- `docs/dependabot-workflow.md` — Dependabot resolution process for agents
 - `docs/adr.md` — architectural decisions (ADR-001 through ADR-013)
 - `docs/specs.md` — functional requirements and acceptance criteria
diff --git a/GEMINI.md b/GEMINI.md
index 8e4bb7d..adcdc7c 100644
--- a/GEMINI.md
+++ b/GEMINI.md
@@ -70,3 +70,4 @@ The project follows a standard MVVM (Model-ViewModel-View) pattern combined with
 ## 🔗 Key Documentation
 - `docs/specs.md`: Detailed functional requirements and acceptance criteria.
 - `docs/adr.md`: Architectural Decision Records explaining the "why" behind key technical choices.
+- `docs/dependabot-workflow.md`: Standard procedure for resolving Dependabot PRs.
diff --git a/docs/dependabot-workflow.md b/docs/dependabot-workflow.md
new file mode 100644
index 0000000..4b11701
--- /dev/null
+++ b/docs/dependabot-workflow.md
@@ -0,0 +1,70 @@
+# Dependabot Resolution Workflow for Agents
+
+This document outlines the standard procedure for an AI agent to handle Dependabot pull requests in the Yorvana project.
+
+## Workflow Overview
+
+Dependabot updates should be processed one at a time to ensure stability and avoid dependency conflicts. The goal is to verify that the update does not break JVM tests, end-to-end smoke tests, or code style/linting rules.
+
+### 1. Identify Open PRs
+Use the GitHub CLI to list open Dependabot PRs:
+```bash
+gh pr list --author "app/dependabot"
+```
+
+### 2. Process Each PR
+For each PR, follow these steps:
+
+#### A. Checkout the PR Branch
+```bash
+gh pr checkout <PR_ID>
+```
+
+#### B. Integrate Latest Upstream Master
+Pull the latest changes from `origin/master` directly into the PR branch. This ensures you are testing against the absolute latest codebase and resolves potential conflicts before validation begins:
+```bash
+git fetch origin master && git merge origin/master
+```
+*Note: If there are conflicts, resolve them manually before proceeding to testing.*
+
+#### C. Run JVM Tests
+Run the fast unit and Robolectric tests:
+```bash
+./gradlew test
+```
+
+#### D. Run Smoke Tests (with GPU Acceleration)
+Verify core user journeys on a real Android environment using a Gradle Managed Device (GMD).
+**Always use GPU acceleration (`host` mode) for speed and fidelity:**
+```bash
+./gradlew pixel2api33Check -Pandroid.testoptions.manageddevices.emulator.gpu=host
+```
+*Note: If `host` mode fails due to environment restrictions, fallback to `angle_indirect`.*
+
+#### E. Verify Code Style and Linting
+Ensure the update didn't trigger new lint, formatting, or static analysis issues (common with `ktlint` or Android lint changes):
+```bash
+./gradlew lintDebug ktlintCheck detekt
+```
+If violations are found, fix them (e.g., using `./gradlew ktlintFormat`) and commit the changes.
+
+#### F. Handling Failures and Fixes
+If the build fails, tests fail, or code quality checks require manual fixes:
+1.  **Apply Fixes:** Implement the necessary code changes to resolve the issue.
+2.  **Commit and Push:** Commit your fixes and push them to the PR branch.
+3.  **Wait for Review:** Notify the user via **terminal output** that fixes were required. You **must** wait for the standard PR review process and for the PR to be merged before proceeding to the next Dependabot update.
+
+#### G. Merge the PR
+If all tests pass and no manual fixes were required (or style fixes were purely automatic/trivial):
+```bash
+gh pr merge --squash --delete-branch
+```
+
+## Best Practices for Agents
+
+- **Sequential Execution:** Never merge multiple Dependabot PRs simultaneously. Always verify on the latest upstream state.
+- **Upstream First:** Always merge `origin/master` into your PR branch before running any tests.
+- **Pre-authorized Fixes:** For Dependabot PRs, the agent is pre-authorized to commit and push mechanical auto-fixes (e.g., the output of `./gradlew ktlintFormat`) directly to the PR branch without per-action approval. Any manual code edits or logical changes—even those needed to resolve `lintDebug` or `detekt` violations—must follow the Step F workflow (commit, push, and wait for manual review).
+- **No Concurrent Work:** If a PR requires manual intervention and review, stop and wait. Do not start on the next PR until the current one is merged.
+- **GPU Acceleration:** Smoke tests are significantly faster with `-Pandroid.testoptions.manageddevices.emulator.gpu=host`.
+- **Validation is Key:** Never merge a Dependabot PR without running the full suite: JVM tests, smoke tests, and all code quality checks (`lintDebug`, `ktlintCheck`, `detekt`).


Output:
Chunk ID: 058d51
Wall time: 0.2969 seconds
Process exited with code 0
Original token count: 4978
Output:
GEMINI.md
CLAUDE.md
AGENTS.md
TESTING_SETUP.md
distribution/store-listing.md
gradle.properties
distribution/store-assets/screenshots/tablet-7/screen_06_paywall_dialog.png
distribution/store-assets/screenshots/tablet-7/screen_05_settings_privacy.png
distribution/store-assets/screenshots/tablet-7/screen_04_categories.png
distribution/store-assets/screenshots/tablet-7/screen_03_add_record.png
distribution/store-assets/screenshots/tablet-7/screen_02_vehicle_detail.png
distribution/store-assets/screenshots/tablet-7/screen_01_vehicle_list.png
sample-vault/generate.py
settings.gradle.kts
sample-vault/README.md
gradlew.bat
gradlew
distribution/store-assets/screenshots/tablet-10/screen_06_paywall_dialog.png
distribution/store-assets/screenshots/tablet-10/screen_05_settings_privacy.png
distribution/store-assets/screenshots/tablet-10/screen_04_categories.png
distribution/store-assets/screenshots/tablet-10/screen_03_add_record.png
distribution/store-assets/screenshots/tablet-10/screen_02_vehicle_detail.png
distribution/store-assets/screenshots/tablet-10/screen_01_vehicle_list.png
gradle/libs.versions.toml
distribution/store-assets/screenshots/phone/screen_06_paywall_dialog.png
distribution/store-assets/screenshots/phone/screen_05_settings_privacy.png
distribution/store-assets/screenshots/phone/screen_04_categories.png
distribution/store-assets/screenshots/phone/screen_03_add_record.png
distribution/store-assets/screenshots/phone/screen_02_vehicle_detail.png
distribution/store-assets/screenshots/phone/screen_01_vehicle_list.png
distribution/whatsnew/whatsnew-en-US
distribution/whatsnew/README.md
build.gradle.kts
gradle/wrapper/gradle-wrapper.jar
gradle/wrapper/gradle-wrapper.properties
docs/plan-paywall.md
docs/specs.md
docs/plan-integration-tests-restructure.md
docs/adr.md
docs/adr-011-navigation-transitions.md
docs/privacy-policy.md
docs/plan-smoke-tests.md
docs/sentry-setup.md
app/detekt-baseline.xml
app/build.gradle.kts
app/proguard-rules.pro
app/lint-baseline.xml
app/keystore.properties.template
config/detekt/detekt.yml
app/coverage-baselines/gmd_smoke.ec
app/src/main/java/com/yorvana/YorvanaApplication.kt
app/src/main/java/com/yorvana/MainActivity.kt
app/src/main/AndroidManifest.xml
app/src/main/res/values-night/themes.xml
app/src/main/java/com/yorvana/util/VaultPathHelper.kt
app/src/main/java/com/yorvana/util/DateFormatter.kt
app/src/main/java/com/yorvana/util/UuidGenerator.kt
app/src/main/java/com/yorvana/util/SentryWrapper.kt
app/src/main/java/com/yorvana/util/SentryInitParams.kt
app/src/main/java/com/yorvana/util/FileProviderHelper.kt
app/src/main/java/com/yorvana/util/CrashReporter.kt
app/src/main/res/values/strings.xml
app/src/main/res/values/themes.xml
app/src/main/res/values/colors.xml
app/src/main/java/com/yorvana/domain/model/VehicleWithMeta.kt
app/src/main/java/com/yorvana/domain/model/RecordWithCategory.kt
app/src/main/res/drawable/ic_launcher_monochrome.xml
app/src/main/java/com/yorvana/domain/AppGate.kt
app/src/main/res/drawable/ic_launcher_foreground.xml
app/src/main/res/drawable/ic_launcher_background.xml
app/src/main/java/com/yorvana/ui/TestTags.kt
app/src/androidTest/assets/screenshots-fixture/vehicles/2019-honda-civic/vehicle.json
app/src/main/res/mipmap-anydpi-v26/ic_launcher_round.xml
app/src/test/java/com/yorvana/util/FileProviderHelperTest.kt
app/src/main/res/mipmap-anydpi-v26/ic_launcher.xml
app/src/test/java/com/yorvana/util/DateFormatterTest.kt
app/src/test/java/com/yorvana/util/CrashReporterTest.kt
app/src/test/java/com/yorvana/util/VaultPathHelperTest.kt
app/src/test/java/com/yorvana/util/UuidGeneratorTest.kt
app/src/test/java/com/yorvana/util/SentryWrapperTest.kt
app/src/main/java/com/yorvana/ui/vehicles/VehicleListViewModel.kt
app/src/main/java/com/yorvana/ui/vehicles/AddEditVehicleViewModel.kt
app/src/main/java/com/yorvana/ui/vehicles/VehiclePreview.kt
app/src/main/java/com/yorvana/ui/vehicles/VehicleListScreen.kt
app/src/main/java/com/yorvana/ui/vehicles/AddEditVehicleScreen.kt
app/src/main/java/com/yorvana/ui/settings/SettingsViewModel.kt
app/src/main/java/com/yorvana/ui/settings/CategoriesViewModel.kt
app/src/main/java/com/yorvana/ui/settings/SettingsScreen.kt
app/src/main/java/com/yorvana/ui/settings/CategoriesScreen.kt
app/src/main/res/xml/file_provider_paths.xml
app/src/test/java/com/yorvana/MainActivityTest.kt
app/src/test/java/com/yorvana/LocalOnly.kt
app/src/test/java/com/yorvana/TestYorvanaApplication.kt
app/src/test/java/com/yorvana/YorvanaApplicationTest.kt
app/src/androidTest/assets/screenshots-fixture/vehicles/2019-honda-civic/records/2025-07-15-coolant-flush.json
app/src/androidTest/assets/screenshots-fixture/vehicles/2019-honda-civic/records/2025-04-02-battery.json
app/src/androidTest/assets/screenshots-fixture/vehicles/2019-honda-civic/records/2025-01-18-mot.json
app/src/androidTest/assets/screenshots-fixture/vehicles/2019-honda-civic/records/2024-09-21-tyre-rotation.json
app/src/androidTest/assets/screenshots-fixture/vehicles/2019-honda-civic/records/2024-06-04-brake-pads.json
app/src/androidTest/assets/screenshots-fixture/vehicles/2019-honda-civic/records/2024-03-12-oil-change.json
app/src/androidTest/assets/screenshots-fixture/categories.json
app/src/androidTest/assets/test_receipt.jpg
app/src/main/java/com/yorvana/ui/util/ViewModelFactory.kt
app/src/main/java/com/yorvana/ui/util/EmailLaunchRequest.kt
app/src/main/java/com/yorvana/ui/util/ViewModelDependencies.kt
app/src/main/java/com/yorvana/ui/util/GatedViewModel.kt
app/src/main/java/com/yorvana/ui/util/ContextExtensions.kt
app/src/main/java/com/yorvana/ui/util/BillingUIUtils.kt
app/src/test/java/com/yorvana/domain/AppGateTest.kt
app/src/test/java/com/yorvana/data/storage/VaultStorageImplIT.kt
app/src/test/java/com/yorvana/data/storage/VaultStorageImplTest.kt
app/src/test/java/com/yorvana/data/storage/MigrationHelperTest.kt
app/src/test/java/com/yorvana/ui/vehicles/AddEditVehicleScreenshotTest.kt
app/src/test/java/com/yorvana/ui/vehicles/AddEditVehicleScreenIT.kt
app/src/main/java/com/yorvana/ui/reportbug/ReportBugViewModel.kt
app/src/test/java/com/yorvana/ui/vehicles/AddEditVehicleScreenTest.kt
app/src/main/java/com/yorvana/ui/reportbug/ReportBugScreen.kt
app/src/main/java/com/yorvana/ui/reportbug/DeviceInfoDialog.kt
app/src/main/java/com/yorvana/data/storage/VaultStorageImpl.kt
app/src/main/java/com/yorvana/ui/theme/Type.kt
app/src/main/java/com/yorvana/ui/navigation/Screen.kt
app/src/main/java/com/yorvana/ui/navigation/AppNavGraph.kt
app/src/main/java/com/yorvana/data/storage/VaultStorage.kt
app/src/main/java/com/yorvana/data/storage/MigrationHelper.kt
app/src/test/java/com/yorvana/data/repository/WorkflowIntegrationIT.kt
app/src/test/java/com/yorvana/data/repository/VehicleRepositoryImplTest.kt
app/src/test/java/com/yorvana/data/repository/RecordRepositoryImplTest.kt
app/src/test/java/com/yorvana/data/repository/DataIntegrationIT.kt
app/src/test/java/com/yorvana/data/repository/CategoryRepositoryImplTest.kt
app/src/main/java/com/yorvana/ui/theme/Theme.kt
app/src/main/java/com/yorvana/ui/theme/Color.kt
app/src/androidTest/java/com/yorvana/SmokeTest.kt
app/src/test/java/com/yorvana/ui/util/EmailLaunchRequestTest.kt
app/src/test/java/com/yorvana/ui/util/ViewModelFactoryTest.kt
app/src/test/java/com/yorvana/ui/util/ViewModelDependenciesExt.kt
app/src/test/java/com/yorvana/ui/util/ContextExtensionsTest.kt
app/src/test/java/com/yorvana/ui/util/BaseScreenshotTest.kt
app/src/test/java/com/yorvana/ui/vehicles/snapshots/AddEditVehicleScreen_add_dark.png
app/src/main/java/com/yorvana/ui/records/VehicleDetailViewModel.kt
app/src/test/java/com/yorvana/data/preferences/AppPreferencesImplTest.kt
app/src/test/java/com/yorvana/ui/vehicles/snapshots/AddEditVehicleScreen_add_light.png
app/src/test/java/com/yorvana/ui/vehicles/snapshots/AddEditVehicleScreen_edit_dark.png
app/src/test/java/com/yorvana/ui/vehicles/snapshots/VehicleListScreen_list_dark.png
app/src/test/java/com/yorvana/ui/vehicles/snapshots/AddEditVehicleScreen_edit_light.png
app/src/test/java/com/yorvana/ui/vehicles/snapshots/VehicleListScreen_list_light.png
app/src/androidTest/java/com/yorvana/testsupport/DemoMode.kt
app/src/test/java/com/yorvana/ui/vehicles/snapshots/VehicleListScreen_readOnly_light.png
app/src/androidTest/java/com/yorvana/testsupport/VaultTestSetup.kt
app/src/test/java/com/yorvana/ui/vehicles/snapshots/VehicleListScreen_empty_dark.png
app/src/test/java/com/yorvana/ui/vehicles/snapshots/VehicleListScreen_readOnly_dark.png
app/src/test/java/com/yorvana/ui/vehicles/snapshots/VehicleListScreen_empty_light.png
app/src/androidTest/java/com/yorvana/testsupport/ScreenshotConstants.kt
app/src/androidTest/java/com/yorvana/testsupport/ComposeWaitHelpers.kt
app/src/test/java/com/yorvana/ui/vehicles/VehicleListViewModelTest.kt
app/src/test/java/com/yorvana/ui/settings/SettingsScreenshotTest.kt
app/src/test/java/com/yorvana/ui/settings/CategoriesScreenTest.kt
app/src/test/java/com/yorvana/ui/settings/SettingsViewModelTest.kt
app/src/test/java/com/yorvana/ui/settings/SettingsScreenIT.kt
app/src/main/java/com/yorvana/data/repository/VehicleRepositoryImpl.kt
app/src/main/java/com/yorvana/data/repository/RecordRepositoryImpl.kt
app/src/test/java/com/yorvana/ui/vehicles/VehicleListScreenshotTest.kt
app/src/main/java/com/yorvana/data/repository/CategoryRepositoryImpl.kt
app/src/main/java/com/yorvana/data/repository/VehicleRepository.kt
app/src/test/java/com/yorvana/ui/vehicles/VehicleListScreenIT.kt
app/src/main/java/com/yorvana/data/repository/RecordRepository.kt
app/src/test/java/com/yorvana/ui/vehicles/VehicleListConsentDialogTest.kt
app/src/main/java/com/yorvana/data/repository/CategoryRepository.kt
app/src/test/java/com/yorvana/ui/vehicles/AddEditVehicleViewModelTest.kt
app/src/main/java/com/yorvana/ui/records/VehicleDetailScreen.kt
app/src/test/java/com/yorvana/ui/vehicles/AddEditVehicleViewModelIT.kt
app/src/main/java/com/yorvana/ui/records/RecordDetailViewModel.kt
app/src/main/java/com/yorvana/ui/records/PerformerUtil.kt
app/src/main/java/com/yorvana/ui/records/ImageViewerScreen.kt
app/src/main/java/com/yorvana/ui/components/MakePickerDialog.kt
app/src/main/java/com/yorvana/ui/records/AddEditRecordViewModel.kt
app/src/main/java/com/yorvana/ui/components/UpgradeDialog.kt
app/src/main/java/com/yorvana/ui/records/AddEditRecordScreen.kt
app/src/main/java/com/yorvana/ui/components/TopBarBackButton.kt
app/src/main/java/com/yorvana/ui/components/ShimmerBrush.kt
app/src/main/java/com/yorvana/ui/records/RecordDetailScreen.kt
app/src/main/java/com/yorvana/ui/components/RequiredLabel.kt
app/src/main/java/com/yorvana/ui/components/PrivacyPolicyDialog.kt
app/src/main/java/com/yorvana/ui/components/PrivacyPolicyContent.kt
app/src/main/java/com/yorvana/ui/components/PaywallStatusCard.kt
app/src/main/java/com/yorvana/ui/components/PaywallScaffold.kt
app/src/androidTest/java/com/yorvana/screenshots/StoreScreenshotBase.kt
app/src/androidTest/java/com/yorvana/screenshots/StoreScreenshotTest.kt
app/src/main/java/com/yorvana/ui/components/PaywallInfoSheet.kt
app/src/main/java/com/yorvana/ui/components/ExpandablePrivacyDisclosure.kt
app/src/main/java/com/yorvana/ui/components/ErrorListItem.kt
app/src/main/java/com/yorvana/ui/components/EmptyStateView.kt
app/src/main/java/com/yorvana/ui/components/CurrencyPickerDialog.kt
app/src/main/java/com/yorvana/ui/components/ConfirmDeleteDialog.kt
app/src/main/java/com/yorvana/ui/components/ChromeLikeMenu.kt
app/src/main/java/com/yorvana/ui/components/AttachmentThumbnail.kt
app/src/main/java/com/yorvana/ui/components/AttachmentChip.kt
app/src/test/java/com/yorvana/data/billing/FakeBillingManager.kt
app/src/test/java/com/yorvana/ui/settings/CategoriesScreenshotTest.kt
app/src/test/java/com/yorvana/ui/settings/CategoriesScreenIT.kt
app/src/test/java/com/yorvana/ui/records/RecordDetailViewModelTest.kt
app/src/main/java/com/yorvana/data/preferences/DebugBillingOverrideMode.kt
app/src/test/java/com/yorvana/ui/records/RecordDetailViewModelIT.kt
app/src/test/java/com/yorvana/ui/records/AddEditRecordViewModelTest.kt
app/src/test/java/com/yorvana/ui/records/AddEditRecordScreenTest.kt
app/src/test/java/com/yorvana/ui/records/AddEditRecordScreenIT.kt
app/src/main/java/com/yorvana/data/preferences/AppPreferencesImpl.kt
app/src/main/java/com/yorvana/data/preferences/AppPreferences.kt
app/src/test/java/com/yorvana/ui/records/RecordDetailScreenshotTest.kt
app/src/test/java/com/yorvana/ui/records/RecordDetailScreenIT.kt
app/src/test/java/com/yorvana/ui/records/ImageViewerScreenshotTest.kt
app/src/test/java/com/yorvana/ui/records/AddEditRecordScreenshotTest.kt
app/src/test/java/com/yorvana/ui/records/VehicleDetailScreenTest.kt
app/src/test/java/com/yorvana/ui/records/VehicleDetailScreenIT.kt
app/src/test/java/com/yorvana/ui/records/VehicleDetailScreenshotTest.kt
app/src/test/java/com/yorvana/ui/records/VehicleDetailViewModelTest.kt
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_premium_light.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_validating_light.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_light.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_debug_crash_section_light.png
app/src/test/java/com/yorvana/ui/settings/snapshots/CategoriesScreen_add_dialog.png
app/src/test/java/com/yorvana/ui/settings/snapshots/CategoriesScreen_light.png
app/src/test/java/com/yorvana/ui/settings/snapshots/CategoriesScreen_dark.png
app/src/test/java/com/yorvana/ui/settings/SettingsViewModelIT.kt
app/src/test/java/com/yorvana/ui/settings/CategoriesViewModelTest.kt
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_debug_crash_section_dark.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_conflict_light.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_dark.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_existing_vault_light.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_premium_dark.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_privacy_dialog.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_crash_reporting_on_light.png
app/src/test/java/com/yorvana/ui/settings/snapshots/SettingsScreen_privacy_section_light.png
app/src/main/java/com/yorvana/data/model/ServiceRecord.kt
app/src/main/java/com/yorvana/data/model/AttachmentMeta.kt
app/src/main/java/com/yorvana/data/model/Vehicle.kt
app/src/main/java/com/yorvana/data/model/Category.kt
app/src/main/java/com/yorvana/data/model/WorkItem.kt
app/src/test/java/com/yorvana/ui/components/PaywallStatusCardScreenshotTest.kt
app/src/test/java/com/yorvana/ui/components/PaywallScaffoldScreenshotTest.kt
app/src/test/java/com/yorvana/ui/components/PaywallInfoSheetScreenshotTest.kt
app/src/test/java/com/yorvana/ui/components/ComponentScreenshotTest.kt
app/src/test/java/com/yorvana/ui/components/UpgradeDialogTest.kt
app/src/test/java/com/yorvana/ui/components/UpgradeDialogScreenshotTest.kt
app/src/test/java/com/yorvana/ui/components/RequiredLabelTest.kt
app/src/test/java/com/yorvana/ui/navigation/SetupScreenshotTest.kt
app/src/test/java/com/yorvana/ui/navigation/SetupScreenTest.kt
app/src/main/java/com/yorvana/data/billing/BillingResults.kt
app/src/main/java/com/yorvana/data/billing/BillingManagerImpl.kt
app/src/main/java/com/yorvana/data/billing/BillingClientProvider.kt
app/src/main/java/com/yorvana/data/billing/DebugBillingOverride.kt
app/src/main/java/com/yorvana/data/billing/DebugBillingActions.kt
app/src/main/java/com/yorvana/data/billing/BillingManager.kt
app/src/test/java/com/yorvana/ui/records/snapshots/VehicleDetailScreen_light.png
app/src/test/java/com/yorvana/ui/records/snapshots/VehicleDetailScreen_menu_dark.png
app/src/test/java/com/yorvana/ui/records/snapshots/VehicleDetailScreen_menu_light.png
app/src/test/java/com/yorvana/ui/records/snapshots/VehicleDetailScreen_dark.png
app/src/test/java/com/yorvana/ui/records/snapshots/RecordDetailScreen_dark.png
app/src/test/java/com/yorvana/ui/records/snapshots/RecordDetailScreen_light.png
app/src/test/java/com/yorvana/ui/records/snapshots/ImageViewerScreen.png
app/src/test/java/com/yorvana/ui/records/snapshots/AddEditRecordScreen_add_light.png
app/src/test/java/com/yorvana/ui/records/snapshots/AddEditRecordScreen_custom_task_dialog.png
app/src/test/java/com/yorvana/ui/records/snapshots/AddEditRecordScreen_add_dark.png
app/src/test/java/com/yorvana/ui/records/snapshots/AddEditRecordScreen_edit_dark.png
app/src/test/java/com/yorvana/ui/records/snapshots/AddEditRecordScreen_edit_light.png
app/src/test/java/com/yorvana/ui/reportbug/ReportBugScreenshotTest.kt
app/src/test/java/com/yorvana/ui/reportbug/ReportBugScreenTest.kt
app/src/test/java/com/yorvana/ui/reportbug/ReportBugViewModelTest.kt
app/src/test/java/com/yorvana/ui/components/snapshots/ChromeLikeMenu.png
app/src/test/java/com/yorvana/ui/components/snapshots/AttachmentChip_deletable.png
app/src/test/java/com/yorvana/ui/components/snapshots/EmptyStateView_dark.png
app/src/test/java/com/yorvana/ui/components/snapshots/RequiredLabel_default.png
app/src/test/java/com/yorvana/ui/components/snapshots/CurrencyPickerDialog.png
app/src/test/java/com/yorvana/ui/components/snapshots/AttachmentChip_readOnly.png
app/src/test/java/com/yorvana/ui/components/snapshots/MakePickerDialog.png
app/src/test/java/com/yorvana/ui/components/snapshots/ErrorListItem_light.png
app/src/test/java/com/yorvana/ui/components/snapshots/AttachmentThumbnail_noUri.png
app/src/test/java/com/yorvana/ui/components/snapshots/CustomCurrencyDialog.png
app/src/test/java/com/yorvana/ui/components/snapshots/ConfirmDeleteDialog.png
app/src/test/java/com/yorvana/ui/navigation/snapshots/SetupScreen_step2_sentry_off.png
app/src/test/java/com/yorvana/ui/navigation/snapshots/SetupScreen_step2_sentry_privacy_dialog.png
app/src/test/java/com/yorvana/ui/navigation/snapshots/SetupScreen_step1_folder.png
app/src/test/java/com/yorvana/ui/navigation/snapshots/SetupScreen_step2_with_topbar.png
app/src/test/java/com/yorvana/ui/navigation/snapshots/SetupScreen_step2_sentry_on.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallInfoSheet_pending_light.png
app/src/test/java/com/yorvana/ui/components/snapshots/RequiredLabel.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallScaffold_noSheet_dark.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallInfoSheet_readOnly_light.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallScaffold_noSheet_light.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallInfoSheet_pending_dark.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallInfoSheet_readOnly_dark.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallStatusCard_readOnly_dark.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallStatusCard_readOnly_light.png
app/src/test/java/com/yorvana/ui/components/snapshots/UpgradeDialog_light.png
app/src/test/java/com/yorvana/ui/components/snapshots/UpgradeDialog_dark.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallStatusCard_pending_dark.png
app/src/test/java/com/yorvana/ui/components/snapshots/PaywallStatusCard_pending_light.png
app/src/test/java/com/yorvana/ui/components/snapshots/EmptyStateView_light.png
app/src/test/java/com/yorvana/ui/reportbug/snapshots/ReportBugScreen_disclosure_light.png
app/src/test/java/com/yorvana/ui/reportbug/snapshots/ReportBugScreen_device_info_dialog_light.png
app/src/test/java/com/yorvana/ui/reportbug/snapshots/ReportBugScreen_filled_dark.png
app/src/test/java/com/yorvana/ui/reportbug/snapshots/ReportBugScreen_empty_light.png
app/src/test/java/com/yorvana/ui/reportbug/snapshots/ReportBugScreen_submitting_light.png
app/src/test/java/com/yorvana/ui/reportbug/snapshots/ReportBugScreen_invalid_email_dark.png
app/src/test/java/com/yorvana/ui/reportbug/snapshots/ReportBugScreen_invalid_email_light.png


rg "pixel2api33|verifyWithCoverage|testDebugUnitTest|ktlintCheck|detekt|lintDebug|manageddevices" -n AGENTS.md CLAUDE.md GEMINI.md TESTING_SETUP.md build.gradle.kts app/build.gradle.kts gradle.properties docs


Output:
Chunk ID: d5b334
Wall time: 0.2648 seconds
Process exited with code 0
Original token count: 1912
Output:
gradle.properties:15:android.testoptions.manageddevices.emulator.gpu=host
build.gradle.kts:7:    alias(libs.plugins.detekt) apply false
build.gradle.kts:12:    setHooks(mapOf("pre-commit" to "ktlintCheck detekt lintDebug"))
app/build.gradle.kts:15:    alias(libs.plugins.detekt)
app/build.gradle.kts:38:            it.contains("verifyWithCoverage", ignoreCase = true) ||
app/build.gradle.kts:134:                create<com.android.build.api.dsl.ManagedVirtualDevice>("pixel2api33") {
app/build.gradle.kts:177:detekt {
app/build.gradle.kts:178:    config.setFrom(rootProject.file("config/detekt/detekt.yml"))
app/build.gradle.kts:184:    dependsOn("lintDebug")
app/build.gradle.kts:198:                name.contains("pixel2api33", ignoreCase = true) -> "pixel2api33"
app/build.gradle.kts:239:                        taskName.contains("pixel2api33", ignoreCase = true) -> {
app/build.gradle.kts:257:    val smokeTask = "pixel2api33DebugAndroidTest"
app/build.gradle.kts:260:    from(layout.buildDirectory.dir("outputs/managed_device_code_coverage/debug/pixel2api33")) {
app/build.gradle.kts:372:tasks.register<JacocoReport>("verifyWithCoverage") {
app/build.gradle.kts:377:    dependsOn("testDebugUnitTest")
GEMINI.md:9:- **Run All Tests & Coverage**: `./gradlew verifyWithCoverage`
AGENTS.md:5: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/`.
AGENTS.md:10:- `./gradlew testDebugUnitTest`: run JVM unit, Robolectric, and local Compose tests.
AGENTS.md:11:- `./gradlew ktlintCheck detekt lintDebug`: run formatting, static analysis, and Android lint checks used by the pre-commit hook.
AGENTS.md:14:- `./gradlew pixel2api33DebugAndroidTest`: run instrumented tests on the managed Pixel 2 API 33 device.
AGENTS.md:15:- `./gradlew verifyWithCoverage -Pcoverage`: generate combined JVM and smoke-test coverage reports.
AGENTS.md:19: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`.
AGENTS.md:31: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`.
CLAUDE.md:17:./gradlew testDebugUnitTest --tests "com.yorvana.path.ClassName.testMethodName"
CLAUDE.md:25:./gradlew pixel2api33Check
CLAUDE.md:28:./gradlew verifyWithCoverage
CLAUDE.md:31:./gradlew lintDebug ktlintCheck detekt
TESTING_SETUP.md:27:./gradlew pixel2api33Check
TESTING_SETUP.md:35:- **GPU mode**: Set via `android.testoptions.manageddevices.emulator.gpu` in `gradle.properties` (see below).
TESTING_SETUP.md:96:| **CI (GitHub Actions, ubuntu-latest)** | `swiftshader_indirect` | SwiftShader | Overridden at runtime via `-Pandroid.testoptions.manageddevices.emulator.gpu=swiftshader_indirect` |
TESTING_SETUP.md:102:./gradlew pixel2api33Check -Pandroid.testoptions.manageddevices.emulator.gpu=host
TESTING_SETUP.md:116:  run: ./gradlew verifyWithCoverage -Pandroid.testoptions.manageddevices.emulator.gpu=swiftshader_indirect -Proborazzi.test.verify=true -Pcoverage --info
TESTING_SETUP.md:212:./gradlew pixel2api33DebugAndroidTest
TESTING_SETUP.md:215:./gradlew pixel2api33Check
TESTING_SETUP.md:238:./gradlew verifyWithCoverage
TESTING_SETUP.md:241:Since `app/coverage-baselines/*.ec` is tracked via Git LFS, a fresh clone can contain only an LFS pointer; `verifyWithCoverage` will fail until `git lfs pull` is run.
TESTING_SETUP.md:245:**`verifyWithCoverage` fails with "Coverage baseline is a Git LFS pointer"**
TESTING_SETUP.md:252:**`verifyWithCoverage` fails with "No dynamic JaCoCo execution data files were found"**
TESTING_SETUP.md:255:./gradlew testDebugUnitTest -Pcoverage
TESTING_SETUP.md:256:./gradlew verifyWithCoverage
docs/plan-paywall.md:133:- `./gradlew assembleDebug ktlintCheck detekt test` all green.
docs/plan-paywall.md:533:- `./gradlew lintDebug ktlintCheck detekt test verifyRoborazziDebug` green.
docs/plan-paywall.md:620:- `./gradlew verifyWithCoverage` → confirm paywall scenarios contribute coverage to `BillingManagerImpl`, `AppGate`, `PaywallScaffold` paths.
docs/plan-paywall.md:625:- `./gradlew pixel2api33Check` green (full smoke suite, S01–S20).
docs/plan-integration-tests-restructure.md:40:   - Depend on `pixel2api33DebugAndroidTest`.
docs/plan-integration-tests-restructure.md:44:3. **Coverage Aggregation**: Update the existing `verifyWithCoverage` task:
docs/plan-integration-tests-restructure.md:45:   - Remove its dependency on `pixel2api33DebugAndroidTest`.
docs/plan-integration-tests-restructure.md:47:   - **Local caveat:** After this change, running `verifyWithCoverage` locally will use whichever `.ec` file is checked out in LFS. If it is stale or missing, coverage from GMD tests will be absent or inaccurate. Developers who need fresh GMD coverage locally should run `generateGmdCoverage` first.
docs/plan-integration-tests-restructure.md:62:3. **Local Verification**: Locally run `./gradlew testDebugUnitTest` and fix any Robolectric specific issues, missing configuration, graphics mode mismatches, or flakiness. Also run `./gradlew pixel2api33DebugAndroidTest` to confirm the retained smoke coverage in `androidTest` still passes.
docs/plan-integration-tests-restructure.md:69:3. **Local Verification**: Run the canonical GMD smoke suite locally using `./gradlew pixel2api33DebugAndroidTest` to verify it passes. If other repo docs reference `./gradlew pixel2api33Check`, treat that as the broader device-specific check task; use `pixel2api33DebugAndroidTest` here when you want to run only the smoke suite itself during local validation.
docs/plan-integration-tests-restructure.md:78:   - Adjust the `./gradlew verifyWithCoverage` command to remove GMD-specific parameters (e.g., `-Pandroid.testoptions.manageddevices.emulator.gpu=swiftshader_indirect`).
docs/plan-integration-tests-restructure.md:92:- **Local Verification:** Running `./gradlew verifyWithCoverage` locally should complete quickly without booting an emulator and correctly aggregate the coverage using the `.ec` file in LFS.
docs/plan-smoke-tests.md:434:9. **Local verification:** Run `./gradlew pixel2api33DebugAndroidTest` to confirm the empty test class compiles, deploys, and the infrastructure helpers initialize without errors.
docs/plan-smoke-tests.md:517:1. **Full local run:** Run `./gradlew pixel2api33DebugAndroidTest` and confirm all 17 tests pass.
docs/plan-smoke-tests.md:520:4. **Coverage report:** Run `./gradlew verifyWithCoverage` and review the report. Confirm the smoke tests contribute meaningful coverage to areas not covered by Robolectric (Activity lifecycle, SAF integration, real filesystem paths).


Output:
Chunk ID: 97f5d5
Wall time: 0.2702 seconds
Process exited with code 0
Original token count: 905
Output:
# Dependabot Resolution Workflow for Agents

This document outlines the standard procedure for an AI agent to handle Dependabot pull requests in the Yorvana project.

## Workflow Overview

Dependabot updates should be processed one at a time to ensure stability and avoid dependency conflicts. The goal is to verify that the update does not break JVM tests, end-to-end smoke tests, or code style/linting rules.

### 1. Identify Open PRs
Use the GitHub CLI to list open Dependabot PRs:
```bash
gh pr list --author "app/dependabot"
```

### 2. Process Each PR
For each PR, follow these steps:

#### A. Checkout the PR Branch
```bash
gh pr checkout <PR_ID>
```

#### B. Integrate Latest Upstream Master
Pull the latest changes from `origin/master` directly into the PR branch. This ensures you are testing against the absolute latest codebase and resolves potential conflicts before validation begins:
```bash
git fetch origin master && git merge origin/master
```
*Note: If there are conflicts, resolve them manually before proceeding to testing.*

#### C. Run JVM Tests
Run the fast unit and Robolectric tests:
```bash
./gradlew test
```

#### D. Run Smoke Tests (with GPU Acceleration)
Verify core user journeys on a real Android environment using a Gradle Managed Device (GMD).
**Always use GPU acceleration (`host` mode) for speed and fidelity:**
```bash
./gradlew pixel2api33Check -Pandroid.testoptions.manageddevices.emulator.gpu=host
```
*Note: If `host` mode fails due to environment restrictions, fallback to `angle_indirect`.*

#### E. Verify Code Style and Linting
Ensure the update didn't trigger new lint, formatting, or static analysis issues (common with `ktlint` or Android lint changes):
```bash
./gradlew lintDebug ktlintCheck detekt
```
If violations are found, fix them (e.g., using `./gradlew ktlintFormat`) and commit the changes.

#### F. Handling Failures and Fixes
If the build fails, tests fail, or code quality checks require manual fixes:
1.  **Apply Fixes:** Implement the necessary code changes to resolve the issue.
2.  **Commit and Push:** Commit your fixes and push them to the PR branch.
3.  **Wait for Review:** Notify the user via **terminal output** that fixes were required. You **must** wait for the standard PR review process and for the PR to be merged before proceeding to the next Dependabot update.

#### G. Merge the PR
If all tests pass and no manual fixes were required (or style fixes were purely automatic/trivial):
```bash
gh pr merge --squash --delete-branch
```

## Best Practices for Agents

- **Sequential Execution:** Never merge multiple Dependabot PRs simultaneously. Always verify on the latest upstream state.
- **Upstream First:** Always merge `origin/master` into your PR branch before running any tests.
- **Pre-authorized Fixes:** For Dependabot PRs, the agent is pre-authorized to commit and push mechanical auto-fixes (e.g., the output of `./gradlew ktlintFormat`) directly to the PR branch without per-action approval. Any manual code edits or logical changes—even those needed to resolve `lintDebug` or `detekt` violations—must follow the Step F workflow (commit, push, and wait for manual review).
- **No Concurrent Work:** If a PR requires manual intervention and review, stop and wait. Do not start on the next PR until the current one is merged.
- **GPU Acceleration:** Smoke tests are significantly faster with `-Pandroid.testoptions.manageddevices.emulator.gpu=host`.
- **Validation is Key:** Never merge a Dependabot PR without running the full suite: JVM tests, smoke tests, and all code quality checks (`lintDebug`, `ktlintCheck`, `detekt`).


Output:
Chunk ID: 8fc68e
Wall time: 0.3018 seconds
Process exited with code 0
Original token count: 939
Output:
# CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

## Git Workflow

**Never commit or push changes unless explicitly asked.** Stage and review only.

## Key Commands

```bash
# Build
./gradlew assembleDebug

# JVM tests (fast — use these for most development)
./gradlew test
./gradlew testDebugUnitTest --tests "com.yorvana.path.ClassName.testMethodName"

# Screenshot tests
./gradlew recordRoborazziDebug   # update baselines
./gradlew verifyRoborazziDebug   # verify against baselines

# Instrumented tests (requires KVM; Pixel 2 API 33 via GMD)
./gradlew cleanManagedDevices    # always run before changing GPU mode
./gradlew pixel2api33Check

# Full check with coverage
./gradlew verifyWithCoverage

# Lint + code style
./gradlew lintDebug ktlintCheck detekt
```

**GPU mode for instrumented tests** (set in `gradle.properties`):
- `host` — fastest, requires KVM + GPU passthrough
- `angle_indirect` — current local default; works on kernel ≥ 6.17 (Fedora 43)
- `swiftshader_indirect` — CI default; crashes on kernel ≥ 6.17

## Architecture

MVVM + Repository. Single-activity (`MainActivity`), Jetpack Compose UI, **no DI framework** — all dependencies are wired manually in `YorvanaApplication`.

```
com.yorvana/
├── YorvanaApplication.kt   # manual DI; all deps created here as public properties
├── data/
│   ├── model/                  # plain Kotlin data classes (Vehicle, ServiceRecord, etc.)
│   ├── storage/                # VaultStorageImpl — SAF/DocumentFile file I/O
│   └── repository/             # interface + *Impl for Vehicle, Record, Category
├── domain/                     # cross-layer models: VehicleWithMeta, RecordWithCategory
└── ui/
    ├── Screen.kt / AppNavGraph.kt   # Navigation 3 routing
    └── {feature}/               # Composables + ViewModel per feature
```

**Vault layout** (user's filesystem, not app-private):
```
Yorvana/
├── categories.json
└── vehicles/{slug}/
    ├── vehicle.json            # includes denormalized recordCount + lastServiceDate
    └── records/{uuid}.json
```

Vehicle list loads are O(N vehicles) by design — record counts are denormalized into `vehicle.json` (see ADR-008).

## Test Conventions

| Suffix | Location | Runner | Use for |
|--------|----------|--------|---------|
| `*Test.kt` | `src/test` | JVM (Robolectric) | Unit + UI tests |
| `*IT.kt` | `src/test` | JVM (Robolectric) | Multi-component integration |
| `*ScreenshotTest.kt` | `src/test` | JVM (Roborazzi) | Visual regression |
| `*IT.kt` / `*Test.kt` | `src/androidTest` | Real emulator (GMD) | SAF, UiAutomator, real Activity |

All Robolectric tests inherit `NATIVE` graphics mode globally (set in `app/build.gradle.kts`). Don't add `@GraphicsMode` unless overriding.

A test **must** stay in `src/androidTest` if it uses `ActivityScenario`, `createAndroidComposeRule`, a real `ContentResolver`/`DocumentFile`, or `InstrumentationRegistry`. If it only *mocks* those, move it to `src/test`.

**ViewModel state** is driven by events (use `onEvent()`); `StateFlow` has no public setter. In VMs using `WhileSubscribed` or `combine` (like `SettingsViewModel`), internal logic MUST read state via `_state.value` because the public `state.value` may return the initial value if there are no active collectors (e.g., in a unit test before calling `collect`).

## Key Documentation

- `GEMINI.md` — project overview and tech stack
- `TESTING_SETUP.md` — detailed GMD/GPU setup and Robolectric migration checklist
- `docs/adr.md` — architectural decisions (ADR-001 through ADR-013)
- `docs/specs.md` — functional requirements and acceptance criteria


One review concern is emerging: the new workflow authorizes agent commits/pushes, while the existing Claude guidance still says never commit or push unless explicitly asked. I’m checking line numbers and whether that conflict is limited to Claude docs or present elsewhere.


git show origin/chore/document-dependabot-workflow:docs/dependabot-workflow.md | nl -ba


git show origin/chore/document-dependabot-workflow:CLAUDE.md | nl -ba


git show origin/chore/document-dependabot-workflow:AGENTS.md | nl -ba


git show origin/chore/document-dependabot-workflow:GEMINI.md | nl -ba


Output:
Chunk ID: d1e423
Wall time: 0.3374 seconds
Process exited with code 0
Original token count: 1028
Output:
     1	# Dependabot Resolution Workflow for Agents
     2
     3	This document outlines the standard procedure for an AI agent to handle Dependabot pull requests in the Yorvana project.
     4
     5	## Workflow Overview
     6
     7	Dependabot updates should be processed one at a time to ensure stability and avoid dependency conflicts. The goal is to verify that the update does not break JVM tests, end-to-end smoke tests, or code style/linting rules.
     8
     9	### 1. Identify Open PRs
    10	Use the GitHub CLI to list open Dependabot PRs:
    11	```bash
    12	gh pr list --author "app/dependabot"
    13	```
    14
    15	### 2. Process Each PR
    16	For each PR, follow these steps:
    17
    18	#### A. Checkout the PR Branch
    19	```bash
    20	gh pr checkout <PR_ID>
    21	```
    22
    23	#### B. Integrate Latest Upstream Master
    24	Pull the latest changes from `origin/master` directly into the PR branch. This ensures you are testing against the absolute latest codebase and resolves potential conflicts before validation begins:
    25	```bash
    26	git fetch origin master && git merge origin/master
    27	```
    28	*Note: If there are conflicts, resolve them manually before proceeding to testing.*
    29
    30	#### C. Run JVM Tests
    31	Run the fast unit and Robolectric tests:
    32	```bash
    33	./gradlew test
    34	```
    35
    36	#### D. Run Smoke Tests (with GPU Acceleration)
    37	Verify core user journeys on a real Android environment using a Gradle Managed Device (GMD).
    38	**Always use GPU acceleration (`host` mode) for speed and fidelity:**
    39	```bash
    40	./gradlew pixel2api33Check -Pandroid.testoptions.manageddevices.emulator.gpu=host
    41	```
    42	*Note: If `host` mode fails due to environment restrictions, fallback to `angle_indirect`.*
    43
    44	#### E. Verify Code Style and Linting
    45	Ensure the update didn't trigger new lint, formatting, or static analysis issues (common with `ktlint` or Android lint changes):
    46	```bash
    47	./gradlew lintDebug ktlintCheck detekt
    48	```
    49	If violations are found, fix them (e.g., using `./gradlew ktlintFormat`) and commit the changes.
    50
    51	#### F. Handling Failures and Fixes
    52	If the build fails, tests fail, or code quality checks require manual fixes:
    53	1.  **Apply Fixes:** Implement the necessary code changes to resolve the issue.
    54	2.  **Commit and Push:** Commit your fixes and push them to the PR branch.
    55	3.  **Wait for Review:** Notify the user via **terminal output** that fixes were required. You **must** wait for the standard PR review process and for the PR to be merged before proceeding to the next Dependabot update.
    56
    57	#### G. Merge the PR
    58	If all tests pass and no manual fixes were required (or style fixes were purely automatic/trivial):
    59	```bash
    60	gh pr merge --squash --delete-branch
    61	```
    62
    63	## Best Practices for Agents
    64
    65	- **Sequential Execution:** Never merge multiple Dependabot PRs simultaneously. Always verify on the latest upstream state.
    66	- **Upstream First:** Always merge `origin/master` into your PR branch before running any tests.
    67	- **Pre-authorized Fixes:** For Dependabot PRs, the agent is pre-authorized to commit and push mechanical auto-fixes (e.g., the output of `./gradlew ktlintFormat`) directly to the PR branch without per-action approval. Any manual code edits or logical changes—even those needed to resolve `lintDebug` or `detekt` violations—must follow the Step F workflow (commit, push, and wait for manual review).
    68	- **No Concurrent Work:** If a PR requires manual intervention and review, stop and wait. Do not start on the next PR until the current one is merged.
    69	- **GPU Acceleration:** Smoke tests are significantly faster with `-Pandroid.testoptions.manageddevices.emulator.gpu=host`.
    70	- **Validation is Key:** Never merge a Dependabot PR without running the full suite: JVM tests, smoke tests, and all code quality checks (`lintDebug`, `ktlintCheck`, `detekt`).