Skip to content

fix: relocate memory-lint + scanner runtime output out of .abcd/logbook (iss-73) - #52

Merged
REPPL merged 2 commits into
mainfrom
fix/iss-73-relocate-logbook-output
Jul 13, 2026
Merged

fix: relocate memory-lint + scanner runtime output out of .abcd/logbook (iss-73)#52
REPPL merged 2 commits into
mainfrom
fix/iss-73-relocate-logbook-output

Conversation

@REPPL

@REPPL REPPL commented Jul 12, 2026

Copy link
Copy Markdown
Owner

What

.abcd/logbook/ is a retired runtime-output location (iss-36/iss-56). The
2026-07-12 maintainer adjudication placed runtime artefacts in the gitignored
.abcd/.work.local/logs/ tier. Two Go sites still named the retired location:

  • memory lint wrote its report dir under .abcd/logbook/memory/ (lint.go)
  • the PII scanner's defaultSkipFragments referenced .abcd/logbook/pii-scan/
    and .abcd/logbook/audit-history/ (scanner.go)

Both now use .abcd/.work.local/logs/.

Detector-first

TestNoRetiredLogbookLocationInSource walks internal/ and fails if any non-test
Go source names the retired logbook location. Watched it flag both sites, then
pass after the relocation.

Transparent / safe

No reader hardcoded the old path — memory lint returns ReportDir; the scanner
uses the fragments only to skip its own output. Security review: PROMOTE, and
it flagged the change as a net improvement — the old .abcd/logbook/ was not
gitignored (a publishable-yet-skipped path), while the new tier is gitignored, so
the launch bundle excludes it before the scanner runs.

Review-driven fix

Correctness review FIX-FIRST: commands/abcd/memory.md (the shipped plugin doc
for this verb) still named the old path — updated to the new one.

Scope note (deferred)

Arming the .abcd/logbook record-lint markdown ban (iss-36/iss-56) is a
separate follow-up: record-lint scans .abcd/development/**/*.md, where several
research notes still reference the path (some historical, one current, plus an
unimplemented publish spec). That markdown reconciliation is out of scope here
and will be tracked/captured on main. iss-56 (logbook) resolution is likewise
deferred to the ledger-cleanup pass (it shares an id with a second issue —
iss-74).

make preflight green. Part of drain #2. Chain: branched from main;
independent of iss-76/iss-79.

Assisted-by: Claude:claude-opus-4-8

REPPL added 2 commits July 12, 2026 23:03
…ok (iss-73)

.abcd/logbook/ is a retired runtime-output location (iss-36/iss-56). The
2026-07-12 maintainer adjudication placed runtime artefacts in the gitignored
.abcd/.work.local/logs/ tier. Two Go sites still named the retired location:

  - memory lint wrote its report dir under .abcd/logbook/memory/ (lint.go)
  - the PII scanner's defaultSkipFragments referenced .abcd/logbook/pii-scan/
    and .abcd/logbook/audit-history/ (scanner.go)

Both now use .abcd/.work.local/logs/. No reader hardcoded the old path (memory
lint returns ReportDir; the scanner uses the fragments only to skip its own
output), so the relocation is transparent.

The shipped plugin doc for the verb (commands/abcd/memory.md) is updated to the
new report path (a correctness-review FIX-FIRST: it is a user-facing front door,
not the deferred .abcd/development markdown).

Detector-first: TestNoRetiredLogbookLocationInSource walks internal/ and fails
if any non-test Go source names the retired 'logbook' location. Watched it flag
both sites, then pass after the relocation.

Purely-internal (gitignored runtime output, no committed/API surface), so no
CHANGELOG entry. Arming the .abcd/logbook record-lint markdown ban (iss-36/
iss-56) is a separate follow-up: record-lint scans .abcd/development/**/*.md,
where several research notes still reference the path (some historical, one
current, plus an unimplemented publish spec) -- a markdown reconciliation pass
out of scope here.

Assisted-by: Claude:claude-opus-4-8
Assisted-by: Claude:claude-opus-4-8
@REPPL
REPPL merged commit 069e62e into main Jul 13, 2026
12 checks passed
@REPPL
REPPL deleted the fix/iss-73-relocate-logbook-output branch July 13, 2026 06:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant