piker/ai/prompt-io/claude
Gud Boi 4485f2b9ce Fix `pytest` config-dir isolation in subactors
The old (commented-out) `get_app_dir()` override gated on
`'pytest' in sys.modules` which can NEVER work in spawned
subactors (fresh procs, no pytest import); as a result test
`paperboi`/daemon actors were writing into the user's REAL
`~/.config/piker/accounting/` files.. friggin yikes.

Deats,
- add `config._maybe_use_test_dir()` which lazily (at
  conf-path access time, NOT import time) reads the
  `piker_test_dir` entry from
  `tractor.runtime._state._runtime_vars['piker_vars']` as
  pre-loaded by `open_piker_runtime()` from the
  `tests.conftest._open_test_pikerd()` overrides.
- hook it in `get_conf_dir()` and route `get_conf_path()`
  + `load()`'s mkdir through `get_conf_dir()`.
- route `.accounting._ledger` / `._pos` dir derivation
  through `config.get_conf_dir()` (was reading the
  `_config_dir` global directly, bypassing the override);
  also `mkdir(parents=True, exist_ok=True)` for nested
  tmp-dir creation.

(this patch was generated in some part by [`claude-code`][claude-code-gh])
[claude-code-gh]: https://github.com/anthropics/claude-code

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Prompt-IO: ai/prompt-io/claude/20260610T170859Z_75cefe10_prompt_io.md
2026-06-10 13:10:09 -04:00
..
20260610T170859Z_75cefe10_prompt_io.md Fix `pytest` config-dir isolation in subactors 2026-06-10 13:10:09 -04:00
20260610T170859Z_75cefe10_prompt_io.raw.md Fix `pytest` config-dir isolation in subactors 2026-06-10 13:10:09 -04:00
README.md Fix `pytest` config-dir isolation in subactors 2026-06-10 13:10:09 -04:00

README.md

AI Prompt I/O Log — claude

This directory tracks prompt inputs and model outputs for AI-assisted development using claude (claude-code CLI).

Policy

Prompt logging follows the NLNet generative AI policy. All substantive AI contributions are logged with: - Model name and version - Timestamps - The prompts that produced the output - Unedited model output (.raw.md files)

Usage

Entries are created by the /prompt-io skill or automatically via /commit-msg integration.

Each commit carrying AI-generated changes links to its provenance entry via a Prompt-IO: commit-msg trailer; entries use “diff-ref mode” (pointers into git log -p instead of verbatim code copies) to avoid duplicating committed code.

Human contributors remain accountable for all code decisions. AI-generated content is never presented as human-authored work.