Working tree carries untracked private session transcripts — disposition pending (gitignore pattern or relocation)

[F-e-u-e-r]

Observed condition

Two untracked files sit at the public repo's working-tree root on the
maintainer machine (observed 2026-07-30):

• chat-history.md — the 2026-07-29/30 maintainer session's terminal
  transcript
• security-enhancement.md — another session's full terminal
  transcript

Both are private session content. Neither has ever entered a commit
(verified: untracked status; no history for either path).

Risk

One stage-everything command (git add -A, git commit -a) away from
publishing private conversation to a public repository. This is the
exact threat 92314a6's own message names for skills-staging/
("keeps a stray git add -A from publishing it"); the transcript files
have no equivalent protection today.

Session lesson (2026-07-29/30)

The campaign session flagged security-enhancement.md to the owner at
close and staged by pathspec throughout, so nothing leaked; the
disposition question was left with the owner and remains open.
chat-history.md appeared after that session (it is that session's own
transcript).

Why this is an issue and not part of the skill-library PR

The fix lives outside skills-staging/ (a .gitignore pattern) and/or
is an owner call (relocate the transcripts out of the repo; choose the
pattern future transcript drops will use — explicit filenames vs a
naming convention).

Proposed acceptance criteria

• Either a .gitignore rule covering these files (plus the naming
  pattern future transcript drops will follow), or the files relocated
  outside the repository; and
• git status at the repo root shows no untracked private transcripts.

Related

• 92314a6 — the skills-staging ignore decision and its stated
  rationale.
• The 2026-07-30 skill-library PR (linked after it opens) documents the
  standing working-tree discipline (repo-boundaries-and-sync;
  UNCERTAINTY.md item 1).

No transcript content is included here by design.

[F-e-u-e-r]

The skill library documenting the standing working-tree discipline for this risk (repo-boundaries-and-sync; UNCERTAINTY.md item 1) is delivered in PR #101 — this issue is linked from its description. The library's safe default stands regardless of this issue's outcome: pathspec-only staging, never quote transcript content publicly.

[F-e-u-e-r]

Closure record (the issue auto-closed via #107's Closes #100; owner-authorized disposition): ignore-in-place + forward convention.

• The two named transcripts are ignored by exact root-anchored name (/chat-history.md, /security-enhancement.md). Both remain on disk, untouched — they are cited as extraction sources by the staged libraries' provenance, so relocation was deliberately not chosen; archival to the fable-archive channel stays available later.
• Forward convention, documented in .gitignore itself: future transcript drops go under transcripts/ (ignored wholesale), or a root-level one-off is named *.transcript.md.
• Verification: a 12-path git check-ignore -v matrix (6 positives hit their intended patterns incl. both transcripts, a transcripts/ member and a root *.transcript.md; 6 negative controls clean incl. all three whitelisted delivery subtrees and a non-root docs/foo.transcript.md), and git status on the rule-carrying tree no longer lists the two files — this issue's acceptance criterion.

The one-stage-everything risk this issue names is closed: git add -A can no longer sweep the transcripts into a commit.