CC: Record Codex native retention probe
This commit is contained in:
@@ -36,6 +36,12 @@ Focused check:
|
||||
python3 tools/archive_codex_inactive_threads.py --check
|
||||
```
|
||||
|
||||
Native Codex retention probe:
|
||||
|
||||
```bash
|
||||
python3 tools/probe_codex_native_retention.py --check
|
||||
```
|
||||
|
||||
Approved archive-only execution:
|
||||
|
||||
```bash
|
||||
@@ -56,6 +62,8 @@ python3 tools/archive_codex_inactive_threads.py --execute --approval-token "I ap
|
||||
- SQLite checkpoint or vacuum is blocked;
|
||||
- Core source mutation is blocked.
|
||||
|
||||
Installed Codex `0.134.0` advertises `--ephemeral` prevention but no native cleanup/archive/retention command. Cached latest is `0.137.0`; update and re-probe before approved archive execution if latest native behavior should be considered.
|
||||
|
||||
## Backup
|
||||
|
||||
Before any approved archive update, the executor backs up:
|
||||
@@ -86,4 +94,5 @@ Use this executor only after JP gives the exact archive-only approval token. Kee
|
||||
## New Issues
|
||||
|
||||
- must-fix: obtain exact approval token before running `--execute`.
|
||||
- follow-up: decide whether to update Codex and re-run the native retention probe before archive-only execution.
|
||||
- follow-up: after archive-only execution, re-run retention planner and decide whether deletion is still worth separate approval.
|
||||
|
||||
@@ -42,6 +42,18 @@ The planner classifies:
|
||||
- top log pressure targets;
|
||||
- approval boundaries.
|
||||
|
||||
## Native Codex Probe
|
||||
|
||||
`python3 tools/probe_codex_native_retention.py` checks installed Codex CLI help, feature flags, and local version cache. It does not read transcript bodies, thread text fields, titles, previews, secrets, raw messages, or mutate Codex state.
|
||||
|
||||
Probe result on 2026-06-04:
|
||||
|
||||
- installed Codex version: `0.134.0`;
|
||||
- cached latest Codex version: `0.137.0`;
|
||||
- native cleanup/archive/retention command advertised by installed CLI: false;
|
||||
- prevention flag advertised: `codex exec --ephemeral`;
|
||||
- decision point: update Codex and re-run the probe before custom archive mutation if latest native behavior must be considered.
|
||||
|
||||
## Policy
|
||||
|
||||
1. Prevention default: use `codex exec --ephemeral` for disposable non-interactive worker runs.
|
||||
@@ -70,4 +82,4 @@ Next safe action is to ask for archive-only approval. Delete and vacuum stay sep
|
||||
|
||||
- must-fix: obtain explicit archive-only approval before any `threads.archived` update.
|
||||
- must-fix: obtain separate destructive approval before session deletion, log deletion, checkpoint, or vacuum.
|
||||
- follow-up: check native Codex retention support before custom mutation.
|
||||
- follow-up: native Codex retention support is checked for installed `0.134.0`; update/re-probe `0.137.0` before custom mutation if latest native behavior should be considered.
|
||||
|
||||
Reference in New Issue
Block a user