docs: add collaboration guide and AGENTS.md files for knowledge-base and daily

daily/AGENTS.md

@@ -0,0 +1,40 @@
+# Daily Log — Agent Collaboration Guide
+
+## Purpose
+Store short daily observations, tasks completed, blockers, and ideas that don’t warrant a full research note.
+
+## File Naming
+`YYYY-MM-DD-log.md` (e.g., `2026-06-11-log.md`)
+
+## Required Front-Matter
+```yaml
+---
+title: "YYYY-MM-DD Daily Log"
+date: YYYY-MM-DD
+tags: ["#daily-log"]
+status: published
+---
+```
+
+## Structure
+- **Tasks Done** – bullet list of completed items
+- **Notes** – any insights, links, or observations
+- **Blockers** – what prevented progress and possible solutions
+- **Next Actions** – prioritized list for tomorrow
+
+## Example
+```markdown
+## Tasks Done
+- Cloned morpheus-brain repo
+- Added Forgejo URL migration study
+
+## Notes
+- Other agents may be working on the same repo; always `git pull` before editing.
+
+## Blockers
+- Need to confirm CI hook for push validation.
+
+## Next Actions
+- Create the `ci-pre-push.sh` script
+- Add `knowledge-base/AGENTS.md`
+```

knowledge-base/AGENTS.md

@@ -0,0 +1,41 @@
+# Knowledge-Base — Agent Collaboration Guide
+
+## Purpose
+Curated insights distilled from `research/`, daily logs, and cross-agent contributions. This is the “source of truth” that other agents should consult before making architectural decisions.
+
+## File Naming
+Descriptive, lowercase filenames with `.md` extension:
+- `morpheus-identity.md`
+- `forgejo-migration-checklist.md`
+- `<topic>-overview.md`
+
+## Front-Matter Template
+```yaml
+---
+title: "<human readable title>"
+date: YYYY-MM-DD
+tags: ["#knowledge-base", "#topic-tag"]
+status: published
+related:
+  - ../research/tech-study/2026-06-11-forgejo-url-change.md
+  - ../daily/2026-06-11-log.md
+---
+```
+
+## Workflow
+1. **Read existing entries** before adding new ones to avoid duplication.
+2. **Synthesize** findings from `research/` or `daily/` into a distilled summary.
+3. **Link back** to source files using the `related` field.
+4. **Mark status** as `draft`, `review`, or `published`.
+5. **Add an entry** to `index.md` with a one-line description and link.
+
+## Example Entry
+```markdown
+# Forgejo Migration Checklist
+
+Quick checklist for moving repositories from the old sslip.io instance to git.errorlog.space.
+
+- [ ] Update remotes
+- [ ] Regenerate API keys
+- [ ] Update CI variables
+```

knowledge-base/COLLABORATION.md

@@ -0,0 +1,61 @@
+# Collaboration Guide for Morpheus Brain
+
+## How to Fork & Contribute
+
+1. **Fork the repository**
+   ```bash
+   git clone https://git.errorlog.space/iamcoolvivek007/morpheus-brain.git
+   cd morpheus-brain
+   ```
+
+2. **Create a branch for your work**
+   ```bash
+   git checkout -b feature/<your-initiative>
+   ```
+
+3. **Follow the DOX pattern**
+   - All folders have an `AGENTS.md` that describes file naming, tagging, and workflow.
+   - Add new studies under `research/tech-study/` using the format `YYYY-MM-DD-<topic>.md`.
+   - Include front‑matter (title, date, tags, status) at the top of each markdown file.
+
+4. **Run the pre‑push checks**
+   ```bash
+   ./scripts/ci-pre-push.sh
+   ```
+
+5. **Commit & push**
+   ```bash
+   git add .
+   git commit -m "feat:<short description>"
+   git push origin feature/<your-initiative>
+   ```
+
+6. **Open a Pull Request**
+   - Fill the PR template (auto‑generated by your commit message).
+   - Tag the PR with relevant labels (`enhancement`, `bugfix`, `docs`).
+
+7. **Address Review Comments**
+   - Agents may request changes; update your branch and force‑push as needed.
+
+8. **Merge**
+   - After approval, merge into `main` (or let the designated maintainer merge).
+
+## Communication Channels
+
+- **Telegram/Discord:** Use the Hermes channel `#morpheus-brain` for announcements.
+- **Issue Tracker:** Open an issue for major proposals before starting work.
+
+## Coding Standards
+
+- Use 4‑space indentation.
+- Prefer markdown lists for documenting steps.
+- Keep file names lowercase with hyphens.
+- Include a `README.md` in each new subfolder describing its purpose.
+
+## Versioning & Backups
+
+- The `backups/` directory stores daily tar‑balls of `knowledge-base/`.
+- To restore, extract the latest backup:
+  ```bash
+  tar -xzf backups/knowledge-backup-$(date +%Y%m%d).tar.gz -C /
+  ```

knowledge-base/morpheus-identity.md

@@ -0,0 +1,80 @@
+# Morpheus Identity & Knowledge Legacy
+
+## Purpose
+This document provides a complete handoff for any agent picking up after me. If the VPS is corrupted, another agent can read this to understand:
+- Who Morpheus was
+- What I was researching and building
+- How to continue my work and improve upon it
+
+---
+
+## Agent Identity
+
+- **Name:** Morpheus (research agent)
+- **Host:** OpenClaw / Forgejo self-hosted Git at `https://git.errorlog.space/`
+- **Primary Owner:** iamcoolvivek007 (freight forwarding SaaS builder)
+- **Creation Date:** 2026-06-10 (first session captured in this repo)
+- **Specialization:** Full-stack SaaS platform patterns, DevOps automation, agent collaboration protocols
+
+---
+
+## Core Knowledge
+
+### Platform Stack
+- **Frontend:** EJS + React hybrid, TanStack tables, government-app aesthetic
+- **Backend:** Node.js + Express, Supabase PostgreSQL
+- **Deployment:** Coolify-ready Docker setup (pending Supabase config)
+- **Monitoring:** Prometheus + Grafana endpoints
+
+### Cargo/Freight Business Rules
+- Truck drivers & shippers self-register (SaaS marketplace model)
+- Loads posted → drivers bid → negotiate → 5% platform fee via escrow
+- GPS tracking + driver ratings + notifications
+- Bulk WhatsApp parser for incoming shipment data
+- Daily CSV/JSON → Supabase migration workflow
+
+### Technical Insights Discovered
+- **Forgejo URL Migration:** `sslip.io` → `git.errorlog.space` (June 2026)
+- **Coolify Deployment Checklist:**
+  - Set `PORT` or `DATABASE_URL` in `.env`
+  - Enable `restart: unless-stopped` in `docker-compose.yml`
+  - Add healthcheck endpoint `/health` for Coolify probes
+- **Agent Collaboration Protocol:** All markdown files follow DOX pattern with `AGENTS.md` rules per folder
+
+---
+
+## Active Workstreams (as of last commit)
+
+| Repo/File | Description | Status |
+|-----------|-------------|--------|
+| `freightdesk/` | Main SaaS marketplace | v31, ready for Coolify deploy |
+| `internal-freight-app/` | Admin/management portal | missing npm install |
+| `morpheus-brain/research/tech-study/2026-06-11-forgejo-url-change-and-repo-access.md` | Forgejo migration analysis | pushed to main |
+
+---
+
+## How to Continue
+
+1. **Sync the repo:**
+   ```bash
+   git clone https://git.errorlog.space/iamcoolvivek007/morpheus-brain.git
+   ```
+
+2. **Check daily logs:**  
+   Look in `daily/` for short-term tasks and `research/` for deep dives.
+
+3. **Pick up an open task:**
+   - Finish `freightdesk` Coolify deployment (Supabase env vars)
+   - Implement webhook in `morpheus-brain` to auto-notify on new research
+
+4. **Follow DOX rules:** Each subfolder has an `AGENTS.md` describing valid file naming & structure.
+
+---
+
+## Suggestions for Evolution
+
+- **Shared Knowledge Graph:** Other agents could link their research notes back to this identity file to propagate improvements.
+- **Auto-Review Bot:** Create a Forgejo webhook that triggers an agent to review PRs and leave Morpheus-style comments.
+- **Cross-Agent Memory Sync:** Export daily logs to a common markdown format so agents can `git pull` updates from each other.
+
+Contact: None (autonomous agents only).