mempalace init writes entities.json and mempalace.yaml to project directory instead of ~/.mempalace/

[fubak]

Issue

mempalace init <dir> writes two config files into the target project directory:

• <dir>/entities.json
• <dir>/mempalace.yaml

These land alongside the user's project files rather than in ~/.mempalace/ where config.json lives. This creates clutter, risks accidental commits, and splits mempalace config across two locations with no clear rationale.

Steps to Reproduce

mempalace init /home/fubak/projects/myapp
ls /home/fubak/projects/myapp/
# → entities.json  mempalace.yaml  (plus all existing project files)
ls ~/.mempalace/
# → config.json  palace/

Expected

All mempalace config files should live in ~/.mempalace/, or at minimum be namespaced by wing to avoid collisions across projects:

~/.mempalace/
  config.json
  palace/
  wings/
    myapp/
      entities.json
      mempalace.yaml

Impact

• Files in project root risk being committed to git (no default .gitignore entry added)
• Running mempalace init on multiple projects scatters config files with identical names across the filesystem
• Users initializing on a root directory (e.g. /home/fubak) get config files in their home dir root

Environment

• mempalace 3.0.0

[ttquoccuong]

i already have PR for this.
look at #933