Stamp daemon log lines only outside the journal

[onechat] / AGENTS.md

# Agent guide

Read this file in full. It holds the rules for every task.

## References

- `README.rst`: project scope, setup, and commands.
- `AGENTS.local.md`: the preferences of one person, machine, or account.
  Git ignores it. Read it when it exists. When it conflicts with this
  guide, this guide wins.

## Skills

Read the `SKILL.md` of a skill before you start the task that it covers:

| Task                                            | Skill                    |
| ----------------------------------------------- | ------------------------ |
| Write or change Go code or Go tests             | `.agents/skills/go-code` |
| Write or change documentation or prose comments | `.agents/skills/docs`    |
| Format and check the repository                 | `.agents/skills/check`   |
| Make any commit                                 | `.agents/skills/commit`  |
| Read or write an issue                          | `.agents/skills/issues`  |

## Rules

- Use ASD-STE100 Simplified Technical English for communication with the
  user, documentation, and code comments.
- Every file describes the current state only. Do not write history in
  files: no dates of changes, no "was", "previously", or "no longer",
  and no changelogs or work logs. Git records what changed and why.
- Keep the implementation small. Add a feature, dependency, or
  integration only when a task requires it.
- Change only what the task asks for. Do not change unrelated code to
  match a style rule.
- Nix is the reference environment. The pinned flake supplies the Go
  toolchain, the tools, and every dependency. Keep Nix code in `nix/`.
  Do not install host dependencies or add a dependency that works only
  outside Nix.
- Write only ASCII characters in files, commit messages, and issues. Use
  `<-` and `->` for arrows, `-` for dashes, and straight quotes. Use
  other characters only in test data that checks Unicode handling.
- Keep secrets and local runtime files out of Git and Nix sources.
- Do not reveal infrastructure in files, code comments, commit messages,
  or issues. This includes host, server, and domain names, IP addresses,
  ports, network devices, user names, paths outside the repository, and
  deploy steps. Values from `AGENTS.local.md` or the local machine are
  private too.
- Use a neutral placeholder, such as `example.com` or `HOST`, or
  describe the condition instead. Write a real value only when the user
  explicitly allows that value for the current task.
- Change `AGENTS.md` and `.agents/` only when the user asks.
- Put personal, machine, or account preferences in `AGENTS.local.md`,
  never in a tracked file.

## Decisions

Stop and ask the user before you act when:

- the task can be read in more than one way;
- two or more reasonable solutions give different results;
- the task conflicts with this guide or a skill.

Ask one short question. Give the options and your recommendation.
Continue only with work that the answer cannot change.