Chronicle Handoff page

HANDOFF — Nick / Chronicle (Cursor + GitHub)

Add today’s date when you publish/save.

Quick links (clickable)

How to work with Nick

  • Very capable engineer; loses patience with vague/contradictory/“I assumed…” answers.
  • Preferred style: short numbered steps, full paths, what “done” looks like after each step.
  • Don’t tell Nick what he’s going to do; wait for his instructions.
  • Screenshots: be honest about limits; ask for a crop if text isn’t readable.
  • Hard rule: no file edits unless Nick explicitly approves that exact change in that exact place.

Intended workflow (Nick’s plan)

  • Clean/audit on local Windows “clean room”, not on the live deployment tree for risky work.
  • Clean-room folder: C:\Users\nick\Desktop\clean room- wire to server
  • Cursor rules folder: C:\Users\nick\Desktop\clean room- wire to server\.cursor\rules
  • Git flow: branch like cleanup/code-audit → PR → Nick reviews → merge to main → promote to live per Nick.

GitHub / repo facts

  • Trunk branch: main (master removed on remote during this thread; main was force-updated to the real codebase commit.)
  • SSH remote: [email protected]:sailingwaves-boop/Chronicle-soft.git

SSH key files (Linux host used in this thread)

  • Private (never paste into chat): /root/.ssh/chronicle_soft_github
  • Public (GitHub Deploy key): /root/.ssh/chronicle_soft_github.pub
  • SSH config: /root/.ssh/config (GitHub host → IdentityFile ~/.ssh/chronicle_soft_github)

What was verified in this thread

  • git fetch / git pull / git push to origin/main worked after deploy key setup.
  • deploy.sh at repo root was repaired (previously corrupted) and pushed (message like “Fix deploy.sh: valid clone script”; commit c075fa8 appeared during the session).

Cursor / workspace reality

  • Agent file tools only see the Cursor workspace root opened for that chat.
  • Typing a Windows path in chat does not mount it into a Remote-SSH workspace session.
  • To work on the clean-room folder: open that folder as the local Cursor project, or paste file contents into chat.

Repo layout warning (commits)

  • Parent checkout treated app/ as a gitlink/submodule-style path (160000) without a normal submodule checkout in this environment.
  • git add app/frontend/src/App.js from the parent failed: “Pathspec … is in submodule app”.
  • Don’t assume git add app/... works from the parent until submodule layout is repaired or commits are done from the correct nested repo.

Serious trust incident (must respect)

  • Nick gave a clear pipeline (local clean → GitHub → review → deploy).
  • Assistant edited app/frontend/src/App.js in the opened remote workspace without explicit per-file approval for that environment.
  • Assistant reverted those edits afterward — Nick should still verify (diff/tests/run app).

Saving chats

  • Long threads may not copy with Ctrl+A; scroll to load, copy in chunks.
  • Optional tooling: see the “exporting chats” forum link above.

Do not

  • Edit live trees when Nick says local clean-room only.
  • Paste private keys into chat.
or
Scroll to Top