Document cleanup for agent temp artifacts (_encode_commit_payload.py, _emit_payload.py) #261
Closed
opened 2026-07-06 12:09:31 -05:00 by jcwalker3
·
4 comments
No Branch/Tag Specified
master
fix/issue-709-decision-lock-cross-profile
fix/issue-695-native-transport-quarantine
fix/issue-698-report-validator-schema
fix/issue-702-stale-binding-lease-recovery
fix/issue-699-structured-auth-mcp-errors
fix/issue-695-native-quarantine-v2
fix/issue-693-review-decision-lock-recovery
fix/issue-691-obsolete-reviewer-lease-cleanup
feat/issue-687-reconciler-branch-delete
fix/issue-683-workflow-guard-hardening
chore/issue-681-preserve-review-session-wip
feat/issue-604-anti-stomp-preflight
feat/issue-606-sentry-observability
fix/issue-671-block-stable-branch-push
fix/issue-675-residual-preflight-remediation
fix/issue-673-remediate-regressions-part2
fix/issue-673-remediate-regressions
feat/issue-603-lifecycle-labels
fix/issue-627-set-issue-labels-pagination
feat/issue-601-first-class-leases
feat/issue-612-incident-bridge
feat/issue-600-controller-allocator-api
fix/issue-620-head-scoped-review-locks
feat/issue-613-allocator-db-substrate
docs/mcp-stable-control-runtime-policy
feat/issue-609-prepared-review-verdict-resume
feat/issue-610-live-remote-parity
feat/issue-503-reviewer-active-worktree
feat/issue-470-preflight-contract
feat/issue-440-lock-recovery
feat/issue-440-branch-recovery
feat/issue-458-queue-fail-closed-copy
feat/issue-400-early-duplicate-work-gate
feat/issue-308-reconcile-inventory-pagination
feat/issue-308-reconcile-pagination-proof
docs/issue-261-agent-temp-artifact-cleanup
feat/issue-262-map-commit-files
fix/infra-stop-conflict-marker-false-positive
feat/issue-139-role-aware-task-routing
feat/issue-188-continuation-selection-wall
feat/issue-189-continuation-mode-proofs
feat/issue-232-refresh-wiki-proof-heads
feat/issue-210-block-workspace-edits
feat/issue-204-exact-issue-lock
docs/issue-80-label-taxonomy
docs/issue-79-safety-boundary-updates
v1.1.0
Labels
Clear labels
allocator
anti-stomp
architecture
bug
chore
codex
concurrency
contamination
control-plane
dashboard
database
design
documentation
enhancement
gitea
glitchtip
important
incident
incident-bridge
integration
jenkins
labels
leases
mcp
mcp-health
mcp-menu
multi-project
mutating
nice-to-have
observability
portability
preflight
protected-branch
queue
read-only
reconnect
recovery
refactor
release
reliability
resumable-review
reviewer
roadmap
safety
security
self-hosted
sentry
stale-runtime
status:blocked
status:in-progress
status:pr-open
status:ready
terminal-lock
testing
tracker
type:bug
type:feature
type:feature
type:guardrail
visibility
workflow
workflow-hardening
workflow-hardening
Controller-owned work allocator
Prevent concurrent LLM session stomping
Architecture / structural design
OpenAI Codex client / workflow session surface
Concurrent session safety
Workflow or session contamination incident
MCP control-plane coordination and allocation authority
MCP operational dashboard/queue view
Internal coordination storage (SQLite/Postgres)
Design / investigation, no implementation
Docs / runbooks
New feature or improvement
Gitea MCP workflow
GlitchTip integration
Operational or process incident requiring durable audit trail
Sentry-to-Gitea incident bridging
Integration testing
Jenkins integration
Label taxonomy management
Lease adopt/release/expire lifecycle
MCP server / tooling
MCP namespace and runtime health
MCP menu surface
Work spanning multiple monitoring projects or Gitea repos
Mutating action; requires gating
Observability, metrics, traces, error reporting
Cross-platform / portability
Shared preflight gates before mutation
Protected branch / stable-branch policy concern
Work queue visibility and allocation
Read-only, no mutation
MCP client reconnect/reload recovery path
Recovery paths for stale/foreign leases
Code refactor / restructure
Release / versioning
Reliability / failure handling
Persist and resume prepared review verdicts across sessions
Reviewer workflow tooling
Roadmap / umbrella issue
Safety rails and fail-closed mutation guards
Security / trust boundary
Self-hosted infrastructure integration
Sentry error monitoring integration
Stale backend daemon / runtime-vs-master parity failures
Issue is blocked
Issue is being worked on
Issue has an open pull request
Issue is ready for work
Terminal review lock (#332) path
Tests / test coverage
Issue tracker hygiene / meta
Bug or defect
Feature or enhancement
Feature or enhancement
Safety gate or guardrail
Workflow state visibility for LLMs/operators
Cross-tool workflow
LLM workflow coordination hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Scaled-Tech-Consulting/Gitea-Tools#261
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Failed subagent runs left throwaway helper scripts in the repo working tree:
_encode_commit_payload.py_emit_payload.pyThese are not part of any issue scope and pollute
git status, triggering issue-lock / preflight failures.Proposal
_encode_*/_emit_*/_inline_*agent artifacts after MCP commit completes or aborts..gitignoreor a documented cleanup checklist._*.pyhelper patterns appear before lock.Acceptance
Context
Left behind during #152 attempt; worsened
gitea_lock_issuefailure (tracked edits before lock).Claimed. Branch:
docs/issue-261-agent-artifact-cleanup. Worktree:branches/docs-issue-261-agent-artifact-cleanup.Plan: add
.gitignorepatterns for throwaway agent commit helpers (_encode_*,_emit_*,_inline_*) and document post-session cleanup indocs/llm-workflow-runbooks.md.Claimed. Branch:
docs/issue-261-agent-temp-artifact-cleanup. Worktree:branches/docs-issue-261-agent-temp-artifact-cleanup.Scope for this slice (per issue proposal + acceptance):
.gitignorepatterns for_encode_*.py/_emit_*.py/_inline_*.pyagent helper artifactsdocs/llm-workflow-runbooks.mdThe optional preflight warning for
_*.pyhelper patterns is left as follow-up (marked optional in the issue).Retracting my claim above —
gitea_lock_issuefail-closed: PR #277 (docs/issue-261-agent-artifact-cleanup) already carries this issue and was opened in the window between my lease sweep and my lock attempt. That session owns the lease; I releasedstatus:in-progressand will not branch or PR for this issue. No code or branch was created under my claim.Standing down on this issue per the Work Selection Rule (no parallel PRs).
Timeline: this session claimed #261 with
status:in-progress, locked it viagitea_lock_issueto branchdocs/issue-261-agent-temp-artifact-cleanup, implemented (runbook section +.gitignorepatterns + 7 doc-contract tests, full suite green except one pre-existingtest_role_session_router.py::TestCheckMidMerge::test_skip_scan_walk_root_skips_sibling_worktrees_onlyfailure reproduced on clean master), and pushed commita55e937. A concurrent session then opened PR #277 (branchdocs/issue-261-agent-artifact-cleanup) for the same issue; the shared/tmp/gitea_issue_lock.jsonlock was also consumed between my lock and PR creation (evidence for #267/#268).Disposition: no PR was created from my branch.
docs/issue-261-agent-temp-artifact-cleanup(heada55e937) is redundant once PR #277 merges and is safe for an operator to delete then — this profile lacksgitea.branch.delete. If #277 misses anything, that branch also contains an independent implementation with tests for comparison.