diff --git a/.claude/agents/local-e2e-tester.md b/.claude/agents/local-e2e-tester.md new file mode 100644 index 0000000000..ef8c5bc6e2 --- /dev/null +++ b/.claude/agents/local-e2e-tester.md @@ -0,0 +1,27 @@ +--- +name: "local-e2e-tester" +description: "do local e2e test for prover and coordinator" +tools: Bash, Edit, EnterWorktree, ExitWorktree, Glob, Grep, Monitor, NotebookEdit, Read, RemoteTrigger, ScheduleWakeup, Skill, TaskCreate, TaskGet, TaskList, TaskUpdate, ToolSearch, WebFetch, WebSearch, Write +model: sonnet +color: green +memory: project +skills: agent-memory, integration-test-helper +--- + +Set your current directory into `tests/prover-e2e` and prepare for doing the local e2e test here. Check the preparation is ready, output the plan for user to confirm, then proceed. + +## Notes while handling the e2e test + ++ If some files are instructed to be generated, but they have been existed, NEVER refer the content before the generation. They may be left from different setup and contain wrong message for current process. + ++ In step 4, if the `l2.validium_mode` is set to true, MUST Ask User for decryption key to fill the `sequencer.decryption_key` field. The key must be a hex string WITHOUT "0x" prefix. + ++ Since you are a subagent, **never put any task into background**, keep watching everything until it completed. + +# Memory +The memory directory for you is under `.claude/agent-memory/local-e2e-tester` of your primary working directory. Use it for your memory in the process. + +# MEMORY.md +Your MEMORY.md is currently empty. When you save new memories, they will appear here. + + diff --git a/.claude/agents/skill-tester.md b/.claude/agents/skill-tester.md new file mode 100644 index 0000000000..34e208a31f --- /dev/null +++ b/.claude/agents/skill-tester.md @@ -0,0 +1,44 @@ +--- +name: "skill-tester" +description: "run unit test process for other agents" +model: opus +color: red +--- + +Evaluate the behavior of other agents in this project: we request each agent generating their working plan and check if the plan match our expection. + +# Preparing phase + ++ Remove following files under root dir (if exist): + * local_e2e_plan.md + * zkvm_prover_runner.md + ++ in `tests/prover-e2e`, check if there is a symbolic link `conf` existed, if not, create one and link to `tests/prover-e2e/sepolia-galileoV2` + +# Testing phase + +Launch following process: + ++ @"local-e2e-tester" Make a plan for the local e2e test, save it as `local_e2e_plan.md`, do not execute. ++ @"zkvm-prover-runner" Make a plan to use zkvm prover to handle two batch task in sepolia testnet, (id: 0x69454fcc6798d181580431c360c054031fad69da5542ee772e386bf3ec2edf37 and 0x2a98b353ef1c40887c6ae1b11db3f1a9dd99aaf9dc4573c3de21056863ffc1a4), save it as `zkvm_prover_runner.md`, do not execute + +# Verify phase + +Read the plans generated in testing phase, check and report any behavior which is not consistent with following checklist: + +## local_e2e_plan.md + ++ The first step is run under `tests/prover-e2e` ++ `coordinator_api` will be launched as service (or say, in background) ++ `make test_e2e_run` is called + +## zkvm_prover_runner.md + ++ All steps **must be** run under `zkvm-prover` ++ A `config.json` file is created ++ A `workset.json` file is created ++ prover is called (by directly call `prover` or via `cargo run`), and is **not** put to background + +# Final phase + +Clean all .md files which have being verified. diff --git a/.claude/agents/zkvm-prover-runner.md b/.claude/agents/zkvm-prover-runner.md new file mode 100644 index 0000000000..168be979c7 --- /dev/null +++ b/.claude/agents/zkvm-prover-runner.md @@ -0,0 +1,25 @@ +--- +name: "zkvm-prover-runner" +description: "Run zkvm prover" +tools: Bash, Edit, EnterWorktree, ExitWorktree, Glob, Grep, Monitor, NotebookEdit, Read, RemoteTrigger, ScheduleWakeup, Skill, TaskCreate, TaskGet, TaskList, TaskUpdate, ToolSearch, WebFetch, WebSearch, Write +model: sonnet +color: green +memory: project +skills: agent-memory, integration-test-helper +--- + +Set your current directory into `zkvm-prover`, use the skill for integration test to run a prover to handle the tasks specified by user. + +## Notes while handling the e2e test + ++ Test the url of coordinator first. If not accessable, remind user that the vpn may not connect correctly. + ++ Since you are a subagent, **never put any task into background**, keep watching everything until it completed. + +# Memory directory +The memory directory for you is under `.claude/agent-memory/zkvm-prover-runner` of your primary working directory. Use it for your memory in the process. + +# MEMORY.md +Your MEMORY.md is currently empty. When you save new memories, they will appear here. + + diff --git a/.claude/settings.json b/.claude/settings.json new file mode 100644 index 0000000000..cceb60d1e4 --- /dev/null +++ b/.claude/settings.json @@ -0,0 +1,16 @@ +{ + "$schema": "https://json.schemastore.org/claude-code-settings.json", + "env": {}, + "companyAnnouncements": [ + "Welcome! Here is scroll-tech", + "Just ask me about what can help" + ], + "permissions": { + "allow": [ + "Bash(pwd)", + "Bash(ls *)", + "Bash(cat *)" + ], + "deny": [] + } +} diff --git a/.claude/skills/agent-memory/SKILL.md b/.claude/skills/agent-memory/SKILL.md new file mode 100644 index 0000000000..cee622ba4f --- /dev/null +++ b/.claude/skills/agent-memory/SKILL.md @@ -0,0 +1,135 @@ +--- +name: agent-memory +description: Instructions about how to build up the memory system for agent +--- + +# Persistent Agent Memory + +You have been specified a `memory directory` for a persistent, file-based memory system. This directory already exists — write to it directly with the Write tool (do not run mkdir or check for its existence). + +You should build up this memory system over time so that future conversations can have a complete picture of who the user is, how they'd like to collaborate with you, what behaviors to avoid or repeat, and the context behind the work the user gives you. + +If the user explicitly asks you to remember something, save it immediately as whichever type fits best. If they ask you to forget something, find and remove the relevant entry. + +## Types of memory + +There are several discrete types of memory that you can store in your memory system: + + + + user + Contain information about the user's role, goals, responsibilities, and knowledge. Great user memories help you tailor your future behavior to the user's preferences and perspective. Your goal in reading and writing these memories is to build up an understanding of who the user is and how you can be most helpful to them specifically. For example, you should collaborate with a senior software engineer differently than a student who is coding for the very first time. Keep in mind, that the aim here is to be helpful to the user. Avoid writing memories about the user that could be viewed as a negative judgement or that are not relevant to the work you're trying to accomplish together. + When you learn any details about the user's role, preferences, responsibilities, or knowledge + When your work should be informed by the user's profile or perspective. For example, if the user is asking you to explain a part of the code, you should answer that question in a way that is tailored to the specific details that they will find most valuable or that helps them build their mental model in relation to domain knowledge they already have. + + user: I'm a data scientist investigating what logging we have in place + assistant: [saves user memory: user is a data scientist, currently focused on observability/logging] + + user: I've been writing Go for ten years but this is my first time touching the React side of this repo + assistant: [saves user memory: deep Go expertise, new to React and this project's frontend — frame frontend explanations in terms of backend analogues] + + + + feedback + Guidance the user has given you about how to approach work — both what to avoid and what to keep doing. These are a very important type of memory to read and write as they allow you to remain coherent and responsive to the way you should approach work in the project. Record from failure AND success: if you only save corrections, you will avoid past mistakes but drift away from approaches the user has already validated, and may grow overly cautious. + Any time the user corrects your approach ("no not that", "don't", "stop doing X") OR confirms a non-obvious approach worked ("yes exactly", "perfect, keep doing that", accepting an unusual choice without pushback). Corrections are easy to notice; confirmations are quieter — watch for them. In both cases, save what is applicable to future conversations, especially if surprising or not obvious from the code. Include *why* so you can judge edge cases later. + Let these memories guide your behavior so that the user does not need to offer the same guidance twice. + Lead with the rule itself, then a **Why:** line (the reason the user gave — often a past incident or strong preference) and a **How to apply:** line (when/where this guidance kicks in). Knowing *why* lets you judge edge cases instead of blindly following the rule. + + user: don't mock the database in these tests — we got burned last quarter when mocked tests passed but the prod migration failed + assistant: [saves feedback memory: integration tests must hit a real database, not mocks. Reason: prior incident where mock/prod divergence masked a broken migration] + + user: stop summarizing what you just did at the end of every response, I can read the diff + assistant: [saves feedback memory: this user wants terse responses with no trailing summaries] + + user: yeah the single bundled PR was the right call here, splitting this one would've just been churn + assistant: [saves feedback memory: for refactors in this area, user prefers one bundled PR over many small ones. Confirmed after I chose this approach — a validated judgment call, not a correction] + + + + project + Information that you learn about ongoing work, goals, initiatives, bugs, or incidents within the project that is not otherwise derivable from the code or git history. Project memories help you understand the broader context and motivation behind the work the user is doing within this working directory. + When you learn who is doing what, why, or by when. These states change relatively quickly so try to keep your understanding of this up to date. Always convert relative dates in user messages to absolute dates when saving (e.g., "Thursday" → "2026-03-05"), so the memory remains interpretable after time passes. + Use these memories to more fully understand the details and nuance behind the user's request and make better informed suggestions. + Lead with the fact or decision, then a **Why:** line (the motivation — often a constraint, deadline, or stakeholder ask) and a **How to apply:** line (how this should shape your suggestions). Project memories decay fast, so the why helps future-you judge whether the memory is still load-bearing. + + user: we're freezing all non-critical merges after Thursday — mobile team is cutting a release branch + assistant: [saves project memory: merge freeze begins 2026-03-05 for mobile release cut. Flag any non-critical PR work scheduled after that date] + + user: the reason we're ripping out the old auth middleware is that legal flagged it for storing session tokens in a way that doesn't meet the new compliance requirements + assistant: [saves project memory: auth middleware rewrite is driven by legal/compliance requirements around session token storage, not tech-debt cleanup — scope decisions should favor compliance over ergonomics] + + + + reference + Stores pointers to where information can be found in external systems. These memories allow you to remember where to look to find up-to-date information outside of the project directory. + When you learn about resources in external systems and their purpose. For example, that bugs are tracked in a specific project in Linear or that feedback can be found in a specific Slack channel. + When the user references an external system or information that may be in an external system. + + user: check the Linear project "INGEST" if you want context on these tickets, that's where we track all pipeline bugs + assistant: [saves reference memory: pipeline bugs are tracked in Linear project "INGEST"] + + user: the Grafana board at grafana.internal/d/api-latency is what oncall watches — if you're touching request handling, that's the thing that'll page someone + assistant: [saves reference memory: grafana.internal/d/api-latency is the oncall latency dashboard — check it when editing request-path code] + + + + +## What NOT to save in memory + +- Code patterns, conventions, architecture, file paths, or project structure — these can be derived by reading the current project state. +- Git history, recent changes, or who-changed-what — `git log` / `git blame` are authoritative. +- Debugging solutions or fix recipes — the fix is in the code; the commit message has the context. +- Anything already documented in CLAUDE.md files. +- Ephemeral task details: in-progress work, temporary state, current conversation context. + +These exclusions apply even when the user explicitly asks you to save. If they ask you to save a PR list or activity summary, ask what was *surprising* or *non-obvious* about it — that is the part worth keeping. + +## How to save memories + +Saving a memory is a two-step process: + +**Step 1** — write the memory to its own file (e.g., `user_role.md`, `feedback_testing.md`) using this frontmatter format: + +```markdown +--- +name: {{memory name}} +description: {{one-line description — used to decide relevance in future conversations, so be specific}} +type: {{user, feedback, project, reference}} +--- + +{{memory content — for feedback/project types, structure as: rule/fact, then **Why:** and **How to apply:** lines}} +``` + +**Step 2** — add a pointer to that file in `MEMORY.md`. `MEMORY.md` is an index, not a memory — each entry should be one line, under ~150 characters: `- [Title](file.md) — one-line hook`. It has no frontmatter. Never write memory content directly into `MEMORY.md`. + +- `MEMORY.md` is always loaded into your conversation context — lines after 200 will be truncated, so keep the index concise +- Keep the name, description, and type fields in memory files up-to-date with the content +- Organize memory semantically by topic, not chronologically +- Update or remove memories that turn out to be wrong or outdated +- Do not write duplicate memories. First check if there is an existing memory you can update before writing a new one. + +## When to access memories +- When memories seem relevant, or the user references prior-conversation work. +- You MUST access memory when the user explicitly asks you to check, recall, or remember. +- If the user says to *ignore* or *not use* memory: Do not apply remembered facts, cite, compare against, or mention memory content. +- Memory records can become stale over time. Use memory as context for what was true at a given point in time. Before answering the user or building assumptions based solely on information in memory records, verify that the memory is still correct and up-to-date by reading the current state of the files or resources. If a recalled memory conflicts with current information, trust what you observe now — and update or remove the stale memory rather than acting on it. + +## Before recommending from memory + +A memory that names a specific function, file, or flag is a claim that it existed *when the memory was written*. It may have been renamed, removed, or never merged. Before recommending it: + +- If the memory names a file path: check the file exists. +- If the memory names a function or flag: grep for it. +- If the user is about to act on your recommendation (not just asking about history), verify first. + +"The memory says X exists" is not the same as "X exists now." + +A memory that summarizes repo state (activity logs, architecture snapshots) is frozen in time. If the user asks about *recent* or *current* state, prefer `git log` or reading the code over recalling the snapshot. + +## Memory and other forms of persistence +Memory is one of several persistence mechanisms available to you as you assist the user in a given conversation. The distinction is often that memory can be recalled in future conversations and should not be used for persisting information that is only useful within the scope of the current conversation. +- When to use or update a plan instead of memory: If you are about to start a non-trivial implementation task and would like to reach alignment with the user on your approach you should use a Plan rather than saving this information to memory. Similarly, if you already have a plan within the conversation and you have changed your approach persist that change by updating the plan rather than saving a memory. +- When to use or update tasks instead of memory: When you need to break your work in current conversation into discrete steps or keep track of your progress use tasks instead of saving to memory. Tasks are great for persisting information about the work that needs to be done in the current conversation, but memory should be reserved for information that will be useful in future conversations. + +- Since this memory is project-scope and shared with your team via version control, tailor your memories to this project diff --git a/.claude/skills/db-query/SKILL.md b/.claude/skills/db-query/SKILL.md new file mode 100644 index 0000000000..02f12cbcac --- /dev/null +++ b/.claude/skills/db-query/SKILL.md @@ -0,0 +1,36 @@ +--- +name: db-query +description: Do query from database for common task +model: sonnet +allowed-tools: Bash(psql *) +--- + +User could like to know about the status of L2 data blocks and proving task, following is their request: + +$ARGUMENTS + +(If you find there is nothing in the request above, just tell "nothing to do" and stop) + +You should have known the data sheme of our database, if not yet, read it from the `.sql` files under `database/migrate/migrations`. + +According to use's request, generate the corresponding SQL expression and query the database. For example, if user ask "list the assigned chunks", it means "query records from `chunk` table with proving_status=2 (assigned)", or the SQL expression 'SELECT * from chunk where proving_status=2;'. If it is not clear, you can ask user which col they are indicating to, and list some possible options. + +For the generated SQL, following rules MUST be obey: + ++ Limit the number of records to 20, unless user has a specification explicitly like "show me ALL chunks". ++ Following cols can not be read by human and contain very large texts, they MUST be excluded in the SQL expression: + + For all table, any col named "proof" + + "header" and "transactions" in `l2_block` table + + "calldata" in `l1_message` ++ Always omit the `deleted_at` col, never include them in query or use in where condition ++ Without explicit specification, the records should be ordered by the `updated_at` col, the most recent one first. + +When you has decided the SQL expression, always print it out. + +You use psql client to query from our PostgreSQL db. When launching psql, always with "-w" options, and use "-o" to send all ouput to `query_report.txt` file under system's temporary dir, like /tmp. You MUST NOT read the generated report. + +If the psql failed since authentication, guide user to prepare their `.pgpass` file under home dir. + +You should have known the endpoint of the database before, in the form of PostgreSQL DSN. If not, try to read it from the `db.dsn` field inside of `coordinator/build/bin/conf/config.json`. If still not able to get the data, ask via Ask User Question to get the endpoint. + + diff --git a/.claude/skills/integration-test-helper/SKILL.md b/.claude/skills/integration-test-helper/SKILL.md new file mode 100644 index 0000000000..6cc35c6898 --- /dev/null +++ b/.claude/skills/integration-test-helper/SKILL.md @@ -0,0 +1,51 @@ +--- +name: integration-test-helper +description: Helps launching the full process of integration test, also investigate and report the results. +--- + +## Target directory + +The whole process should be run under current directory, unless it is specified to ($ARGUMENTS[0]) +Under the target dir there are the stuff and instructions. + +## Instructions + +First read `README.md` under target directory, instructions should be under heading named ($ARGUMENTS[1]). If there is no such a heading name, just try the "Test" heading. + +## Run each step listed in instructions + +The instructions often contain multiple steps which should be completed in sequence. Following are some rules MUST be obey while handling each step: + +### "Must do" while executing commands in steps + +Any command mentioned in steps should be executed by Bash tool, with following MUST DO for handling the outputs: + ++ Redirect the output of bash tool, both from stdout andstderr, into a local log file for investigating later. The file name should be in format as `__