jmap-mime 0.1.2

MIME-to-JMAP adapter: converts mime_tree parsed output to jmap-mail-types body structures
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70

# Agent Instructions — jmap-mime

Thin adapter crate in the JMAP workspace. Converts `mime-tree` output types to
`jmap-mail-types` types. No parsing logic lives here.

Read `~/PROJECT/crate-jmap/AGENTS.md` before doing anything.

## Role in the Workspace

| Depends on | Why |
|---|---|
| `mime-tree` | Source of `ParsedPart`, `ParsedMessage`, `DecodedBodyValue` |
| `jmap-mail-types` | Target types: `EmailBodyPart`, `EmailBodyValue`, `EmailHeader` |
| `jmap-types` | For `Id` type used in `blobId` |

Used by: `jmap-mail-server` (and `stoa-mail` via path dep).

## The One Rule

**This crate must stay thin.** Every function here should be obvious field mapping.
If you find yourself writing a loop, a match on content-type, or any parsing logic,
stop — it belongs in `mime-tree` instead.

## Conversion Functions

```rust
// Part tree: ParsedPart → EmailBodyPart (recursive)
pub fn part_to_jmap(part: &ParsedPart, blob_id_for: impl Fn(&ParsedPart) -> Id) -> EmailBodyPart;

// Body value: DecodedBodyValue → EmailBodyValue
pub fn body_value_to_jmap(val: DecodedBodyValue) -> EmailBodyValue;

// Full body fields from a ParsedMessage
pub fn message_to_jmap_body(msg: &ParsedMessage, blob_id_for: impl Fn(&ParsedPart) -> Id) -> JmapBodyFields;
```

## Quality Gate

```bash
cargo fmt --all
cargo clippy -p jmap-mime -- -D warnings
cargo test -p jmap-mime
```

## Non-Interactive Shell Commands

```bash
cp -f source dest       # NOT: cp source dest
mv -f source dest       # NOT: mv source dest
rm -f file              # NOT: rm file
rm -rf dir              # NOT: rm -r dir
```

## Git Commit and Push Policy

Commit and push freely — see workspace `AGENTS.md` "Git Commit and Push Policy".
The agent is the only writer to `origin/main`, so the default is `git push` with
no `pull --rebase` ritual. Exceptions (force-push, secrets, unrequested files)
are listed in the workspace policy.

## Beads Issue Tracker

```bash
bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --claim  # Claim work
bd close <id>         # Complete work
```

Use `bd` for ALL task tracking. Do not use TodoWrite, TaskCreate, or markdown TODO lists.