Session log — v0.10.0-2026-03-22-code-untrack-operator-files

Date

2026-03-22

Type

Code (Harley)

Summary

Executed BUILD-untrack-operator-files.md to fix issue #340. Removed 4 operator custom root files (CLAUDE.md, STANDARDS.md, PROJECT-INSTRUCTIONS.md, RELEASE-CHECKLIST.md) from git tracking so branch switches stop overwriting operator custom versions.

What was completed

Created fix/untrack-operator-root-files branch from dev
Updated .gitignore with operator file ignore rules and updated ai-sessions comment
Ran git rm —cached on the 4 files (removed from index, kept on disk)
Committed: “fix: untrack operator custom root files (closes #340)”
Pushed branch and created PR #341 targeting dev
Operator merged PR #341
Verified files are untracked on dev (git ls-files returns nothing)

Issues encountered

After merging to dev, the 4 files were deleted from disk — this is expected git behavior when a merge includes “delete from index” changes. Operator has backups to restore.

Decisions

Used fix/ branch into dev instead of hotfix to main. The previous hotfix approach (PR #324) failed because gitignore only protects untracked files, and dev/staging still tracked them.

Current state

On dev branch, PR #341 merged
4 operator files untracked on dev, need disk restore from backup
Staging and main still track the files — fix propagates via normal release flow

Next steps

Restore 4 operator files from backup
Release flow: dev -> staging -> main to propagate the untrack fix
Restore files again after each merge (git will delete them each time)
Verify end state: branch switches don’t touch operator files