fix: chore: create formula label in Codeberg + add more formula templates (#22)

- Add formulas/upgrade-dependency.toml: multi-ecosystem (npm/cargo/forge) dependency upgrade
  with steps for checking changelog, upgrading, applying breaking changes, and running tests
- Add formulas/add-rpc-method.toml: JSON-RPC method addition with steps for reading
  existing patterns, implementing handler, registering, writing tests, and running tests
- Document `formula` label in BOOTSTRAP.md optional labels table

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

BOOTSTRAP.md

@@ -84,6 +84,7 @@ Optional but recommended:
 |-------|---------|
 | `tech-debt` | Gardener can promote these to `backlog` |
 | `blocked` | Dev-agent marks issues with unmet dependencies |
+| `formula` | Dev-agent uses a structured TOML formula instead of freeform — issue body must have YAML front matter specifying the formula name and variables (see `formulas/`) |
 
 ### Required: Branch protection
 

formulas/add-rpc-method.toml

@@ -0,0 +1,92 @@
+# formulas/add-rpc-method.toml — Add a new JSON-RPC method to a server
+
+name        = "add-rpc-method"
+description = "Add JSON-RPC method {{method_name}} to the server"
+version     = 1
+
+[vars.method_name]
+description = "Full method name (e.g. eth_getBalance, harb_listPositions)"
+required    = true
+
+[vars.params_spec]
+description = "Comma-separated parameter names and types (e.g. 'address: Address, blockTag: BlockTag')"
+required    = false
+default     = ""
+
+[vars.return_type]
+description = "Return type description (e.g. 'U256 balance', 'Vec<Position>')"
+required    = false
+default     = "result"
+
+[vars.namespace]
+description = "RPC namespace prefix (e.g. eth, harb, net) — derived from method_name if omitted"
+required    = false
+default     = ""
+
+[[steps]]
+id          = "read-existing"
+title       = "Read existing RPC methods for patterns"
+description = """
+Find and read 2-3 existing RPC method implementations in this codebase.
+Identify:
+- Where method handlers are defined (trait, module, file)
+- How methods are registered with the router/server
+- How params are deserialized and validated
+- How errors are returned (error type, codes)
+- How tests are structured for RPC methods
+Note the file paths so subsequent steps can follow the same patterns.
+"""
+
+[[steps]]
+id          = "implement-handler"
+title       = "Implement {{method_name}} handler"
+description = """
+Create the handler for {{method_name}} following the patterns found above.
+
+Method signature should accept: {{params_spec}}
+Return type: {{return_type}}
+
+Requirements:
+- Validate input parameters; return appropriate JSON-RPC error codes for invalid input
+- Implement the core logic
+- Add inline documentation describing the method's purpose and params
+- Follow the naming conventions and error-handling style of existing methods
+"""
+needs       = ["read-existing"]
+
+[[steps]]
+id          = "register-method"
+title       = "Register {{method_name}} with the RPC router"
+description = """
+Add {{method_name}} to the server's method registry / router, following the
+same registration pattern used by existing methods.
+
+Verify the method is reachable — check that no namespace filter or
+allowlist would block it in the default configuration.
+"""
+needs       = ["implement-handler"]
+
+[[steps]]
+id          = "write-tests"
+title       = "Write tests for {{method_name}}"
+description = """
+Add at least two tests for {{method_name}}:
+1. Happy path — valid input, expected {{return_type}} returned
+2. Error path — invalid or missing params, correct JSON-RPC error returned
+
+Follow the test patterns found in read-existing.
+Use any existing test fixtures or mock server helpers.
+"""
+needs       = ["register-method"]
+
+[[steps]]
+id          = "run-tests"
+title       = "Run tests and verify"
+description = """
+Run the full test suite (e.g. cargo test, npm test, forge test).
+Confirm:
+- New tests pass
+- No existing tests were broken
+Fix any compilation errors or assertion failures before finishing.
+"""
+needs       = ["write-tests"]

formulas/upgrade-dependency.toml

@@ -0,0 +1,78 @@
+# formulas/upgrade-dependency.toml — Upgrade a package dependency
+
+name        = "upgrade-dependency"
+description = "Upgrade {{package}} from {{from_version}} to {{to_version}}"
+version     = 1
+
+[vars.package]
+description = "Package name to upgrade (e.g. viem, serde, forge-std)"
+required    = true
+
+[vars.ecosystem]
+description = "Package ecosystem: npm, cargo, or forge"
+required    = true
+
+[vars.from_version]
+description = "Current version (e.g. 1.2.3) — used for changelog lookup"
+required    = false
+default     = "current"
+
+[vars.to_version]
+description = "Target version (e.g. 2.0.0) — leave blank for latest"
+required    = false
+default     = "latest"
+
+[[steps]]
+id          = "check-current"
+title       = "Check current {{package}} version and changelog"
+description = """
+Identify the installed version of {{package}} in the lockfile or manifest.
+Look up the changelog or release notes between {{from_version}} and {{to_version}}.
+Note any breaking changes, deprecations, or migration steps required.
+"""
+
+[[steps]]
+id          = "upgrade"
+title       = "Run upgrade for {{ecosystem}}"
+description = """
+Run the appropriate upgrade command for ecosystem={{ecosystem}}:
+
+- npm:   npm install {{package}}@{{to_version}} (or @latest)
+         Then: npm install  (to sync lockfile)
+- cargo: cargo update -p {{package}} [--precise {{to_version}}]
+         Or bump version in Cargo.toml, then: cargo build
+- forge: Update version in foundry.toml or gitmodules, then:
+         forge install {{package}}  (or forge update {{package}})
+
+Confirm the lockfile / manifest now reflects {{to_version}}.
+"""
+needs       = ["check-current"]
+
+[[steps]]
+id          = "fix-breaking-changes"
+title       = "Apply migration steps for breaking changes"
+description = """
+Based on the changelog reviewed in check-current, apply any required changes:
+- Rename renamed APIs or types
+- Update import paths if they moved
+- Adjust call sites for signature changes
+- Remove usage of deprecated symbols
+
+If no breaking changes were noted, verify a quick build still passes.
+"""
+needs       = ["upgrade"]
+
+[[steps]]
+id          = "run-tests"
+title       = "Run tests and verify"
+description = """
+Run the full test suite appropriate for ecosystem={{ecosystem}}:
+
+- npm:   npm test (or the project's test script)
+- cargo: cargo test
+- forge: forge test
+
+Confirm all tests pass. Fix any compilation errors or test failures introduced
+by the upgrade before declaring this done.
+"""
+needs       = ["fix-breaking-changes"]