Ecosystem Optimization: Adopt Shared Infrastructure & Standards

[Kanevry]

GitLab #1

Ecosystem Optimization — What Changed

The Goetzendorfer ecosystem has been upgraded with shared infrastructure, centralized knowledge, and automation. Here's what's new and what action items exist for this repo.

Global Changes (already live)

1. GitLab CE → EE 18.9.1 — Premium features now available (Epics, Group Boards, Required Approvals)
2. Group Labels — Standardized across all groups: P0-P3 priority, bug/feature/tech-debt/security/compliance types, needs-triage/in-progress/review/blocked status
3. Group Milestones — Q2-Q4 2026 + "Ecosystem Optimization" milestone
4. CI/CD Components Catalog — 6 reusable components in infrastructure/ci-components:
   • validate (TypeScript + ESLint + Prettier)
   • security (Gitleaks + pnpm audit)
   • test (Vitest + Coverage)
   • deploy-vercel (Preview/Production)
   • deploy-docker (Docker Build + Deploy)
   • publish-package (GitLab Package Registry)
5. New Shared Packages (in projects-baseline/packages/):
   • @goetzendorfer/supabase-helpers — requireAuth(), error classes, client/server
   • @goetzendorfer/zod-schemas — Austrian + common validation schemas
   • @goetzendorfer/logger — Pino + Sentry structured logging
   • @goetzendorfer/testing-utils — Supabase mocks, test factories
   • @goetzendorfer/ui-primitives — EUR formatting, Austrian locale
6. Renovate Bot — Automated dependency updates (Saturdays 6-10am), auto-merge patches for trusted packages
7. Knowledge Gardener (Clank) — Weekly doc freshness checks, compliance tracking, change detection on push

Action Items for This Repo

• Review and update CLAUDE.md if missing or outdated
• Ensure .claude/rules/ directory exists with baseline rules
• Add .gitleaks.toml if missing
• Add .mcp.json with context7 MCP server if missing
• Ensure .env patterns in .gitignore
• Add lint:fix and typecheck scripts to package.json if applicable
• Consider migrating CI/CD to use shared components from infrastructure/ci-components
• Consider adopting shared packages where applicable (@goetzendorfer/supabase-helpers, @goetzendorfer/zod-schemas, etc.)
• Use standardized Group Labels on all new issues

References

• Baseline repo: infrastructure/projects-baseline
• CI Components: infrastructure/ci-components
• Compliance check: bash scripts/sync-baseline.sh (in baseline repo)
• Compliance push: bash scripts/compliance-push.sh (in baseline repo)

[Kanevry]

Housekeeping Session Progress (2026-04-06)

Addressed the following checklist items for this Swift/Xcode project:

• CLAUDE.md — Created with project overview, build/test commands, structure, CI info
• .gitleaks.toml — Added with sensible defaults for Swift project
• .gitignore — Added .env / .env.* / .env.local patterns

Not applicable (Swift project, not Node.js):

• lint:fix / typecheck scripts in package.json
• CI/CD shared components (Xcode-specific pipeline)
• Shared npm packages

Remaining:

• .claude/rules/ baseline rules — deferred to next session
• .mcp.json with context7 — deferred (no MCP integration needed for native Swift)
• Standardized Group Labels on new issues