marccampbell

Plan: Remove Dagger from Vandoor

Context

Dagger is used in Vandoor for CI/CD pipelines and local dev automation. The goal is to fully remove Dagger and replace its functionality with native GitHub Actions + standard tooling.

Current Dagger Usage

1. Code/Module (dagger/ directory)

marccampbell

name: Publish

on:
  push:
    branches:
      - main
    paths:
      - '.elasticclaw/**'
  workflow_dispatch:

marccampbell

elasticclaw-config

ElasticClaw configuration for Faster Next — templates and factories for automated claw workflows.

What's in here

.elasticclaw/
  templates/
 / # One directory per claw template

marccampbell

🚨 Axios Supply Chain Vulnerability — Replicated Repo Audit

Date: 2026-03-31 Threat: axios@1.14.1 pulls in plain-crypto-js@4.2.1 — confirmed malware (supply chain attack) Action: DO NOT upgrade axios. Pin versions. Audit lockfiles.

Affected Repos (replicatedhq + replicatedcom)

Repo	File	Section	Axios Version

marccampbell

# Autoprobe Bot Instructions

You are an autoprobe research bot. Your goal is to make autoprobe actually work — to reduce XHR requests on a test page from 11 to fewer.

## Your Environment

- **Autoprobe source:** `~/autoprobe` (you can modify this)
- **Test repo:** `~/vandoor` (vendor-web React app)
- **Test page:** `channels` (makes 11 XHR requests, goal is fewer)
- **Discard vandoor changes:** Always `git checkout .` in vandoor after each run — we're improving autoprobe, not vandoor

marccampbell

# Autoprobe Auto-Research Loop

Automated feedback loop for improving autoprobe:
1. Push fix to autoprobe repo
2. GitHub webhook triggers your Mac
3. Mac rebuilds autoprobe, runs it on test repo
4. Results posted to Telegram
5. Analyze, push next fix, repeat

## Prerequisites

marccampbell

# autoprobe CLI Structure

## Command Tree

```
autoprobe
├── init                    # Create .autoprobe.yaml, set up project
├── run <name>              # Analyze → fix → verify → repeat
│   ├── --max-iterations    # Stop after N cycles (1 = single-shot analysis)
│   └── --dry-run           # Show proposed changes, don't apply

marccampbell

2026-03-06

Support Bundle AI — Major Progress

What Happened

• Rebased feat/daytona-provisioning onto latest main (resolved otel version conflicts)
• Added "Analyze with AI" menu item to SupportBundleRow (gated by ai_support_bundle_analysis feature flag)
• Wired button to POST /v3/supportbundle/:bundleId/agent/start
• Renamed tables: support_bundle_analysis → ai_support_bundle_analysis (+ bundle join table)
• Moved SchemaHero schemas to correct path: migrations/kustomize/schemas/mysql/

marccampbell

Helm Chart Reference Docs — Design

Overview

When a vendor promotes a release, we generate structured Helm chart reference documentation and serve it through Enterprise Portal. Vendors declare which charts they want documented in toc.yaml. The worker extracts chart content from the release, parses values.yaml deterministically, enriches with Claude, and stores structured JSON. The EP frontend renders it using the same component pattern as Terraform module references.

toc.yaml Declaration

- title: Reference

marccampbell

Terraform Module URI-Based Ingest — Design

Summary

Terraform modules are referenced as source URIs directly in toc.yaml. The URI is the single source of truth for where a module lives. During content sync, Vandoor resolves the URI, fetches the module using the GitHub App, and stores it with a commit SHA for change detection.

---

toc.yaml