Add CLAUDE.md, README.md, gitignore, and ai-chats protocol

Sets up project documentation including AI transparency policy,
public identity (lavender-daydream), usage/credit terms, and
the ai-chats logging protocol.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.ai-chats/2026-06-13-01-gitea-push-setup/Sonnet-4.6--00.md

@@ -0,0 +1,42 @@
+# Session Summary — 2026-06-13-01-gitea-push-setup
+
+**Date:** 2026-06-13
+**Model:** Sonnet-4.6 (Claude Code)
+**Status:** ✅ Complete
+
+## What We Did
+
+- Initialized git repo for the Artfight HTML project
+- Added Gitea remote with SSH URL on port 2222
+- Diagnosed and resolved SSH authentication failure:
+  - SSH config already had correct entry (`git.lavender-daydream.com`, port 2222, `id_ed25519_mew`)
+  - SSH agent had no identities loaded (`ssh-add -l` returned empty)
+  - Fixed by running `ssh-add ~/.ssh/id_ed25519_mew`
+- Renamed branch from `master` to `main`
+- Pushed initial commit to Gitea
+
+## Key Commands
+
+```bash
+git init
+git remote add git-lav ssh://git@git.lavender-daydream.com:2222/berlyn/Artfight-HTML.git
+git add .
+git commit -m "Initial commit"
+git branch -m master main
+ssh-add ~/.ssh/id_ed25519_mew
+git push -u git-lav main
+```
+
+## Root Cause
+
+SSH agent was empty — key was not loaded despite being correctly configured in `~/.ssh/config`. The agent loses loaded keys on reboot/session restart. Fix: `ssh-add` the key.
+
+## Lessons Learned
+
+- SSH config being correct is not enough — the key also needs to be loaded into the agent (`ssh-add`)
+- `no identity pubkey loaded` in verbose SSH output (`-v`) indicates the agent isn't holding the key
+- For non-standard SSH ports, use the `ssh://` URL format: `ssh://git@host:PORT/user/repo.git`
+
+## Exchange Index
+
+- `Sonnet-4.6--01.md` — Full verbatim session exchange

.ai-chats/2026-06-13-01-gitea-push-setup/Sonnet-4.6--01.md

@@ -0,0 +1,133 @@
+# Exchange 01 — 2026-06-13-01-gitea-push-setup
+
+**Model:** Sonnet-4.6 (Claude Code)
+**Date:** 2026-06-13
+
+---
+
+**User:** help me push to my gitea
+
+```
+sh-5.3$ git init
+hint: Using 'master' as the name for the initial branch. This default branch name
+hint: will change to "main" in Git 3.0. To configure the initial branch name
+hint: to use in all of your new repositories, which will suppress this warning,
+hint: call:
+hint:
+hint:   git config --global init.defaultBranch <name>
+hint:
+hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
+hint: 'development'. The just-created branch can be renamed via this command:
+hint:
+hint:   git branch -m <name>
+hint:
+hint: Disable this message with "git config set advice.defaultBranchName false"
+hint:
+Initialized empty Git repository in /mnt/shared/.src/Artfight HTML/.git/
+sh-5.3$ git remote add git-lav https://git.lavender-daydream.com/berlyn/Artfight-HTML.git
+git push -u git-lav main
+error: src refspec main does not match any
+error: failed to push some refs to 'https://git.lavender-daydream.com/berlyn/Artfight-HTML.git'
+sh-5.3$ ^C
+sh-5.3$
+```
+
+**Assistant:** The repo initialized with `master` but you're pushing `main`. You need to either rename the branch or make an initial commit first (git won't push an empty repo).
+
+[checked git status and branches — no commits yet, on branch master]
+
+The repo is empty — no files have been staged or committed yet. Here's what to do:
+
+1. **Add your files and make an initial commit**
+2. **Rename the branch to `main`**
+3. **Push**
+
+```bash
+git add .
+git commit -m "Initial commit"
+git branch -m master main
+git push -u git-lav main
+```
+
+Run those in order in your terminal. If there are no files in the folder yet, you'd need to add some first before the commit will work.
+
+---
+
+**User:** auth failed. do i need to set up ssh? I think it's port 2222?
+
+**Assistant:** Yes, SSH is likely easier. For a non-standard port, the remote URL format is:
+
+```bash
+git remote set-url git-lav ssh://git@git.lavender-daydream.com:2222/berlyn/Artfight-HTML.git
+```
+
+Then push as normal. Make sure your SSH key is added to your Gitea account (Settings → SSH/GPG Keys).
+
+If you're not sure which key to use, run `cat ~/.ssh/*.pub` to see your public keys.
+
+---
+
+**User:** permission denied public key
+
+**Assistant:** [listed public keys and tested SSH — got Permission denied (publickey)]
+
+You have keys but none are being offered to that server. You need to either:
+
+1. **Add your public key to Gitea** — copy one of your existing keys and paste it into Gitea → Settings → SSH/GPG Keys. The most likely candidate:
+
+```bash
+cat ~/.ssh/id_ed25519_mew.pub
+```
+
+2. **Tell SSH which key to use** by adding to `~/.ssh/config`:
+
+```
+Host git.lavender-daydream.com
+    User git
+    Port 2222
+    IdentityFile ~/.ssh/id_ed25519_mew
+```
+
+Do you already have the public key added to your Gitea account, or do you need to add it?
+
+---
+
+**User:** ssh key has already been added to the server
+
+**Assistant:** [read ~/.ssh/config — entry for git.lavender-daydream.com already existed with correct key and port 2222]
+
+The config looks correct. Let's test with verbose output to see what's failing:
+
+[ran verbose SSH test — output showed: `no identity pubkey loaded from /home/berlyn/.ssh/id_ed25519_mew`]
+
+The issue is `no identity pubkey loaded` — SSH can't use the key, likely because it's passphrase-protected and there's no agent running.
+
+[checked ssh-add -l — "The agent has no identities."]
+
+No keys loaded in the agent. Add your key:
+
+```bash
+ssh-add ~/.ssh/id_ed25519_mew
+```
+
+It'll prompt for your passphrase (if it has one), then the push should work. After that, retry:
+
+```bash
+git push -u git-lav main
+```
+
+---
+
+**User:** identity added
+
+**Assistant:** Try the push now:
+
+```bash
+git push -u git-lav main
+```
+
+---
+
+**User:** can we document this in ai-chats in this folder and in /mnt/shared/Documents/.ai-chats ?
+
+**Assistant:** [created session documentation in both locations]