Version Logger Workflow:
- [ ] Step 1: Gather change context
- [ ] Step 2: Generate Log ID
- [ ] Step 3: Create Master Log entry
- [ ] Step 4: Update PROJECT_OVERVIEW.md (if files changed)
- [ ] Step 5: Update README.md (if public-facing changes)
- [ ] Step 6: Verify dev pages will reflect updates
- [ ] Step 7: Report completion to primary agent

---

## AU-C01-YYYYMMDD-NNN — Title (short + specific)

**Type:** Feature | Fix | Refactor | Decision | Docs | Ops  
**Context:** why this work happened / trigger  
**Change summary:** what changed (plain English)  
**Rationale / tradeoffs:** why this approach, what alternatives were rejected  
**Files touched:**
- `path/to/file1.ext`
- `path/to/file2.ext`

**Commands run:**
```bash
commands executed

### Entry Type Guidelines

| Type | Use When |
|------|----------|
| Feature | New capability or functionality |
| Fix | Bug fix or error correction |
| Refactor | Code restructuring without behavior change |
| Decision | Choosing between alternatives (ADR-lite) |
| Docs | Documentation-only changes |
| Ops | Deployment, infrastructure, or operational changes |

### Concept Tags

Use `@concept:slug` for cross-reference. Common tags:

- `@concept:branding` — Logo, colors, visual identity
- `@concept:auth` — Authentication/authorization
- `@concept:api` — API endpoints
- `@concept:frontend` — UI/UX changes
- `@concept:deployment` — Deployment/infrastructure
- `@concept:atlas-forge` — AtlasForge playground
- `@concept:quickpro` — QuickPRO/AtlasOps app
- `@concept:master-log` — Documentation system

---

## Step 4: Update PROJECT_OVERVIEW.md

Update `docs/master_log/PROJECT_OVERVIEW.md` when:

1. **New files created** — Add to appropriate section
2. **Files deleted** — Remove from inventory
3. **New directories added** — Add new section
4. **File purpose changed** — Update description

### Update Process

1. Read current PROJECT_OVERVIEW.md
2. Identify which section(s) need updating based on file paths:
   - `atlasops/` → Backend sections
   - `atlasforge/` → Atlas Forge section
   - `frontend-main/` → Main Portfolio Site section
   - `frontend/` → QuickPRO Frontend section
   - `deploy/` → Deployment section
   - etc.
3. Add/remove entries in the appropriate table
4. Update "Last Updated" date in header

### File Entry Format

```markdown
| `filename.ext` | Brief description of purpose |

# AtlasOps

## Features
- Feature list with brief descriptions

## Tech Stack
### Backend / ### Frontend
- Technology: version and purpose

## Development Setup
### Prerequisites / ### Backend Setup / ### Frontend Setup
- Step-by-step instructions

## Project Structure
- Directory tree with descriptions

## API Endpoints
### Authentication / ### Jobs / ### Profile / ### Applications
- `METHOD /path` - Description

## Environment Variables
- Variable explanations and examples

## User Management Scripts
- Script commands and descriptions

## Deployment
- Deployment instructions and secrets

Version Logger Complete:
- Log Entry: AU-C01-YYYYMMDD-NNN
- Title: [entry title]
- Files updated:
  - docs/master_log/Master_Log.md ✓
  - docs/master_log/PROJECT_OVERVIEW.md [✓ if updated | — if unchanged]
  - README.md [✓ if updated | — if unchanged]
- Dev pages will auto-refresh on next load

## AU-C01-20260131-003 — Add library lazy-loading for Atlas Forge

**Type:** Feature  
**Context:** User requested full integration of major UI libraries with lazy-loading  
**Change summary:** Created dynamic library loader system with lazy imports for Vue and React UI libraries  
**Rationale / tradeoffs:** Dynamic imports ensure fast initial load (~150KB), libraries load on-demand  
**Files touched:**
- `atlasforge/src/lib/library-loader.ts`
- `atlasforge/src/lib/libraries/vuetify-loader.ts`
- `atlasforge/package.json`

**Commands run:**
```bash
cd atlasforge && npm install && npm run build

### Example 2: Bug Fix

```markdown
## AU-C01-20260131-004 — Fix scroll indicator overlap on homepage

**Type:** Fix  
**Context:** User reported animated scroll arrow overlapping CTA buttons  
**Change summary:** Moved scroll indicator outside content container, adjusted positioning  
**Rationale / tradeoffs:** Element was inside flex container causing overlap; absolute positioning relative to viewport prevents this  
**Files touched:**
- `frontend-main/src/components/HeroSection.vue`

**Commands run:**
```bash
git add && git commit && git push

### Example 3: Decision Record

```markdown
## AU-C01-20260131-005 — Select Orbital Hexagon as final logo

**Type:** Decision  
**Context:** User evaluated 5 hexagonal logo variations  
**Change summary:** Updated atlas-icon.svg with Orbital Hexagon design (bold hexagon, crossing orbital ellipses, A letterform, gold satellite nodes)  
**Rationale / tradeoffs:** 
- Alternatives considered: Layered Depth, Circuit Network, Segmented Modern, Crystalline Gem
- Orbital System chosen for dynamic feel and global reach suggestion
- Works well at small sizes (16px, 32px, 64px)

**Files touched:**
- `frontend-main/public/atlas-icon.svg`

**Commands run:**
```bash
git commit -m "Update logo to Orbital Hexagon design"

---

## Integration with Primary Agents

### How Primary Agents Should Invoke

After completing work, the primary agent should:

1. Call this skill explicitly: "Invoke the version-logger skill"
2. Provide context about changes made
3. Wait for completion confirmation

### Automatic Invocation Triggers

Primary agents should invoke this skill after:

- Any file write operation
- Git commit or push
- SSH commands to production server
- Database migrations
- Package installations
- Configuration changes

### Commit Message Convention

Include the Log ID in commit messages:

```bash
git commit -m "AU-C01-20260131-003: Add library lazy-loading for Atlas Forge"

# Windows
.\scripts\build_master_log.ps1

# Linux/Mac
./scripts/build_master_log.sh