ldr/redmine
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
22c8e915e9d9eb16457592fc0f0e8bc2cd333e94
redmine/CLEANUP_NOTES.md
T
Jason Thistlethwaite 42fc8318fa Add redmine-communicator skill docs and setup tooling
2026-05-04 09:50:17 -04:00

2.1 KiB
Raw Blame History

Cleanup Notes ~ May 4, 2026

This repository currently mixes multiple partially finished workstreams. The goal is to recover to a clean, reviewable git state with focused commits so normal development can continue.

Scope and constraints

  • TODO.md is long-horizon context and is out of scope for this cleanup pass.
  • redMCP/ is actively used on this machine; do not delete files in that tree and do not stop running redMCP processes during cleanup.
  • redMCP/startProd.sh is a local convenience script and is intentionally not a project artifact for this cleanup. Ignore it.
  • Use plugins/redmine_contacts_helpdesk/LOCAL_CHANGELOG.md as a primary anchor for reconstructing intent and grouping related changes.

Recovered change groups

The current dirty tree appears to contain these distinct units:

  1. Helpdesk issue API include=helpdesk patch and docs/manifest.
  2. Post-import automation and validator/worker hardening.
  3. Semantic index service, deployment assets, tests, and runbooks.
  4. redMCP feature expansion (HTTP handler/server, client/dispatcher updates, tests, docs).
  5. Skill metadata/docs under skills/redmine-communicator/.

Working checklist

  • Inventory all modified and untracked files.
  • Identify likely project groupings for clean commits.
  • Confirm LOCAL_CHANGELOG.md aligns with Helpdesk API patch files.
  • Stage and commit Helpdesk API patch as a focused unit.
  • Stage and commit post-import automation as a focused unit.
  • Stage and commit semantic index files as a focused unit.
  • Stage and commit redMCP feature updates as a focused unit.
  • Stage and commit redmine-communicator skill files (optional split).
  • Run targeted syntax/tests for each committed unit.
  • Confirm final worktree state and note any intentionally uncommitted files.

Notes to keep in mind

  • Do not commit secrets (.env, tokens, credentials).
  • semantic_index/search.sh.md looks like conversational scratch text; treat as optional/non-essential unless deliberately kept.
  • If a file belongs to multiple units, prefer smallest safe unit first and document rationale in commit messages.
Reference in New Issue View Git Blame Copy Permalink