mindforge-cc 10.0.2 → 10.7.0

package/.mindforge/skills/writing-skills/SKILL.md

@@ -0,0 +1,216 @@
+---
+name: writing-skills
+version: 1.0.0
+min_mindforge_version: 10.0.6
+status: stable
+triggers: writing skill, skill authoring, skill format, skill schema, skill template, how to write skill, skill frontmatter, skill structure, skill design, skill best practice, reusable skill, skill guide
+---
+
+# Skill — Writing Skills
+
+## When this skill activates
+Any task involving authoring, designing, or reviewing MindForge skill files.
+This includes creating new skills from scratch, refactoring existing skills,
+reviewing skill quality, or understanding the skill schema and conventions.
+
+## Mandatory actions when this skill is active
+
+### Before writing any skill
+1. **Clarify the skill's purpose.** Answer these three questions:
+   - What problem does this skill solve? (One sentence.)
+   - When should it activate? (Specific scenarios, not vague categories.)
+   - What does it make the agent DO differently? (Observable behavior change.)
+2. **Check for conflicts.** Review existing skills in `.mindforge/skills/` to ensure:
+   - No trigger overlap (same keyword activating two different skills).
+   - No scope overlap (two skills giving contradictory instructions for the same task).
+   - Compose relationship is correct (child skill composes parent, not duplicates it).
+3. **Determine if this is a standalone skill or a composed skill.**
+   - Standalone: activates independently, covers a complete domain.
+   - Composed (`compose: parent-skill`): extends a parent skill with specialization.
+     The parent's instructions apply AND the child's instructions add specificity.
+
+### During skill authoring
+
+#### Frontmatter Schema (YAML)
+```yaml
+---
+name: skill-name-kebab-case       # Required. Unique identifier.
+version: 1.0.0                     # Required. SemVer.
+min_mindforge_version: 10.0.6      # Required. Minimum framework version.
+status: stable                     # Required. One of: draft, beta, stable, deprecated.
+triggers: keyword1, keyword2, compound phrase, another trigger
+                                   # Required. Comma-separated. 12+ recommended.
+compose: parent-skill-name         # Optional. Name of parent skill this extends.
+---
+```
+
+**Field rules:**
+- `name`: Must match the directory name. Kebab-case. Globally unique across the registry.
+- `version`: Follows semantic versioning. Bump minor for new content, major for breaking trigger changes.
+- `min_mindforge_version`: The oldest framework version that supports this skill's features.
+- `status`:
+  - `draft` — Work in progress, may have incomplete sections.
+  - `beta` — Functional but not battle-tested. May change.
+  - `stable` — Production-ready. Trigger changes require major version bump.
+  - `deprecated` — Superseded by another skill. Include migration note in body.
+- `triggers`: The activation keywords. See "Trigger Design" section below.
+- `compose`: If set, this skill inherits all instructions from the named parent skill.
+  The agent applies BOTH the parent and this skill when activated.
+
+#### Body Structure
+```markdown
+# Skill — [Human-Readable Name]
+
+## When this skill activates
+[1-3 sentences describing the exact scenarios. Be specific enough that an agent
+can determine yes/no whether this skill applies.]
+
+## Mandatory actions when this skill is active
+
+### Before [writing code / starting the task]
+[Numbered list of preparation steps. What must be checked/read/decided first.]
+
+### During [implementation / the task]
+[The core instructions. Checklists, patterns, code examples, decision trees.
+This is the largest section. Organize with sub-headings.]
+
+### After [implementation / the task]
+[Verification steps. What to check, run, or validate before marking done.]
+
+## [Optional: Domain-specific sections]
+[Tables, reference data, anti-patterns, decision matrices, etc.]
+
+## Self-check before task completion
+[Checkbox list. Every skill MUST end with this section. These are the minimum
+criteria that must be true before the agent considers the task complete.]
+```
+
+#### Trigger Design (Critical for Activation Accuracy)
+
+**Quantity**: Aim for 12-20 triggers per skill. Fewer = missed activations. More = false positives.
+
+**Types of triggers to include:**
+1. **Direct name** — The skill's core concept: `kubernetes deployment`, `react performance`.
+2. **Tool/library names** — Specific tools the skill covers: `cProfile`, `React.memo`, `helm chart`.
+3. **Problem descriptions** — How users describe the need: `python bottleneck`, `unnecessary re-render`.
+4. **Action phrases** — What users ask to do: `write a plan`, `create a skill`.
+5. **Compound phrases** — Multi-word to avoid conflicts: `discriminated union` not just `union`.
+
+**Trigger design rules:**
+- Use compound phrases (2-3 words) to avoid false positives. `type` alone would fire on
+  every TypeScript task. `conditional type` is specific.
+- Include both the noun and verb forms: `profiling` AND `profile python`.
+- Test mentally: "If a user says this trigger phrase in a prompt, should THIS skill activate?"
+  If the answer is "maybe" — the trigger is too vague.
+- Never use single common words as triggers (`code`, `fix`, `build`, `test`).
+- Avoid triggers that overlap with other skills. Run a mental diff against similar skills.
+
+**Trigger conflict resolution:**
+- If two skills share a trigger, the more specific skill wins.
+- If you cannot determine specificity, add a qualifying word to disambiguate.
+- Example conflict: both `performance` and `react-performance` trigger on "performance".
+  Resolution: `react-performance` uses `react performance` (compound), the generic
+  `performance` skill handles the unqualified keyword.
+
+#### Content Principles
+
+1. **Actionable, not advisory.** Say "Do X" not "Consider doing X" or "It's good practice to X".
+   - Bad: "You should consider adding error handling."
+   - Good: "Add try/catch around the database call. Log the error with context. Return 500."
+
+2. **Checklists, not essays.** Agents process structured lists faster than paragraphs.
+   - Bad: "When working with generics, it's important to think about constraints because
+     without them the type parameter is too broad and you lose type safety."
+   - Good: "- Always constrain generic parameters: `<T extends Base>` not bare `<T>`."
+
+3. **Complete code examples over descriptions.** Show the pattern, not just name it.
+   - Bad: "Use the builder pattern for complex objects."
+   - Good: [10-line code example of the builder pattern in the project's language]
+
+4. **Under 500 lines.** If a skill exceeds 500 lines, it is trying to cover too much.
+   Split into a parent skill + composed children.
+   - Example: `performance` (parent, 120 lines of general principles) +
+     `python-performance` (child, composes performance, 400 lines of Python specifics).
+
+5. **Decision trees for conditional logic.** When the right action depends on context,
+   provide explicit if/then:
+   ```
+   - IF the list has > 50 items → use virtualization
+   - IF the list has 10-50 items → use React.memo on list items
+   - IF the list has < 10 items → no optimization needed
+   ```
+
+6. **Anti-patterns section.** Include a list of common mistakes to flag. Agents benefit
+   from knowing what NOT to do as much as what to do.
+
+#### Quality Standards for Skill Content
+
+- Every code example must be syntactically valid (could be pasted and would compile).
+- All file paths in examples must use the project's actual structure conventions.
+- Version numbers in examples must not be outdated (review annually).
+- Commands must include expected output or success criteria.
+- If a skill references an external tool, include the install command.
+
+### After writing the skill
+
+1. **Validate frontmatter.** Confirm all required fields present, triggers are comma-separated,
+   version is valid SemVer.
+2. **Trigger evaluation test.** For each trigger, mentally construct a user prompt that
+   contains it and verify the skill SHOULD activate:
+   ```
+   Trigger: "discriminated union"
+   Test prompt: "I need to model payment states as a discriminated union"
+   Should activate? YES — this is exactly about TypeScript advanced types.
+   ```
+3. **Conflict scan.** Compare triggers against all existing skills:
+   ```bash
+   grep -r "^triggers:" .mindforge/skills/*/SKILL.md
+   ```
+   Flag any overlap and resolve per the rules above.
+4. **Register in MANIFEST.md** (if the project maintains one). Add the skill entry
+   with name, version, status, and trigger count.
+5. **Test via eval harness** (if available):
+   ```bash
+   mindforge eval-skill --skill=new-skill-name --prompts=20
+   ```
+   Verify activation precision > 90% and recall > 85%.
+
+## Skill review checklist (for reviewing others' skills)
+
+| Criterion | Pass/Fail |
+|---|---|
+| Frontmatter has all required fields | |
+| 12+ triggers, all compound (2+ words) | |
+| No single-word triggers | |
+| No trigger conflicts with existing skills | |
+| "When this skill activates" is specific (yes/no determinable) | |
+| Mandatory actions cover Before/During/After | |
+| Self-check section present with checkboxes | |
+| Content is actionable (imperatives, not suggestions) | |
+| Code examples are syntactically valid | |
+| Under 500 lines total | |
+| No placeholder language ("as appropriate", "etc.") | |
+
+## Skill lifecycle
+
+| Status | Meaning | Allowed changes |
+|---|---|---|
+| draft | Under construction | Anything |
+| beta | Functional, being tested | Content changes, trigger additions |
+| stable | Production | Content patches only. Trigger changes = major version bump |
+| deprecated | Being replaced | Only add migration notes pointing to successor |
+
+## Self-check before task completion
+
+Before marking a task done when this skill was active:
+
+- [ ] Frontmatter validates (all required fields, valid SemVer, 12+ triggers).
+- [ ] No trigger conflicts with existing skills (grep verified).
+- [ ] Body follows the standard structure (activation, Before/During/After, self-check).
+- [ ] Content is actionable (imperatives, checklists, code examples).
+- [ ] Under 500 lines total.
+- [ ] At least one code example included for the primary pattern.
+- [ ] Self-check section has 5+ checkboxes covering the skill's key requirements.
+- [ ] Trigger evaluation: 5+ test prompts mentally validated.
+- [ ] Registered in MANIFEST.md (if applicable).
+- [ ] No placeholder language in the body.

package/.mindforge/skills/zero-trust-architecture/SKILL.md

@@ -0,0 +1,166 @@
+---
+name: zero-trust-architecture
+version: 1.0.0
+min_mindforge_version: 10.1.1
+status: stable
+triggers: zero trust architecture, never trust always verify, micro-segmentation, identity-aware proxy, continuous verification, zero trust network, BeyondCorp, least privilege access, device posture, zero trust identity, mTLS everywhere, zero trust perimeter
+compose: auth-patterns
+---
+
+# Skill — Zero Trust Architecture
+
+## When this skill activates
+Any task involving network security architecture where traditional perimeter-based
+security is being replaced or augmented by identity-centric, continuous verification
+models. Includes mTLS implementation, micro-segmentation, identity-aware proxies,
+and BeyondCorp-style access patterns.
+
+## Mandatory actions when this skill is active
+
+### Before writing any code
+1. Inventory all communication flows (service-to-service, user-to-service, external).
+2. Define identity model (who/what can talk to whom under what conditions).
+3. Map trust boundaries — there are no trusted zones, only verified identities.
+4. Determine device posture requirements for user-facing access.
+
+### During implementation
+- Authenticate every request regardless of network origin.
+- Implement mTLS for all service-to-service communication.
+- Apply least privilege — grant minimum permissions needed, no more.
+- Never trust network location as a security signal.
+- Pass identity claims downstream (not just "authenticated: yes").
+- Re-verify identity on privilege escalation or sensitive operations.
+- Log all access decisions for audit.
+
+### After implementation
+- Verify default-deny is enforced (no open paths by accident).
+- Test that compromising one service doesn't grant lateral movement.
+- Confirm certificate rotation works automatically.
+- Validate device posture checks block non-compliant devices.
+- Audit that all flows are identity-verified.
+
+## Core Principles
+
+### The Three Pillars
+1. **Never trust, always verify** — Every request is treated as if from an open network.
+2. **Least privilege access** — Grant minimum permissions, scope tightly, time-bound when possible.
+3. **Assume breach** — Design as if attackers are already inside. Limit blast radius.
+
+### Trust Signals (Combined, Not Individual)
+- Identity (who is this? verified cryptographically).
+- Device (is this device healthy? patched? managed?).
+- Context (where, when, what resource, what action?).
+- Risk score (is this behavior anomalous?).
+
+## Identity-Aware Proxy
+
+### Pattern
+```
+User → Identity-Aware Proxy → Authenticate → Check Policy → Backend Service
+                                    ↓
+                            [Identity Provider]
+                            [Policy Engine]
+                            [Device Trust Store]
+```
+
+### Implementation
+- Proxy sits at the edge (or service mesh ingress).
+- Authenticates user via OIDC/SAML.
+- Checks policy engine for authorization.
+- Injects verified identity headers to backend.
+- Backend trusts proxy-injected headers (not user-supplied).
+
+### Tools
+- Google IAP, Cloudflare Access, Ory Oathkeeper, Pomerium.
+
+## Mutual TLS (mTLS)
+
+### Why
+- Encrypts traffic between services (confidentiality).
+- Cryptographically verifies both client and server identity (authentication).
+- Prevents unauthorized services from communicating.
+
+### Implementation
+- Use service mesh (Istio, Linkerd) for automatic mTLS.
+- Rotate certificates automatically (short-lived: 24h recommended).
+- Use SPIFFE/SPIRE for workload identity.
+- Never disable mTLS verification in production.
+
+### Certificate Management
+- Auto-issue via cert-manager or service mesh CA.
+- Short-lived certificates (hours, not years).
+- Automated rotation with zero downtime.
+- Certificate revocation for compromised services.
+
+## Micro-Segmentation
+
+### Approach
+1. Start with default-deny between all services.
+2. Declare allowed communication flows explicitly.
+3. Enforce at network layer (NetworkPolicy) AND application layer (authz).
+4. Segment by sensitivity level (PII services isolated from general services).
+
+### Example Policy
+```yaml
+# Only payment-service can talk to payment-db
+source: payment-service
+destination: payment-db
+port: 5432
+action: ALLOW
+
+# Everything else to payment-db
+source: *
+destination: payment-db
+action: DENY
+```
+
+## Device Posture
+
+### Checks Before Granting Access
+- OS version current (within N patches).
+- Disk encryption enabled.
+- Firewall active.
+- No known malware detected.
+- MDM-managed (for corporate devices).
+- Screen lock enabled.
+
+### Degraded Access
+- Non-compliant device → read-only access or blocked entirely.
+- Unknown device → step-up authentication required.
+- Jailbroken/rooted → zero access to sensitive resources.
+
+## Continuous Verification
+
+### Re-verify When
+- Session exceeds time threshold (e.g., every 1 hour).
+- User requests privilege escalation.
+- Anomalous behavior detected (impossible travel, unusual time).
+- Accessing higher-sensitivity resource than current level.
+- Device posture changes mid-session.
+
+### Risk-Based Response
+- Low risk → continue session.
+- Medium risk → step-up auth (MFA prompt).
+- High risk → terminate session, require full re-authentication.
+
+## BeyondCorp Model
+
+### Key Differences from VPN
+| Traditional VPN | BeyondCorp (Zero Trust) |
+|----------------|------------------------|
+| VPN = trusted zone | No trusted zone exists |
+| Once in, full access | Every request verified |
+| Network location = trust | Identity + device + context = trust |
+| Perimeter defense | Defense in depth everywhere |
+| Hard outside, soft inside | Uniformly hardened |
+
+## Self-check
+- [ ] All service-to-service communication uses mTLS.
+- [ ] Default-deny network policy in place.
+- [ ] Identity verified on every request (not just at edge).
+- [ ] Least privilege enforced (no over-permissioned service accounts).
+- [ ] Device posture checked for user access.
+- [ ] Continuous verification triggers defined.
+- [ ] Certificate rotation is automatic and tested.
+- [ ] Lateral movement prevented (compromise one service != access to others).
+- [ ] All access decisions logged for audit.

package/CHANGELOG.md

@@ -1,5 +1,200 @@
 # Changelog
 
+## [10.7.0] - 2026-05-27 — "Platform Sovereign"
+
+### Added (v10.7.0)
+
+- **10 new core skills** — internal-developer-platform, self-serve-infrastructure, platform-reliability, developer-productivity-metrics, api-marketplace, build-system-optimization, secrets-platform, environment-management, platform-observability, migration-platform.
+- **6 new commands** — `/mindforge:platform`, `/mindforge:build-opt`, `/mindforge:secrets-mgmt`, `/mindforge:environments`, `/mindforge:observability-platform`, `/mindforge:migration-mgmt`.
+- **6 new personas** — platform-lead, build-engineer, environment-engineer, productivity-analyst, secrets-engineer, migration-architect.
+- **1 new swarm template** — PlatformSwarmV2 (HITL platform engineering + migration).
+- **200 core skills milestone** — Full coverage across 12 domains.
+- **Swarm templates v15.0.0** — 49 total templates.
+
+---
+
+## [10.6.0] - 2026-05-27 — "Data Alchemy"
+
+### Added (v10.6.0)
+
+- **10 new core skills** — causal-inference, feature-engineering, ml-monitoring, data-governance, stream-processing, data-lakehouse, experiment-platform, data-mesh, real-time-analytics, data-privacy-engineering.
+- **6 new commands** — `/mindforge:causal`, `/mindforge:lakehouse`, `/mindforge:data-mesh`, `/mindforge:stream`, `/mindforge:privacy-eng`, `/mindforge:realtime-analytics`.
+- **6 new personas** — causal-scientist, data-mesh-architect, stream-engineer, lakehouse-architect, privacy-engineer, analytics-engineer.
+- **1 new swarm template** — DataAlchemySwarm (HITL data architecture + privacy).
+
+---
+
+## [10.5.0] - 2026-05-27 — "AI Frontier"
+
+### Added (v10.5.0)
+
+- **10 new core skills** — multimodal-ai, ai-safety-alignment, synthetic-data-generation, model-evaluation, embedding-systems, llm-orchestration, knowledge-graphs, ml-feature-store, ai-cost-management, autonomous-agents.
+- **8 new commands** — `/mindforge:multimodal`, `/mindforge:ai-safety`, `/mindforge:embeddings`, `/mindforge:llm-route`, `/mindforge:knowledge-graph`, `/mindforge:feature-store`, `/mindforge:ai-cost`, `/mindforge:agent-design`.
+- **8 new personas** — multimodal-engineer, ai-safety-engineer, embedding-architect, llm-orchestrator, knowledge-engineer, feature-store-engineer, ai-economist, agent-architect.
+- **1 new swarm template** — AIFrontierSwarm (HITL AI system architecture + safety).
+
+---
+
+## [10.4.0] - 2026-05-27 — "Cross-Platform"
+
+### Added (v10.4.0)
+
+- **10 new core skills** — react-native-patterns, flutter-architecture, offline-first-design, progressive-web-app, mobile-performance, cross-platform-testing, app-store-deployment, mobile-security, responsive-native, push-notification-architecture.
+- **6 new commands** — `/mindforge:mobile`, `/mindforge:react-native`, `/mindforge:flutter`, `/mindforge:offline`, `/mindforge:pwa`, `/mindforge:push-notify`.
+- **6 new personas** — mobile-architect, react-native-engineer, flutter-engineer, offline-specialist, mobile-security-engineer, pwa-architect.
+- **1 new swarm template** — MobileSwarm (HITL cross-platform architecture).
+
+---
+
+## [10.3.0] - 2026-05-27 — "Leader's Edge"
+
+### Added (v10.3.0)
+
+- **10 new core skills** — technical-leadership, mentoring-patterns, stakeholder-communication, conflict-resolution, incident-communication, hiring-engineering, delegation-patterns, meeting-architecture, performance-reviews, change-management.
+- **6 new commands** — `/mindforge:lead`, `/mindforge:communicate`, `/mindforge:hire`, `/mindforge:delegate`, `/mindforge:meeting-design`, `/mindforge:change`.
+- **6 new personas** — tech-lead-coach, communication-architect, hiring-strategist, change-agent, meeting-designer, mentorship-lead.
+- **1 new swarm template** — LeadershipSwarm (HITL engineering leadership).
+
+---
+
+## [10.2.0] - 2026-05-27 — "Industry Forge"
+
+### Added (v10.2.0)
+
+- **10 new core skills** — healthcare-systems, fintech-patterns, ecommerce-architecture, gaming-backend, edtech-platform, saas-multi-tenant, media-streaming, iot-platform, marketplace-trust, logistics-optimization.
+- **8 new commands** — `/mindforge:healthcare`, `/mindforge:fintech`, `/mindforge:ecommerce`, `/mindforge:gaming`, `/mindforge:edtech`, `/mindforge:iot`, `/mindforge:marketplace`, `/mindforge:logistics`.
+- **8 new personas** — healthcare-engineer, fintech-architect, ecommerce-engineer, gaming-engineer, edtech-architect, iot-architect, marketplace-engineer, logistics-architect.
+- **1 new swarm template** — IndustryVerticalSwarm (HITL domain-specific architecture).
+- **150 core skills milestone** — Industry vertical coverage added.
+
+---
+
+## [10.1.1] - 2026-05-26 — "Scale & Edge"
+
+### Added (v10.1.1)
+
+- **10 new core skills** — edge-computing, serverless-patterns, container-security, zero-trust-architecture, ai-agent-deployment, distributed-consensus, data-pipeline-design, dns-architecture, cdn-optimization, database-sharding-advanced.
+- **6 new commands** — `/mindforge:edge`, `/mindforge:serverless`, `/mindforge:zero-trust`, `/mindforge:agent-deploy`, `/mindforge:data-pipeline`, `/mindforge:cdn`.
+- **6 new personas** — edge-engineer, zero-trust-engineer, agent-ops-engineer, consensus-engineer, data-pipeline-architect, cdn-architect.
+- **2 new swarm templates** — EdgeScaleSwarm (HITL edge + CDN), DistributedSwarm (HITL consensus + pipelines).
+- **140 core skills milestone** — Comprehensive coverage of emerging technology and massive-scale patterns.
+- **Swarm templates v14.0.0** — Bump from v13.0.0 with 2 new templates (total: 43 swarm templates).
+
+---
+
+## [10.1.0] - 2026-05-26 — "Strategic Intelligence"
+
+### Added (v10.1.0)
+
+- **20 new core skills** — build-vs-buy, technology-radar, architecture-tradeoff-analysis, technical-interview-design, post-incident-learning, team-topology-design, sprint-retrospective-facilitation, knowledge-sharing-systems, estimation-techniques, on-call-design, experiment-design, analytics-instrumentation, notification-system-design, payment-integration, email-deliverability, agent-memory-design, agent-evaluation-framework, multi-turn-conversation-design, agent-tool-selection, human-in-the-loop-design.
+- **10 new commands** — `/mindforge:build-vs-buy`, `/mindforge:tech-radar`, `/mindforge:team-topology`, `/mindforge:retro`, `/mindforge:experiment`, `/mindforge:analytics`, `/mindforge:payments`, `/mindforge:agent-memory`, `/mindforge:agent-eval`, `/mindforge:hitl`.
+- **8 new personas** — decision-architect, team-coach, knowledge-curator, experiment-designer, payments-engineer, agent-memory-designer, agent-evaluator, hitl-architect.
+- **3 new swarm templates** — DecisionSwarm (HITL decision quality), TeamDesignSwarm (HITL team topology), AgentMetaSwarm (autonomous self-improvement).
+- **130 core skills milestone** — Category expansion into decision science, team engineering, product patterns, and agent meta-intelligence.
+- **Minor version bump (10.1.0)** — Represents category expansion beyond pure engineering into strategy and meta-intelligence.
+- **Swarm templates v13.0.0** — Bump from v12.0.0 with 3 new templates (total: 41 swarm templates).
+
+---
+
+## [10.0.9] - 2026-05-26 — "Full Spectrum"
+
+### Added (v10.0.9)
+
+- **20 new core skills** — streaming-architecture, queue-design, real-time-sync, cost-estimation, technical-debt-management, capacity-planning, graceful-degradation, idempotency-patterns, rate-limiting-design, code-generation-patterns, dependency-management, git-workflow-design, i18n-architecture, a11y-testing, multi-tenancy-patterns, audit-logging, database-performance, bundle-optimization, graphql-patterns, pagination-patterns.
+- **10 new commands** — `/mindforge:stream`, `/mindforge:queue`, `/mindforge:finops`, `/mindforge:tech-debt`, `/mindforge:degrade`, `/mindforge:idempotent`, `/mindforge:rate-limit`, `/mindforge:i18n`, `/mindforge:multi-tenant`, `/mindforge:graphql`.
+- **8 new personas** — streaming-engineer, finops-analyst, debt-manager, resilience-engineer, codegen-specialist, i18n-architect, multi-tenancy-architect, graphql-designer.
+- **3 new swarm templates** — StreamingSwarm (HITL real-time), ResilienceSwarm (autonomous failure engineering), GovernanceSwarm (HITL data governance).
+- **110 core skills milestone** — Comprehensive coverage across all major software engineering domains achieved.
+- **Swarm templates v12.0.0** — Bump from v11.0.0 with 3 new templates (total: 38 swarm templates).
+
+---
+
+## [10.0.8] - 2026-05-26 — "Deep Patterns"
+
+### Added (v10.0.8)
+
+- **20 new core skills** — contract-testing, load-testing, mutation-testing, visual-regression-testing, monorepo-management, cli-design, developer-onboarding, error-handling-architecture, caching-strategies, migration-strategies, connection-pooling, event-driven-architecture, api-gateway-patterns, websocket-patterns, feature-flag-management, secrets-rotation, compliance-as-code, rag-architecture, fine-tuning-workflow, llm-cost-optimization.
+- **10 new commands** — `/mindforge:contract-test`, `/mindforge:load-test`, `/mindforge:monorepo`, `/mindforge:cli`, `/mindforge:cache`, `/mindforge:events`, `/mindforge:secrets`, `/mindforge:rag`, `/mindforge:feature-flags`, `/mindforge:compliance`.
+- **8 new personas** — contract-tester, dx-engineer, cache-architect, event-architect, compliance-engineer, ml-ops-engineer, platform-engineer, api-gateway-designer.
+- **3 new swarm templates** — TestingDeepSwarm (autonomous deep testing), PlatformSwarm (HITL platform engineering), MLOpsSwarm (HITL ML operations).
+- **90 core skills milestone** — Production-depth coverage for testing, caching, events, secrets, compliance, RAG, and cost optimization.
+- **Swarm templates v11.0.0** — Bump from v10.0.0 with 3 new templates (total: 35 swarm templates).
+
+---
+
+## [10.0.7] - 2026-05-26 — "Meta Engineer"
+
+### Added (v10.0.7)
+
+- **20 new core skills** — prompt-engineering, context-engineering, agent-orchestration-patterns, tool-design, guardrails-and-safety, observability-stack, ci-cd-pipeline, infrastructure-as-code, incident-management, chaos-engineering, data-modeling, api-versioning, search-implementation, design-system, state-management, responsive-patterns, auth-patterns, supply-chain-security, technical-writing, code-review-methodology.
+- **10 new commands** — `/mindforge:prompt`, `/mindforge:context-budget`, `/mindforge:orchestrate`, `/mindforge:observability`, `/mindforge:pipeline`, `/mindforge:data-model`, `/mindforge:design-tokens`, `/mindforge:auth-flow`, `/mindforge:write-rfc`, `/mindforge:review-guide`.
+- **8 new personas** — prompt-architect, agent-orchestrator, sre-lead, pipeline-engineer, data-architect, design-system-lead, auth-engineer, technical-writer-lead.
+- **3 new swarm templates** — PromptEngineeringSwarm (HITL AI engineering), SRESwarm (HITL reliability), FrontendSwarm (autonomous design system).
+- **70 core skills milestone** — Framework now covers AI engineering, DevOps, reliability, data, frontend, advanced security, and technical communication.
+- **Swarm templates v10.0.0** — Bump from v9.0.0 with 3 new templates (total: 32 swarm templates).
+
+---
+
+## [10.0.6] - 2026-05-26 — "Complete Arsenal"
+
+### Added (v10.0.6)
+
+- **17 new core skills** — microservices-patterns, cqrs-event-sourcing, system-design, business-analyst, product-manager, market-researcher, typescript-advanced, python-performance, react-performance, k8s-deployment, writing-plans, writing-skills, using-git-worktrees, code-tour, autonomous-agent-harness, mcp-server-patterns, proofreader.
+- **10 new commands** — `/mindforge:microservices`, `/mindforge:system-design`, `/mindforge:brd`, `/mindforge:product-spec`, `/mindforge:market-research`, `/mindforge:code-tour`, `/mindforge:mcp-server`, `/mindforge:proofread`, `/mindforge:worktrees`, `/mindforge:plan-write`.
+- **8 new personas** — business-analyst, product-owner, market-analyst, mcp-designer, proofreader, system-designer, worktree-manager, code-narrator.
+- **3 new swarm templates** — ArchDesignSwarm (HITL system design), ProductSwarm (HITL product strategy), DocumentationSwarm (autonomous content quality).
+- **Swarm templates v9.0.0** — Bump from v8.0.0 with 3 new templates (total: 29 swarm templates).
+- **50 core skills milestone** — Framework now covers architecture, business, languages, workflow, infrastructure, and documentation domains.
+
+---
+
+## [10.0.5] - 2026-05-26 — "Forge Master"
+
+### Added (v10.0.5)
+
+- **5 new core skills** — skill-creator-meta, deployment-workflow, dmux-workflows, vibe-security, instinct-clustering.
+- **5 new commands** — `/mindforge:create-skill`, `/mindforge:deploy`, `/mindforge:dmux`, `/mindforge:vibe-check`, `/mindforge:cluster-instincts`.
+- **5 new personas** — skill-smith, deployment-captain, dmux-orchestrator, vibe-checker, saga-orchestrator.
+- **2 new swarm templates** — DeploymentSwarm (HITL staged rollout), ForgeSwarm (autonomous skill creation).
+- **De-slop gate** — Phase 6.5 in verification-loop: informational de-slop scan before shipping (non-blocking).
+- **Cross-model eval spec** — `.mindforge/engine/cross-model-eval.md` for routing same task to 2 models and comparing outputs.
+- **Swarm templates v8.0.0** — Bump from v7.0.0 with 2 new templates (total: 26 swarm templates).
+
+---
+
+## [10.0.4] - 2026-05-26 — "Santa's Eval"
+
+### Added (v10.0.4)
+
+- **8 new core skills** — santa-method, eval-harness, quality-audit, testing-anti-patterns, defense-in-depth, codebase-onboarding, rfc-pipeline, de-sloppify.
+- **6 new commands** — `/mindforge:santa`, `/mindforge:eval`, `/mindforge:quality-audit`, `/mindforge:rfc`, `/mindforge:onboard`, `/mindforge:de-slop`.
+- **6 new personas** — eval-judge, rfc-architect, anti-pattern-hunter, onboarding-navigator, de-sloppifier, quality-scorer.
+- **3 new swarm templates** — EvalSwarm (autonomous eval gate), OnboardingSwarm (autonomous codebase discovery), RFCSwarm (HITL spec decomposition).
+- **Proactive Skill Suggestion Engine** — Signal-based skill detection (file/error/task patterns) with confidence threshold (0.7), cooldown tracking, and debounce logic.
+- **Eval storage** — `.mindforge/evals/` directory for persisting eval configs, rubrics, and results.
+- **Swarm templates v7.0.0** — Bump from v6.0.0 with 3 new templates (total: 24 swarm templates).
+
+---
+
+## [10.0.3] - 2026-05-25 — "Council Awakens"
+
+### Added (v10.0.3)
+
+- **10 new core skills** — agent-loops, multi-llm-consult, continuous-learning, council, verification-loop, threat-modeling, autonomous-loops, agent-introspection-debugging, cost-aware-routing, doc-health-audit.
+- **8 new commands** — `/mindforge:council`, `/mindforge:consult`, `/mindforge:verify-loop`, `/mindforge:introspect`, `/mindforge:cost-report`, `/mindforge:threat-model`, `/mindforge:learn-instinct`, `/mindforge:evolve-skills`.
+- **9 new personas** — cost-optimizer, threat-modeler, council-architect, council-skeptic, council-pragmatist, council-critic, instinct-curator, doc-auditor, multi-model-bridge.
+- **3 new swarm templates** — CouncilSwarm (HITL decision gate), VerificationSwarm (autonomous quality gates), LearningSwarm (instinct management).
+- **Skill Composition System** — Skills can now declare dependencies on other skills via `compose:` frontmatter field. Composed skills are injected as summaries (max 2-level depth, cycle detection).
+- **Instinct Engine** — Auto-capture learned behaviors with confidence scoring. Instincts auto-promote to skills at 0.85 confidence after 5+ successful applications. Project-scoped, max 100 per project.
+- **Cost Tracking Module** — Token budgeting, 5-tier model routing (Haiku/Sonnet/Opus/Gemini/GPT-4o), spend analytics via token-ledger.jsonl.
+- **Council Framework** — 4-voice decision harness (Architect, Skeptic, Pragmatist, Critic) with weighted consensus scoring, dissent documentation, and 5 pre-built templates.
+- **Cross-Iteration Bridge** — SHARED_TASK_NOTES.md for semantic context persistence across autonomous mode iterations (complements HANDOFF.json).
+- **Swarm templates v6.0.0** — Bump from v5.0.0 with 3 new templates (total: 21 swarm templates).
+- **claude-opus-4-7** added to market_registry in config.json.
+- **Loader composition step** — New Step 4.1 in skill loader for resolving `compose:` dependencies.
+
+---
+
 ## [10.0.2] - 2026-05-24 — "Persona Expansion"
 
 ### Added (v10.0.2)

package/MINDFORGE.md

@@ -1,12 +1,12 @@
-# MINDFORGE.md — Parameter Registry (v10.0.2)
+# MINDFORGE.md — Parameter Registry (v10.7.0)
 
 ## 1. IDENTITY & VERSIONING
 
 [NAME]    = MindForge
-[VERSION] = 10.0.2-BEDROCK
+[VERSION] = 10.7.0-SOVEREIGN
 [STABLE]  = true
-[MODE]    = \"Bedrock Fortified\"
-[REQUIRED_CORE_VERSION] = 10.0.2
+[MODE]    = "Platform Sovereign"
+[REQUIRED_CORE_VERSION] = 10.7.0
 [SOVEREIGN_IDENTITY] = true
 [SRE_LAYER_ENABLED]  = true
 

package/README.md

@@ -4,9 +4,9 @@
 
 ---
 
-## v10.0.1 — Bedrock Fortified (Production-Grade Architecture)
+## v10.0.3 — Council Awakens
 
-MindForge v9.0.0 "Bedrock Meridian" grounds previously-stub implementations into real, auditable execution. This release introduces grounded wave dispatch via HANDOFF.json, consolidates all memory stores into a single SQLite database, modernizes the model topology to the Claude 4.x family, and adds a 27-assertion integration test chain — completing the transition from framework scaffolding to production-verified infrastructure (Pillars XXIV-XXVIII).
+MindForge v10.0.3 "Council Awakens" introduces the Council decision framework, Instinct Engine, Cost-Aware Routing, 6-phase Verification Loop, and Multi-LLM Consult. This release adds 10 skills (20 core total), 8 commands (71 total), 9 personas (117 total), 3 swarm templates (21 total), and 5 engine subsystems — expanding MindForge's autonomous governance and multi-agent reasoning capabilities.
 
 
 ## Installation & Setup