Document repo structure and ignore local OMX state
Add a root README that explains the active runtime layers and onboarding path, and keep local OMX session state out of version control so developer tooling does not interfere with pulls. Constraint: Local OMX state is developer-specific and should not block branch sync or appear in shared history Rejected: Keep onboarding notes untracked | easy to lose and hard to share with the team Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep the README aligned with the active app/backend-java/frontend-vue execution path; revisit if the runtime architecture changes Tested: git diff review; git status after staging Not-tested: lint, typecheck, unit/integration tests not run (docs and ignore rules only)
This commit is contained in:
1
.gitignore
vendored
1
.gitignore
vendored
@@ -43,3 +43,4 @@ app/assets/
|
||||
app/new_web_source
|
||||
app/user_data/
|
||||
OPS_REDIS_MYSQL_OPTIMIZATION_NOTES.md
|
||||
.omx/
|
||||
|
||||
Reference in New Issue
Block a user