feat(ENG-162): Add tree example

.claude/commands/build-example.md

@@ -0,0 +1,23 @@
+# Build example
+
+Run the full build-examples pipeline that builds, dumps, disassembles,
+tests, and verifies artifacts.
+
+From the `examples/` directory, run:
+
+```sh
+cargo run --bin build-examples -- --example $ARGUMENTS
+```
+
+If `$ARGUMENTS` is empty, run without the `--example` flag to build all
+examples:
+
+```sh
+cargo run --bin build-examples
+```
+
+This executes `examples/utils/build-examples/src/main.rs` which handles
+building ELF files, generating dumps/disassembly, running tests, saving
+test snippets, and verifying code snippets.
+
+Report the outcome. If the command fails, show the relevant error output.

.claude/commands/disassemble-example.md

@@ -0,0 +1,32 @@
+# Disassemble example
+
+Quick compile and disassemble cycle for a specific example program.
+
+Run the following commands sequentially from the example directory at
+`examples/$ARGUMENTS`:
+
+1. Remove stale binary:
+
+```sh
+rm -f ../target/deploy/${ARGUMENTS//-/_}.so
+```
+
+1. Build for the disassembly architecture:
+
+```sh
+cargo build-sbf --arch v2 --tools-version 1.52
+```
+
+1. Disassemble and write output:
+
+```sh
+sbpf disassemble ../target/deploy/${ARGUMENTS//-/_}.so \
+  > artifacts/rs-disassembly.s
+```
+
+If `$ARGUMENTS` is empty, infer the example name from the current
+conversation context (e.g. recent file paths or discussion). If you still
+cannot determine it, ask which example to disassemble.
+
+Report the result. Show the disassembly content or the relevant section
+if the user is focused on specific functions.

.claude/commands/test-example.md

@@ -0,0 +1,18 @@
+# Test example
+
+Quick build and test cycle for a specific example program.
+
+Run the following commands sequentially from the example directory at
+`examples/$ARGUMENTS`:
+
+```sh
+cargo build-sbf --arch v3 --tools-version 1.51
+sbpf build
+cargo test -- --test-threads 1
+```
+
+If `$ARGUMENTS` is empty, infer the example name from the current
+conversation context (e.g. recent file paths or discussion). If you still
+cannot determine it, ask which example to test.
+
+Report the result of each step. If any step fails, stop and show the error.

.claude/skills/manage-pentagon-agent

@@ -0,0 +1 @@
+/Users/alex/.pentagon/skills/manage-pentagon-agent

.claude/skills/manage-pentagon-canvas

@@ -0,0 +1 @@
+/Users/alex/.pentagon/skills/manage-pentagon-canvas

.claude/skills/manage-pentagon-role

@@ -0,0 +1 @@
+/Users/alex/.pentagon/skills/manage-pentagon-role

.claude/skills/manage-pentagon-team

@@ -0,0 +1 @@
+/Users/alex/.pentagon/skills/manage-pentagon-team

.claude/skills/send-pentagon-message

@@ -0,0 +1 @@
+/Users/alex/.pentagon/skills/send-pentagon-message

.github/workflows/build-examples.yml

@@ -4,7 +4,7 @@ env:
   SBPF_ARCH_DISASSEMBLE: 'v2'
   SBPF_ARCH_DUMP: 'v4'
   SBPF_ARCH_TEST: 'v3'
-  SBPF_CLI_REVISION: 'eb67fc5'
+  SBPF_CLI_REVISION: 'c52805f'
   SOLANA_VERSION: 'v3.1.2'
   TOOLS_VERSION_DISASSEMBLE: 'v1.52'
   TOOLS_VERSION_DUMP: 'v1.51'

CLAUDE.md

@@ -0,0 +1,34 @@
+# Conventions
+
+## Self-Improvement
+
+After every task, check what was learned and route it:
+
+- Repeated instruction (corrected twice): add it to CLAUDE.md.
+- Design decision: write or update a spec.
+- Repeatable workflow: propose a skill.
+- Must always happen: propose a hook.
+- Learned pattern: save to memory.
+
+Before implementing anything non-trivial, write or update a spec and get
+approval first.
+
+## Markdown
+
+- Use `-` for list markers.
+- End list items with periods.
+- Wrap lines to maximize use of the 80-column limit. Break at word boundaries,
+  not early.
+
+Every markdown change must pass (run both):
+
+```sh
+cfg=cfg/pre-commit/quick-lint.yml
+pre-commit run -c $cfg markdownlint-fix --files <file>
+pre-commit run -c $cfg mdformat --files <file>
+```
+
+## Specs
+
+- `specs/` for cross-cutting concerns (build, CI, conventions).
+- `examples/tree/specs/` for tree-specific design decisions.

cfg/dictionary.txt

@@ -16,8 +16,11 @@ lamports
 lddw
 ldxb
 ldxdw
+ldxh
 ldxw
+markdownlint
 mathjax
+mdformat
 memcmp
 memcpy
 metas
@@ -41,6 +44,7 @@ syscalls
 sysvar
 sysvars
 uninit
+uoff
 usize
 vitepress
 xffff

docs/.vitepress/config.js

@@ -40,6 +40,7 @@ export default {
           { text: "Fibonacci", link: "/examples/fibonacci" },
           { text: "Transfer", link: "/examples/transfer" },
           { text: "Counter", link: "/examples/counter" },
+          { text: "Tree", link: "/examples/tree" },
         ],
       },
       {

docs/src/examples/fibonacci.md

@@ -4,7 +4,7 @@
 
 <!-- @include: ./disclaimer.md -->
 
-## :1234: Fibonacci sequence background
+## :1234: Background
 
 The [Fibonacci sequence] is a classic mathematical sequence where each number is
 the sum of the two preceding ones, typically starting with $F(0) = 0$ and

docs/src/examples/memo.md

@@ -4,7 +4,13 @@
 
 <!-- @include: ./disclaimer.md -->
 
-## :world_map: Memory map background
+## :desktop_computer: Background
+
+This program logs arbitrary message data passed via instruction data. It accepts
+no accounts and simply writes the provided bytes to the program log using the
+[`sol_log_`] syscall. If any accounts are passed, the program returns an error.
+
+## :world_map: Memory map layout
 
 The [SBPF instruction set architecture] defines 12 registers, including
 10 general-purpose registers `r0` through `r9`. At the start of instruction