vik 0.1.2

Vik is an issue-driven coding workflow automation tool.
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
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93

# Review Checklist

Use this for implementation review. Check acceptance criteria first, then these
gates.

## Module Boundaries

Run:

```sh
rg -n "crate::agent" src/orchestrator src/template src/workspace src/logging
rg -n "crate::shell" src/orchestrator src/config src/workflow src/logging src/workspace
rg -n "crate::orchestrator" src/agent src/session src/hooks src/template src/workflow src/workspace src/daemon
```

Expected result: no hits.

Allowed edges:

- `session -> agent`
- `session -> shell`
- `session -> template`
- `agent -> config`
- `template -> shell`
- `hooks -> shell`

## Workspace Paths

Run:

```sh
rg -n 'join\("(logs|sessions|service|issues|state\.json)"\)' src --glob '*.rs'
```

Production hits stay in `src/workspace/`. Test-only assertions elsewhere are
allowed.

## Provider Boundary

- Adapter builds provider commands.
- Adapter maps provider JSON events.
- Session spawns providers.
- Orchestrator does not know provider JSON or commands.

## Prompt And Hook Boundary

- Prompt files may use ``!`exec(command)` ``.
- Hooks do not run prompt-command expansion.
- Root template bindings stay `issue`, `workspace_root`, `workflow_path`, and
  `env`.
- Extra template objects are absent unless current code adds them.

## Error Surface

- Use typed errors at module boundaries.
- Use `anyhow` only in CLI glue.
- Return or log exact validation failures.

## Tests

- Keep fakes local and `#[cfg(test)]`.
- Use `Workflow::builder()` for runtime workflow tests.
- Use parser fixtures only when parser behavior is under test.
- Use `TempDir` only for filesystem behavior.
- Keep timing tests cheap and parameterized.

## CLI And Docs

- Current shape is `vik <command> [WORKFLOW]`.
- Reject stale `vik [WORKFLOW] <command>` examples.
- HTTP docs say planned unless server code exists.

## Language

- Use American English.
- Commit English text only.
- Grep changed files for non-English text.

## Report Shape

```text
## Architecture audit
- PASS/FAIL: module boundaries
- PASS/FAIL: workspace path ownership
- PASS/FAIL: provider boundaries
- PASS/FAIL: prompt and hook boundaries
- PASS/FAIL: error surface
- PASS/FAIL: tests
- PASS/FAIL: CLI and docs
- PASS/FAIL: language
```

If no old pattern came back, say: `No architectural regressions detected.`