Skip to content

hygiene: gitignore drop/ + .playwright-mcp/ — ferry and scratch directories#151

Open
AceHack wants to merge 1 commit intomainfrom
hygiene/gitignore-drop-folder
Open

hygiene: gitignore drop/ + .playwright-mcp/ — ferry and scratch directories#151
AceHack wants to merge 1 commit intomainfrom
hygiene/gitignore-drop-folder

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 23, 2026

Summary

Small gitignore additions for two transient/local directories that shouldn't ship:

  • drop/ — Aaron's ferry-space for handing content to the agent (Amara's transfer report, notes, etc.). Pattern: drop → absorb into proper substrate → raw file stays local. Preserves signal cleanliness in committed form.
  • .playwright-mcp/ — Playwright MCP per-session scratch logs.

Why lands separately

Each in-flight PR has its own gitignore changes queued but can't reach main until merge. Landing these two on main independently gives base-level coverage regardless of merge order.

Memory

Ferry pattern documented at memory/feedback_drop_folder_ferry_pattern_aaron_hands_off_via_root_drop_dir_2026_04_23.md (per-user).

Test plan

  • git check-ignore drop/ returns ignored status
  • Existing .playwright-mcp/ is now gitignored at main level
  • Verify no accidental commits of drop/ content in any open PR

🤖 Generated with Claude Code

…tories

Two small gitignore additions to prevent accidental commits of
transient / local-only content:

## drop/ — Aaron's human-drop folder

Repo-root `drop/` is Aaron's ferry-space for handing content to
the agent (research reports from Amara via ChatGPT, notes,
transfer artifacts, drafts). Pattern:

1. Aaron drops a file in `drop/`
2. Agent checks at session wake, reads content
3. Agent absorbs into proper substrate (`docs/aurora/`,
   `docs/research/`, `memory/`) with provenance header
4. Raw drop file stays local / transient

Committing raw drop files would ship chat-artifact citation
markers, draft fragments, and other noise that shouldn't
appear in the clean in-repo form. Gitignoring the directory
keeps the ferry loop lightweight.

Pattern documented in per-user memory:
`feedback_drop_folder_ferry_pattern_aaron_hands_off_via_root_drop_dir_2026_04_23.md`.

## .playwright-mcp/ — MCP scratch logs

The Playwright MCP server writes per-session console logs and
ephemeral scratch to `.playwright-mcp/` at repo root. Regenerated
every session, never source. This was already present in one
of the in-flight PR branches' .gitignore; landing it on main
via this hygiene branch so it merges independently of those PRs.

## What this does NOT do

- Does NOT remove the existing `drop/` content — that's
  Aaron's folder to manage
- Does NOT affect other ferry mechanisms (PR comments,
  Slack, email) — those are separate patterns
- Does NOT change absorption policy — signal-preservation
  discipline on ingest still applies

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 23, 2026 14:37
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.

AceHack added a commit that referenced this pull request Apr 23, 2026
Investigated markdownlint failures across 7 demo-cluster PRs
(#141/#145/#146/#147/#142/#143/#144). Scoped back on per-PR
fixes in favor of a higher-leverage next-tick move:
either land #151 (gitignore drop/ on main) or fix the
MD056 tick-history row on main — both would unblock the
whole cluster in one move.

No new PRs this tick. Honest partial-execution per the
prefer-progress-over-quiet-close discipline — documenting
the unblock-vector rather than pushing through with
inefficient per-PR fixes.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.

2 participants