agent-nuvira 1.88.2 → 1.88.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.agents/skills/backup-strategy/SKILL.md +4 -4
- package/.agents/skills/cdn-setup/SKILL.md +4 -4
- package/.agents/skills/cloud-deploy/SKILL.md +4 -4
- package/.agents/skills/cron-job/SKILL.md +4 -4
- package/.agents/skills/data-processing/SKILL.md +4 -4
- package/.agents/skills/dns-setup/SKILL.md +4 -4
- package/.agents/skills/github-actions/SKILL.md +4 -4
- package/.agents/skills/kafka-queue/SKILL.md +4 -4
- package/.agents/skills/kubernetes/SKILL.md +4 -4
- package/.agents/skills/load-balancer/SKILL.md +4 -4
- package/.agents/skills/log-rotation/SKILL.md +4 -4
- package/.agents/skills/ml-model/SKILL.md +4 -4
- package/.agents/skills/nginx-config/SKILL.md +4 -4
- package/.agents/skills/prometheus/SKILL.md +4 -4
- package/.agents/skills/redis-cache/SKILL.md +4 -4
- package/.agents/skills/secrets-manager/SKILL.md +4 -4
- package/.agents/skills/ssl-cert/SKILL.md +4 -4
- package/.agents/skills/structured-logging/SKILL.md +4 -4
- package/.agents/skills/terraform/SKILL.md +4 -4
- package/.agents/skills/web-scraping/SKILL.md +4 -4
- package/dist/agent-sdk/src/register.js +1 -1
- package/dist/agents/agents/branch-automation-agent.js +1 -1
- package/dist/agents/agents/branch-automation-hooks.js +1 -1
- package/dist/agents/checkpoint-store.js +1 -1
- package/dist/agents/nvda-addon.js +1 -1
- package/dist/agents/phase-engine.js +1 -1
- package/dist/cli/audit.js +1 -1
- package/dist/cli/chat.js +1 -1
- package/dist/cli/execute.js +1 -1
- package/dist/cli/memory.js +1 -1
- package/dist/commands/semantic-intent.js +1 -1
- package/dist/context/cache.js +1 -1
- package/dist/context/history.js +1 -1
- package/dist/context/session-recall.js +1 -1
- package/dist/enterprise/audit-chain.js +1 -1
- package/dist/enterprise/log.js +1 -1
- package/dist/enterprise/metrics.js +1 -1
- package/dist/enterprise/rbac.js +1 -1
- package/dist/enterprise/secrets.js +1 -1
- package/dist/enterprise/vault-audit.js +1 -1
- package/dist/gateway/adapters.js +1 -1
- package/dist/gateway/platform-config.js +1 -1
- package/dist/gateway/registry.js +1 -1
- package/dist/gateway/whatsapp/session.js +1 -1
- package/dist/learning/agent-stats.js +1 -1
- package/dist/learning/benchmark.js +1 -1
- package/dist/learning/cost-tracker.js +1 -1
- package/dist/learning/eval-framework.js +1 -1
- package/dist/learning/failure-lessons.js +1 -1
- package/dist/learning/feedback.js +1 -1
- package/dist/learning/key-hygiene.js +1 -1
- package/dist/learning/ml-router.js +1 -1
- package/dist/learning/model-registry.js +1 -1
- package/dist/learning/pattern-extractor.js +1 -1
- package/dist/learning/provider-fallback.js +1 -1
- package/dist/learning/quota-ledger.js +1 -1
- package/dist/learning/reasoning-cache.js +1 -1
- package/dist/learning/reasoning-trace.js +1 -1
- package/dist/learning/retrieval.js +1 -1
- package/dist/learning/router-bandit.js +1 -1
- package/dist/learning/router-promotion.js +1 -1
- package/dist/learning/routing-history.js +1 -1
- package/dist/learning/skill-bundles.js +1 -1
- package/dist/learning/skill-drafts.js +1 -1
- package/dist/learning/skills-hub.js +1 -1
- package/dist/learning/skills-registry.js +1 -1
- package/dist/learning/tier0-router.js +1 -1
- package/dist/mcp/mcp-oauth.js +1 -1
- package/dist/mcp/mcp-schema-cache.js +1 -1
- package/dist/memory/faiss-backend.js +1 -1
- package/dist/memory/sqlite-store.js +1 -1
- package/dist/memory/trajectory-store.js +1 -1
- package/dist/memory/vector-store.js +1 -1
- package/dist/skills/bundled-skills.js +5 -5
- package/dist/skills/secret-capture.js +1 -1
- package/dist/sync/validate.js +1 -1
- package/dist/sync/validate.js.map +1 -1
- package/dist/tools/artifact-store.js +1 -1
- package/dist/tools/browser-camofox.js +1 -1
- package/dist/tools/checkpoint-manager.js +1 -1
- package/dist/tools/clone-repo.js +1 -1
- package/dist/tools/credential-env-tools.js +1 -1
- package/dist/tools/credential-files.js +1 -1
- package/dist/tools/cronjob-tools.js +1 -1
- package/dist/tools/delegation-live-log.js +1 -1
- package/dist/tools/delegation-state.js +1 -1
- package/dist/tools/delegation-system.js +1 -1
- package/dist/tools/infra-tools.js +1 -1
- package/dist/tools/kanban-cron-tools.js +1 -1
- package/dist/tools/kanban-tools.js +1 -1
- package/dist/tools/memory-tool.js +1 -1
- package/dist/tools/memory-tools.js +1 -1
- package/dist/tools/modality/modality-catalog.js +1 -1
- package/dist/tools/modality/shared.js +1 -1
- package/dist/tools/modality/vision.js +1 -1
- package/dist/tools/modality/voice.js +1 -1
- package/dist/tools/project-tools.js +1 -1
- package/dist/tools/registry.js +1 -1
- package/dist/tools/session-tools.js +1 -1
- package/dist/tools/skill-metadata.js +1 -1
- package/dist/tools/skills-hub.js +1 -1
- package/dist/tools/skills-sync-client.js +1 -1
- package/dist/tools/subagent-spawner.js +1 -1
- package/dist/tools/terminal-tool.js +1 -1
- package/dist/tools/todo-tool.js +1 -1
- package/dist/tools/web-research.js +1 -1
- package/dist/utils/env.js +1 -1
- package/dist/web-dashboard/hub-data.js +1 -1
- package/dist/web-dashboard/server.js +1 -1
- package/dist/web-dashboard/src/admin-auth.js +1 -1
- package/package.json +2 -2
|
@@ -22,7 +22,7 @@ backup disaster recovery retention snapshot restore data protection RPO RTO
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze backup requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check data to backup
|
|
@@ -44,7 +44,7 @@ df -h /var/backups
|
|
|
44
44
|
- What retention? (7 days, 30 days, 1 year)
|
|
45
45
|
- What compliance? (GDPR, HIPAA, SOC2)
|
|
46
46
|
|
|
47
|
-
### Step 2: [
|
|
47
|
+
### Step 2: [analyst] — Implement backup solution
|
|
48
48
|
|
|
49
49
|
**Database backup script:**
|
|
50
50
|
```bash
|
|
@@ -100,7 +100,7 @@ restic -r s3:s3.amazonaws.com/my-backups restore latest --target /restore
|
|
|
100
100
|
0 4 * * 0 root /usr/local/bin/backup-verify.sh >> /var/log/backup.log 2>&1
|
|
101
101
|
```
|
|
102
102
|
|
|
103
|
-
### Step 3: [
|
|
103
|
+
### Step 3: [analyst] — Deploy and test
|
|
104
104
|
|
|
105
105
|
```bash
|
|
106
106
|
# Run backup manually
|
|
@@ -117,7 +117,7 @@ psql mydb < /var/backups/db/mydb_20240101_020000.sql
|
|
|
117
117
|
aws s3 ls s3://my-backups/database/ | tail -5
|
|
118
118
|
```
|
|
119
119
|
|
|
120
|
-
### Step 4: [
|
|
120
|
+
### Step 4: [analyst] — Verify backup strategy
|
|
121
121
|
|
|
122
122
|
```bash
|
|
123
123
|
# Check backup logs
|
|
@@ -22,7 +22,7 @@ CDN content delivery network static assets cache edge cloudflare cloudfront
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze content and traffic patterns
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check current asset sizes
|
|
@@ -41,7 +41,7 @@ dig CNAME example.com +short
|
|
|
41
41
|
- What cache behavior? (long TTL for static, short for HTML)
|
|
42
42
|
- What security needs? (DDoS protection, WAF, rate limiting)
|
|
43
43
|
|
|
44
|
-
### Step 2: [
|
|
44
|
+
### Step 2: [analyst] — Configure CDN
|
|
45
45
|
|
|
46
46
|
**Cloudflare configuration:**
|
|
47
47
|
```javascript
|
|
@@ -140,7 +140,7 @@ ttl = 3600 # 1 hour
|
|
|
140
140
|
}
|
|
141
141
|
```
|
|
142
142
|
|
|
143
|
-
### Step 3: [
|
|
143
|
+
### Step 3: [analyst] — Deploy CDN configuration
|
|
144
144
|
|
|
145
145
|
```bash
|
|
146
146
|
# Cloudflare: deploy worker
|
|
@@ -159,7 +159,7 @@ curl -X POST "https://api.cloudflare.com/client/v4/zones/ZONE_ID/purge_cache" \
|
|
|
159
159
|
--data '{"purge_everything":true}'
|
|
160
160
|
```
|
|
161
161
|
|
|
162
|
-
### Step 4: [
|
|
162
|
+
### Step 4: [analyst] — Verify CDN performance
|
|
163
163
|
|
|
164
164
|
```bash
|
|
165
165
|
# Check cache hit ratio
|
|
@@ -22,7 +22,7 @@ cloud deploy AWS GCP Azure serverless lambda function app engine kubernetes
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze deployment requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check cloud CLI
|
|
@@ -45,7 +45,7 @@ gcloud run services list 2>/dev/null | head -5
|
|
|
45
45
|
- What environment variables? (secrets, config)
|
|
46
46
|
- What domain/SSL? (custom domain, certificates)
|
|
47
47
|
|
|
48
|
-
### Step 2: [
|
|
48
|
+
### Step 2: [analyst] — Create deployment configuration
|
|
49
49
|
|
|
50
50
|
**AWS ECS deployment:**
|
|
51
51
|
```yaml
|
|
@@ -128,7 +128,7 @@ images:
|
|
|
128
128
|
- 'gcr.io/$PROJECT_ID/myapp:$COMMIT_SHA'
|
|
129
129
|
```
|
|
130
130
|
|
|
131
|
-
### Step 3: [
|
|
131
|
+
### Step 3: [analyst] — Deploy application
|
|
132
132
|
|
|
133
133
|
```bash
|
|
134
134
|
# Build and push Docker image
|
|
@@ -154,7 +154,7 @@ aws ecs describe-services \
|
|
|
154
154
|
--query 'services[0].{status:status,desired:desiredCount,running:runningCount}'
|
|
155
155
|
```
|
|
156
156
|
|
|
157
|
-
### Step 4: [
|
|
157
|
+
### Step 4: [analyst] — Verify deployment
|
|
158
158
|
|
|
159
159
|
```bash
|
|
160
160
|
# Health check
|
|
@@ -22,7 +22,7 @@ cron schedule task automate periodic cleanup backup report
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze scheduling needs
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check existing crontab
|
|
@@ -41,7 +41,7 @@ systemctl status cron 2>/dev/null || systemctl status crond 2>/dev/null
|
|
|
41
41
|
- What dependencies? (database, API, filesystem)
|
|
42
42
|
- What notifications? (email, Slack, PagerDuty)
|
|
43
43
|
|
|
44
|
-
### Step 2: [
|
|
44
|
+
### Step 2: [analyst] — Create cron jobs
|
|
45
45
|
|
|
46
46
|
**System crontab:**
|
|
47
47
|
```bash
|
|
@@ -114,7 +114,7 @@ services:
|
|
|
114
114
|
crond -f -l 8"
|
|
115
115
|
```
|
|
116
116
|
|
|
117
|
-
### Step 3: [
|
|
117
|
+
### Step 3: [analyst] — Deploy and test
|
|
118
118
|
|
|
119
119
|
```bash
|
|
120
120
|
# Deploy crontab
|
|
@@ -132,7 +132,7 @@ grep CRON /var/log/syslog | tail -10
|
|
|
132
132
|
systemctl status cron
|
|
133
133
|
```
|
|
134
134
|
|
|
135
|
-
### Step 4: [
|
|
135
|
+
### Step 4: [analyst] — Verify tasks execute
|
|
136
136
|
|
|
137
137
|
```bash
|
|
138
138
|
# Check cron execution
|
|
@@ -22,7 +22,7 @@ data processing pandas numpy polars CSV JSON transform clean aggregate ETL
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze data requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check data files
|
|
@@ -43,7 +43,7 @@ du -sh data/*
|
|
|
43
43
|
- What output format? (CSV, JSON, database)
|
|
44
44
|
- What data quality? (missing values, duplicates, outliers)
|
|
45
45
|
|
|
46
|
-
### Step 2: [
|
|
46
|
+
### Step 2: [analyst] — Create processing pipeline
|
|
47
47
|
|
|
48
48
|
```python
|
|
49
49
|
# src/processing/pipeline.py
|
|
@@ -159,7 +159,7 @@ def run_pipeline(input_path: str, output_path: str):
|
|
|
159
159
|
return df
|
|
160
160
|
```
|
|
161
161
|
|
|
162
|
-
### Step 3: [
|
|
162
|
+
### Step 3: [analyst] — Execute pipeline
|
|
163
163
|
|
|
164
164
|
```bash
|
|
165
165
|
# Run processing pipeline
|
|
@@ -182,7 +182,7 @@ print(f'Duplicates: {df.duplicated().sum()}')
|
|
|
182
182
|
"
|
|
183
183
|
```
|
|
184
184
|
|
|
185
|
-
### Step 4: [
|
|
185
|
+
### Step 4: [analyst] — Verify data quality
|
|
186
186
|
|
|
187
187
|
```bash
|
|
188
188
|
# Check output file
|
|
@@ -22,7 +22,7 @@ DNS domain records MX SPF DKIM DMARC A CNAME TXT subdomain
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze DNS requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check current DNS
|
|
@@ -44,7 +44,7 @@ dig example.com TXT | grep -E "spf|dkim|dmarc"
|
|
|
44
44
|
- What email auth? (SPF, DKIM, DMARC)
|
|
45
45
|
- What TTL values? (300s for dynamic, 3600s for stable)
|
|
46
46
|
|
|
47
|
-
### Step 2: [
|
|
47
|
+
### Step 2: [analyst] — Create DNS records
|
|
48
48
|
|
|
49
49
|
**Zone file configuration:**
|
|
50
50
|
```dns
|
|
@@ -112,7 +112,7 @@ curl -X POST "https://api.cloudflare.com/client/v4/zones/ZONE_ID/dns_records" \
|
|
|
112
112
|
}'
|
|
113
113
|
```
|
|
114
114
|
|
|
115
|
-
### Step 3: [
|
|
115
|
+
### Step 3: [analyst] — Apply DNS configuration
|
|
116
116
|
|
|
117
117
|
```bash
|
|
118
118
|
# Verify DNS propagation
|
|
@@ -133,7 +133,7 @@ dig default._domainkey.example.com TXT +short
|
|
|
133
133
|
# Send test email and check headers
|
|
134
134
|
```
|
|
135
135
|
|
|
136
|
-
### Step 4: [
|
|
136
|
+
### Step 4: [analyst] — Verify DNS works
|
|
137
137
|
|
|
138
138
|
```bash
|
|
139
139
|
# Check all records
|
|
@@ -22,7 +22,7 @@ github actions ci cd workflow pipeline automate test build deploy
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze CI/CD requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check existing workflows
|
|
@@ -42,7 +42,7 @@ cat .github/CODEOWNERS 2>/dev/null
|
|
|
42
42
|
- What environments? (dev, staging, prod)
|
|
43
43
|
- What secrets needed? (API keys, deploy tokens)
|
|
44
44
|
|
|
45
|
-
### Step 2: [
|
|
45
|
+
### Step 2: [analyst] — Create workflow files
|
|
46
46
|
|
|
47
47
|
**CI Workflow:**
|
|
48
48
|
```yaml
|
|
@@ -155,7 +155,7 @@ jobs:
|
|
|
155
155
|
curl -f https://example.com/health || exit 1
|
|
156
156
|
```
|
|
157
157
|
|
|
158
|
-
### Step 3: [
|
|
158
|
+
### Step 3: [analyst] — Push and verify workflows
|
|
159
159
|
|
|
160
160
|
```bash
|
|
161
161
|
# Create workflow directory
|
|
@@ -174,7 +174,7 @@ gh run list --limit=5
|
|
|
174
174
|
gh run view <run-id>
|
|
175
175
|
```
|
|
176
176
|
|
|
177
|
-
### Step 4: [
|
|
177
|
+
### Step 4: [analyst] — Verify CI/CD works
|
|
178
178
|
|
|
179
179
|
```bash
|
|
180
180
|
# Check workflow status
|
|
@@ -22,7 +22,7 @@ kafka message queue event streaming async processing producer consumer
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze messaging requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check Kafka availability
|
|
@@ -40,7 +40,7 @@ kafka-topics --bootstrap-server localhost:9092 --describe 2>/dev/null | head -20
|
|
|
40
40
|
- What ordering? (per-partition, global)
|
|
41
41
|
- What retention? (hours, days, forever)
|
|
42
42
|
|
|
43
|
-
### Step 2: [
|
|
43
|
+
### Step 2: [analyst] — Implement Kafka producers and consumers
|
|
44
44
|
|
|
45
45
|
**Producer:**
|
|
46
46
|
```python
|
|
@@ -134,7 +134,7 @@ consumer = EventConsumer('my-consumer-group')
|
|
|
134
134
|
consumer.consume(['user-events'], handle_event)
|
|
135
135
|
```
|
|
136
136
|
|
|
137
|
-
### Step 3: [
|
|
137
|
+
### Step 3: [analyst] — Deploy and test
|
|
138
138
|
|
|
139
139
|
```bash
|
|
140
140
|
# Create topics
|
|
@@ -168,7 +168,7 @@ kafka-consumer-groups --bootstrap-server localhost:9092 \
|
|
|
168
168
|
--describe --group my-consumer-group
|
|
169
169
|
```
|
|
170
170
|
|
|
171
|
-
### Step 4: [
|
|
171
|
+
### Step 4: [analyst] — Verify Kafka works
|
|
172
172
|
|
|
173
173
|
```bash
|
|
174
174
|
# Check topic stats
|
|
@@ -22,7 +22,7 @@ kubernetes k8s cluster pod deployment service ingress helm
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze cluster and workload requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check cluster status
|
|
@@ -44,7 +44,7 @@ kubectl get pods --all-namespaces | grep -v kube-system
|
|
|
44
44
|
- What storage? (PV/PVC, StorageClass, local vs network)
|
|
45
45
|
- What security? (RBAC, PodSecurityPolicy, NetworkPolicy)
|
|
46
46
|
|
|
47
|
-
### Step 2: [
|
|
47
|
+
### Step 2: [analyst] — Create Kubernetes manifests
|
|
48
48
|
|
|
49
49
|
**Deployment with best practices:**
|
|
50
50
|
```yaml
|
|
@@ -184,7 +184,7 @@ spec:
|
|
|
184
184
|
averageUtilization: 80
|
|
185
185
|
```
|
|
186
186
|
|
|
187
|
-
### Step 3: [
|
|
187
|
+
### Step 3: [analyst] — Deploy and configure
|
|
188
188
|
|
|
189
189
|
```bash
|
|
190
190
|
# Apply manifests
|
|
@@ -207,7 +207,7 @@ curl http://localhost:8080/healthz
|
|
|
207
207
|
kubectl logs -f deployment/myapp -n production --tail=100
|
|
208
208
|
```
|
|
209
209
|
|
|
210
|
-
### Step 4: [
|
|
210
|
+
### Step 4: [analyst] — Verify cluster health
|
|
211
211
|
|
|
212
212
|
```bash
|
|
213
213
|
# Check all resources
|
|
@@ -22,7 +22,7 @@ load balancer nginx haproxy health check failover session persistence round-robi
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze load balancing requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check backend servers
|
|
@@ -40,7 +40,7 @@ ss -s
|
|
|
40
40
|
- What health checks? (HTTP, TCP, custom)
|
|
41
41
|
- What session needs? (sticky sessions, stateless)
|
|
42
42
|
|
|
43
|
-
### Step 2: [
|
|
43
|
+
### Step 2: [analyst] — Configure load balancer
|
|
44
44
|
|
|
45
45
|
**Nginx load balancer:**
|
|
46
46
|
```nginx
|
|
@@ -118,7 +118,7 @@ backend backend_servers
|
|
|
118
118
|
server backend3 10.0.0.3:8080 check inter 5s fall 3 rise 2 backup
|
|
119
119
|
```
|
|
120
120
|
|
|
121
|
-
### Step 3: [
|
|
121
|
+
### Step 3: [analyst] — Deploy and test
|
|
122
122
|
|
|
123
123
|
```bash
|
|
124
124
|
# Test load balancing
|
|
@@ -139,7 +139,7 @@ curl -s http://example.com/whoami # Should route to backend2/3
|
|
|
139
139
|
curl -s http://localhost/nginx_status
|
|
140
140
|
```
|
|
141
141
|
|
|
142
|
-
### Step 4: [
|
|
142
|
+
### Step 4: [analyst] — Verify load balancing works
|
|
143
143
|
|
|
144
144
|
```bash
|
|
145
145
|
# Verify traffic distribution
|
|
@@ -22,7 +22,7 @@ log rotation compress archive retention disk space cleanup syslog
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze logging setup
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check current log sizes
|
|
@@ -44,7 +44,7 @@ find /var/log -name "*.log" -size +100M -exec ls -lh {} \;
|
|
|
44
44
|
- What retention? (7 days, 30 days, 1 year)
|
|
45
45
|
- What compression? (gzip, bzip2, xz)
|
|
46
46
|
|
|
47
|
-
### Step 2: [
|
|
47
|
+
### Step 2: [analyst] — Configure log rotation
|
|
48
48
|
|
|
49
49
|
**Logrotate configuration:**
|
|
50
50
|
```bash
|
|
@@ -125,7 +125,7 @@ find "$ARCHIVE_DIR" -name "*.gz" -mtime +365 -delete
|
|
|
125
125
|
logger "Log cleanup completed: rotated $(find "$LOG_DIR" -name "*.log.gz" | wc -l) files"
|
|
126
126
|
```
|
|
127
127
|
|
|
128
|
-
### Step 3: [
|
|
128
|
+
### Step 3: [analyst] — Deploy and test
|
|
129
129
|
|
|
130
130
|
```bash
|
|
131
131
|
# Test logrotate configuration
|
|
@@ -145,7 +145,7 @@ chmod +x /usr/local/bin/log-cleanup.sh
|
|
|
145
145
|
/usr/local/bin/log-cleanup.sh
|
|
146
146
|
```
|
|
147
147
|
|
|
148
|
-
### Step 4: [
|
|
148
|
+
### Step 4: [analyst] — Verify rotation works
|
|
149
149
|
|
|
150
150
|
```bash
|
|
151
151
|
# Check disk usage after rotation
|
|
@@ -22,7 +22,7 @@ machine learning model training evaluation prediction scikit-learn tensorflow py
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze data and requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check available data
|
|
@@ -43,7 +43,7 @@ nvidia-smi 2>/dev/null || echo "No GPU"
|
|
|
43
43
|
- What metrics matter? (accuracy, F1, RMSE, AUC)
|
|
44
44
|
- What constraints? (latency, memory, explainability)
|
|
45
45
|
|
|
46
|
-
### Step 2: [
|
|
46
|
+
### Step 2: [analyst] — Build training pipeline
|
|
47
47
|
|
|
48
48
|
```python
|
|
49
49
|
# src/models/train.py
|
|
@@ -138,7 +138,7 @@ if __name__ == '__main__':
|
|
|
138
138
|
save_model(model, scaler, metrics)
|
|
139
139
|
```
|
|
140
140
|
|
|
141
|
-
### Step 3: [
|
|
141
|
+
### Step 3: [analyst] — Train and evaluate
|
|
142
142
|
|
|
143
143
|
```bash
|
|
144
144
|
# Train model
|
|
@@ -188,7 +188,7 @@ EOF
|
|
|
188
188
|
uvicorn src.models.serve:app --host 0.0.0.0 --port 8000
|
|
189
189
|
```
|
|
190
190
|
|
|
191
|
-
### Step 4: [
|
|
191
|
+
### Step 4: [analyst] — Verify model quality
|
|
192
192
|
|
|
193
193
|
```bash
|
|
194
194
|
# Check model metrics
|
|
@@ -22,7 +22,7 @@ nginx reverse proxy load balancer web server ssl tls
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze serving requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check Nginx version and modules
|
|
@@ -46,7 +46,7 @@ ss -tlnp | grep -E ":(80|443|8080)"
|
|
|
46
46
|
- What rate limits? (per-IP, per-endpoint, global)
|
|
47
47
|
- What caching? (proxy cache, microcaching, browser cache)
|
|
48
48
|
|
|
49
|
-
### Step 2: [
|
|
49
|
+
### Step 2: [analyst] — Write Nginx configuration
|
|
50
50
|
|
|
51
51
|
**Reverse proxy with SSL:**
|
|
52
52
|
```nginx
|
|
@@ -166,7 +166,7 @@ server {
|
|
|
166
166
|
}
|
|
167
167
|
```
|
|
168
168
|
|
|
169
|
-
### Step 3: [
|
|
169
|
+
### Step 3: [analyst] — Apply and test configuration
|
|
170
170
|
|
|
171
171
|
```bash
|
|
172
172
|
# Test configuration
|
|
@@ -191,7 +191,7 @@ tail -f /var/log/nginx/error.log
|
|
|
191
191
|
curl http://localhost/nginx_status
|
|
192
192
|
```
|
|
193
193
|
|
|
194
|
-
### Step 4: [
|
|
194
|
+
### Step 4: [analyst] — Verify configuration works
|
|
195
195
|
|
|
196
196
|
```bash
|
|
197
197
|
# Test SSL grade (should be A+)
|
|
@@ -22,7 +22,7 @@ prometheus monitoring metrics alert grafana dashboard promql
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Define monitoring requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check if Prometheus is already running
|
|
@@ -40,7 +40,7 @@ curl -s http://localhost:3000/api/health 2>/dev/null
|
|
|
40
40
|
- What alert channels? (Slack, PagerDuty, email)
|
|
41
41
|
- What dashboards needed? (overview, service-specific, infrastructure)
|
|
42
42
|
|
|
43
|
-
### Step 2: [
|
|
43
|
+
### Step 2: [analyst] — Configure Prometheus and alerting
|
|
44
44
|
|
|
45
45
|
**Prometheus config:**
|
|
46
46
|
```yaml
|
|
@@ -177,7 +177,7 @@ inhibit_rules:
|
|
|
177
177
|
equal: ['alertname', 'instance']
|
|
178
178
|
```
|
|
179
179
|
|
|
180
|
-
### Step 3: [
|
|
180
|
+
### Step 3: [analyst] — Deploy monitoring stack
|
|
181
181
|
|
|
182
182
|
```bash
|
|
183
183
|
# Deploy with Docker Compose
|
|
@@ -195,7 +195,7 @@ curl -X POST http://localhost:3000/api/dashboards/db \
|
|
|
195
195
|
-d @grafana-dashboard.json
|
|
196
196
|
```
|
|
197
197
|
|
|
198
|
-
### Step 4: [
|
|
198
|
+
### Step 4: [analyst] — Verify monitoring works
|
|
199
199
|
|
|
200
200
|
```bash
|
|
201
201
|
# Verify metrics are being collected
|
|
@@ -22,7 +22,7 @@ redis cache session store rate limit pub sub queue
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze caching requirements
|
|
26
26
|
|
|
27
27
|
Map the caching needs:
|
|
28
28
|
- **Read/write ratio**: High-read workloads benefit most from caching
|
|
@@ -40,7 +40,7 @@ redis-cli INFO memory | grep used_memory_human
|
|
|
40
40
|
redis-cli INFO clients
|
|
41
41
|
```
|
|
42
42
|
|
|
43
|
-
### Step 2: [
|
|
43
|
+
### Step 2: [analyst] — Implement Redis connection and caching layer
|
|
44
44
|
|
|
45
45
|
Choose strategy based on requirements:
|
|
46
46
|
|
|
@@ -98,7 +98,7 @@ def is_rate_limited(user_id, max_requests=100, window=60):
|
|
|
98
98
|
return results[2] > max_requests
|
|
99
99
|
```
|
|
100
100
|
|
|
101
|
-
### Step 3: [
|
|
101
|
+
### Step 3: [analyst] — Configure Redis for production
|
|
102
102
|
|
|
103
103
|
```bash
|
|
104
104
|
# Redis config for production
|
|
@@ -133,7 +133,7 @@ redis-cli CONFIG GET maxmemory
|
|
|
133
133
|
redis-cli CONFIG GET maxmemory-policy
|
|
134
134
|
```
|
|
135
135
|
|
|
136
|
-
### Step 4: [
|
|
136
|
+
### Step 4: [analyst] — Verify caching works correctly
|
|
137
137
|
|
|
138
138
|
```bash
|
|
139
139
|
# Test cache hit/miss
|
|
@@ -22,7 +22,7 @@ secrets manager vault AWS secrets manager credential rotation encryption key man
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze secrets requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check existing secrets
|
|
@@ -42,7 +42,7 @@ find . -name ".env*" -exec ls -la {} \;
|
|
|
42
42
|
- What compliance? (SOC2, HIPAA, PCI-DSS)
|
|
43
43
|
- What encryption? (AES-256, KMS, HSM)
|
|
44
44
|
|
|
45
|
-
### Step 2: [
|
|
45
|
+
### Step 2: [analyst] — Implement secrets management
|
|
46
46
|
|
|
47
47
|
**AWS Secrets Manager:**
|
|
48
48
|
```python
|
|
@@ -115,7 +115,7 @@ vault write database/roles/myapp \
|
|
|
115
115
|
max_ttl="24h"
|
|
116
116
|
```
|
|
117
117
|
|
|
118
|
-
### Step 3: [
|
|
118
|
+
### Step 3: [analyst] — Deploy and configure
|
|
119
119
|
|
|
120
120
|
```bash
|
|
121
121
|
# Store secrets in AWS
|
|
@@ -140,7 +140,7 @@ print(sm.get_secret('prod/myapp/database'))
|
|
|
140
140
|
"
|
|
141
141
|
```
|
|
142
142
|
|
|
143
|
-
### Step 4: [
|
|
143
|
+
### Step 4: [analyst] — Verify secrets management
|
|
144
144
|
|
|
145
145
|
```bash
|
|
146
146
|
# Check secret access logs
|
|
@@ -22,7 +22,7 @@ SSL TLS certificate HTTPS Let's Encrypt certbot ACME wildcard renewal
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze certificate requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check existing certificates
|
|
@@ -42,7 +42,7 @@ certbot certificates 2>/dev/null
|
|
|
42
42
|
- What server? (Nginx, Apache, Cloudflare)
|
|
43
43
|
- What auto-renewal? (certbot, custom script)
|
|
44
44
|
|
|
45
|
-
### Step 2: [
|
|
45
|
+
### Step 2: [analyst] — Configure certificates
|
|
46
46
|
|
|
47
47
|
**Let's Encrypt with certbot:**
|
|
48
48
|
```bash
|
|
@@ -81,7 +81,7 @@ openssl verify -CAfile /etc/letsencrypt/live/example.com/chain.pem \
|
|
|
81
81
|
openssl x509 -in /etc/letsencrypt/live/example.com/fullchain.pem -noout -text
|
|
82
82
|
```
|
|
83
83
|
|
|
84
|
-
### Step 3: [
|
|
84
|
+
### Step 3: [analyst] — Deploy and verify
|
|
85
85
|
|
|
86
86
|
```bash
|
|
87
87
|
# Test SSL configuration
|
|
@@ -97,7 +97,7 @@ openssl s_client -connect example.com:443 -servername example.com < /dev/null 2>
|
|
|
97
97
|
sudo certbot renew --dry-run
|
|
98
98
|
```
|
|
99
99
|
|
|
100
|
-
### Step 4: [
|
|
100
|
+
### Step 4: [analyst] — Verify SSL works
|
|
101
101
|
|
|
102
102
|
```bash
|
|
103
103
|
# Verify HTTPS redirects
|
|
@@ -22,7 +22,7 @@ logging structured json log aggregation elk loki Winston pino
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Analyze logging requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check existing logging
|
|
@@ -40,7 +40,7 @@ docker ps | grep -E "elk|loki|fluentd" 2>/dev/null
|
|
|
40
40
|
- What transport? (stdout, file, ELK, Loki)
|
|
41
41
|
- What compliance? (audit logging, PII masking)
|
|
42
42
|
|
|
43
|
-
### Step 2: [
|
|
43
|
+
### Step 2: [analyst] — Implement structured logging
|
|
44
44
|
|
|
45
45
|
**Pino logger setup:**
|
|
46
46
|
```typescript
|
|
@@ -109,7 +109,7 @@ export function logError(err: Error, context: Record<string, unknown> = {}) {
|
|
|
109
109
|
}
|
|
110
110
|
```
|
|
111
111
|
|
|
112
|
-
### Step 3: [
|
|
112
|
+
### Step 3: [analyst] — Configure log transport
|
|
113
113
|
|
|
114
114
|
```bash
|
|
115
115
|
# Development: stdout with pretty printing
|
|
@@ -142,7 +142,7 @@ cat > /etc/fluentd/conf.d/app.conf << 'EOF'
|
|
|
142
142
|
EOF
|
|
143
143
|
```
|
|
144
144
|
|
|
145
|
-
### Step 4: [
|
|
145
|
+
### Step 4: [analyst] — Verify logging works
|
|
146
146
|
|
|
147
147
|
```bash
|
|
148
148
|
# Verify structured output
|
|
@@ -22,7 +22,7 @@ terraform infrastructure iac provision cloud resource module state
|
|
|
22
22
|
|
|
23
23
|
## Steps
|
|
24
24
|
|
|
25
|
-
### Step 1: [
|
|
25
|
+
### Step 1: [analyst] — Map infrastructure requirements
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
# Check Terraform version
|
|
@@ -41,7 +41,7 @@ terraform state list 2>/dev/null || echo "No existing state"
|
|
|
41
41
|
- What state backend? (S3+DynamoDB, GCS, Terraform Cloud)
|
|
42
42
|
- What compliance requirements? (encryption, tagging, logging)
|
|
43
43
|
|
|
44
|
-
### Step 2: [
|
|
44
|
+
### Step 2: [analyst] — Write Terraform configurations
|
|
45
45
|
|
|
46
46
|
**Project structure:**
|
|
47
47
|
```
|
|
@@ -120,7 +120,7 @@ terraform {
|
|
|
120
120
|
}
|
|
121
121
|
```
|
|
122
122
|
|
|
123
|
-
### Step 3: [
|
|
123
|
+
### Step 3: [analyst] — Apply infrastructure
|
|
124
124
|
|
|
125
125
|
```bash
|
|
126
126
|
# Initialize
|
|
@@ -153,7 +153,7 @@ terraform output
|
|
|
153
153
|
run: terraform apply -auto-approve tfplan
|
|
154
154
|
```
|
|
155
155
|
|
|
156
|
-
### Step 4: [
|
|
156
|
+
### Step 4: [analyst] — Verify infrastructure
|
|
157
157
|
|
|
158
158
|
```bash
|
|
159
159
|
# Check for drift
|