vik 0.1.1

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

# Pull Requests

## Branches

Use issue-scoped branches:

```sh
git switch -c vik-16-docs origin/main
```

Sync with `origin/main` before implementation and before handoff:

```sh
git fetch origin
git merge origin/main
```

## Commits

Use English commit messages. Keep commits logical and reviewable.

Message shape:

```text
docs: add Vik usage and development guides

Summary:
- Add operator docs for startup, service, config, and observation.
- Add development docs and agent index.

Rationale:
- Keep README small and make setup steps executable by agents.

Tests:
- cargo test --all-features
```

## PR Body

Include:

- issue id
- summary of changed behavior or docs
- validation commands and results
- risks or known gaps

Add the `vik` label.

## Review Loop

Before moving the tracker issue to human review:

1. Push latest branch.
2. Check PR comments, inline comments, and review summaries.
3. Address every actionable item or reply with clear pushback.
4. Rerun required checks.
5. Confirm CI is green.
6. Confirm PR is linked to the tracker issue.

Do not leave stale workpad or PR body text after scope changes.