@jetrabbits/agentic 0.3.0 → 0.3.1

package/areas/devops/ci-cd/AGENTS.md

@@ -4,13 +4,6 @@
 
 Continuous integration and delivery pipelines: GitHub Actions, GitLab CI, quality gates, artifact management, build optimization, supply-chain security, and pipeline security hardening.
 
-## Guidance chain
-
-1. Project `.agent/` baseline
-2. `ci-cd/rules/*` — load all
-3. `ci-cd/skills/*/SKILL.md` — load only the skill matching the current task
-4. `ci-cd/workflows/*` — load the workflow matching the triggered command
-
 ## Cross-cutting constraints
 
 - **No secrets in pipeline YAML** — all credentials via vault / environment secrets, never inline.
@@ -21,7 +14,7 @@ Continuous integration and delivery pipelines: GitHub Actions, GitLab CI, qualit
 ## Spec map
 
 ```text
-ci-cd/
+.agent/
 ├── rules/
 │   ├── pipeline-standards.md         ← stage order, naming, timeout policies
 │   ├── quality-gates.md              ← required checks, merge block conditions
@@ -39,10 +32,3 @@ ci-cd/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/devops/database-ops/AGENTS.md

@@ -4,13 +4,6 @@
 
 Operational database management: backup verification, performance tuning, migration safety, incident response, PostgreSQL and Redis operations. Focus is on production database reliability, not application-level ORM usage.
 
-## Guidance chain
-
-1. Project `.agent/` baseline
-2. `database-ops/rules/*` — load all
-3. `database-ops/skills/*/SKILL.md` — load only the skill matching the current task
-4. `database-ops/workflows/*` — load the workflow matching the triggered command
-
 ## Cross-cutting constraints
 
 - **Backups are not optional** — every production database has a verified backup and a tested restore procedure.
@@ -21,7 +14,7 @@ Operational database management: backup verification, performance tuning, migrat
 ## Spec map
 
 ```text
-database-ops/
+.agent/
 ├── rules/
 │   ├── backup-policy.md         ← frequency, retention, offsite requirements
 │   ├── access-control.md        ← least-privilege roles, audit logging, break-glass
@@ -38,10 +31,3 @@ database-ops/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/devops/devsecops/AGENTS.md

@@ -4,13 +4,6 @@
 
 Shift-left security integration: container hardening, SBOM and supply-chain attestation, OPA / Kyverno policy enforcement, secret detection, and Sigstore artifact signing. Security controls are embedded in the delivery pipeline, not applied after the fact.
 
-## Guidance chain
-
-1. Project `.agent/` baseline
-2. `devsecops/rules/*` — load all
-3. `devsecops/skills/*/SKILL.md` — load only the skill matching the current task
-4. `devsecops/workflows/*` — load the workflow matching the triggered command
-
 ## Cross-cutting constraints
 
 - **Shift left** — security checks run in CI, not in a post-deploy audit.
@@ -21,7 +14,7 @@ Shift-left security integration: container hardening, SBOM and supply-chain atte
 ## Spec map
 
 ```text
-devsecops/
+.agent/
 ├── rules/
 │   ├── shift-left-policy.md       ← required CI checks, fail-fast thresholds
 │   ├── container-security.md      ← base image standards, rootless, read-only FS
@@ -38,10 +31,3 @@ devsecops/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/devops/infrastructure/AGENTS.md

@@ -4,13 +4,6 @@
 
 Infrastructure-as-Code lifecycle: Terraform module authoring, environment provisioning and destruction, drift detection and remediation, state management, Ansible playbooks, cost optimization, and secret hygiene.
 
-## Guidance chain
-
-1. Project `.agent/` baseline
-2. `infrastructure/rules/*` — load all
-3. `infrastructure/skills/*/SKILL.md` — load only the skill matching the current task
-4. `infrastructure/workflows/*` — load the workflow matching the triggered command
-
 ## Cross-cutting constraints
 
 - **IaC-only changes** — zero manual console or CLI changes in non-development environments; document exceptions.
@@ -21,7 +14,7 @@ Infrastructure-as-Code lifecycle: Terraform module authoring, environment provis
 ## Spec map
 
 ```text
-infrastructure/
+.agent/
 ├── rules/
 │   ├── iac-standards.md       ← module structure, naming, provider pinning
 │   ├── immutability.md        ← replace-before-destroy, no in-place secret mutations
@@ -41,10 +34,3 @@ infrastructure/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/devops/kubernetes/AGENTS.md

@@ -4,13 +4,6 @@
 
 Self-hosted and managed Kubernetes cluster operations: cluster bootstrap, workload onboarding, RBAC design, network policies, resource governance, upgrade management, and pod-level debugging.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `kubernetes/rules/*` — load all
-3. `kubernetes/skills/*/SKILL.md` — load only the skill matching the current task
-4. `kubernetes/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from devops area
 
 - Infrastructure-as-Code immutability principle — no manual kubectl edits in production.
@@ -27,7 +20,7 @@ Self-hosted and managed Kubernetes cluster operations: cluster bootstrap, worklo
 ## Spec map
 
 ```text
-kubernetes/
+.agent/
 ├── rules/
 │   ├── cluster-standards.md      ← node sizing, OS, CRI, CNI constraints
 │   ├── workload-security.md      ← PSA levels, RBAC defaults, network policy baselines
@@ -48,10 +41,3 @@ kubernetes/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/devops/networking/AGENTS.md

@@ -4,13 +4,6 @@
 
 Platform networking: Kubernetes ingress design, TLS termination, service mesh onboarding, DNS management, VPC design, and network segmentation. Networking changes are high-blast-radius — this area enforces a plan-review-apply discipline.
 
-## Guidance chain
-
-1. Project `.agent/` baseline
-2. `networking/rules/*` — load all
-3. `networking/skills/*/SKILL.md` — load only the skill matching the current task
-4. `networking/workflows/*` — load the workflow matching the triggered command
-
 ## Cross-cutting constraints
 
 - **TLS everywhere** — plaintext traffic is forbidden between services and at ingress, without exception.
@@ -21,7 +14,7 @@ Platform networking: Kubernetes ingress design, TLS termination, service mesh on
 ## Spec map
 
 ```text
-networking/
+.agent/
 ├── rules/
 │   ├── tls-policy.md               ← minimum TLS version, cert rotation, mTLS requirements
 │   ├── ingress-standards.md        ← ingress class, annotations, rate limiting, WAF baseline
@@ -38,10 +31,3 @@ networking/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/devops/observability/AGENTS.md

@@ -4,13 +4,6 @@
 
 Platform observability: Prometheus metrics and Alertmanager rules, Loki log aggregation, Tempo distributed tracing, Grafana dashboards, SLO implementation, and service monitoring onboarding.
 
-## Guidance chain
-
-1. Project `.agent/` baseline
-2. `observability/rules/*` — load all
-3. `observability/skills/*/SKILL.md` — load only the skill matching the current task
-4. `observability/workflows/*` — load the workflow matching the triggered command
-
 ## Cross-cutting constraints
 
 - **Golden signals first** — every new service exposes latency, traffic, errors, and saturation before any custom metrics.
@@ -21,7 +14,7 @@ Platform observability: Prometheus metrics and Alertmanager rules, Loki log aggr
 ## Spec map
 
 ```text
-observability/
+.agent/
 ├── rules/
 │   ├── golden-signals.md        ← required metrics per service, naming conventions
 │   ├── alerting-standards.md    ← severity levels, routing, inhibition, runbook requirement
@@ -39,10 +32,3 @@ observability/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/devops/sre/AGENTS.md

@@ -4,13 +4,6 @@
 
 Site reliability engineering: SLO/SLI design, error budget policy, chaos engineering, capacity planning, incident command, and post-mortem facilitation. The SRE area treats reliability as a measurable feature with a finite budget — not a vague aspiration.
 
-## Guidance chain
-
-1. Project `.agent/` baseline
-2. `sre/rules/*` — load all
-3. `sre/skills/*/SKILL.md` — load matching skill only
-4. `sre/workflows/*` — load matching workflow
-
 ## Cross-cutting constraints
 
 - **SLOs drive decisions** — if error budget remains, ship features; if exhausted, halt features and fix reliability.
@@ -21,7 +14,7 @@ Site reliability engineering: SLO/SLI design, error budget policy, chaos enginee
 ## Spec map
 
 ```text
-sre/
+.agent/
 ├── rules/
 │   ├── slo-policy.md             ← SLO definition standards, window sizes, target tiers
 │   ├── error-budget-policy.md    ← budget consumption thresholds, freeze triggers
@@ -39,10 +32,3 @@ sre/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/backend/AGENTS.md

@@ -4,14 +4,6 @@
 
 Server-side service development: REST / GraphQL API design, domain modeling, database access patterns, async processing, observability, and security. Load after `software/general/` baseline.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `backend/rules/*` — load all for this spec
-4. `backend/skills/*/SKILL.md` — load only the skill matching the current task
-5. `backend/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from general
 
 - SDLC methodology and role responsibilities
@@ -27,7 +19,7 @@ Server-side service development: REST / GraphQL API design, domain modeling, dat
 ## Spec map
 
 ```text
-backend/
+.agent/
 ├── rules/
 │   ├── architecture.md       ← layering, module boundaries, dependency direction
 │   ├── data_access.md        ← ORM usage, query patterns, N+1 prevention
@@ -50,10 +42,3 @@ backend/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/data-engineering/AGENTS.md

@@ -4,14 +4,6 @@
 
 Data pipeline engineering: dbt model development, data warehouse schema management, orchestration (Airflow / Prefect), data quality checks, lineage governance, SQL optimization, streaming patterns, and PII-safe data handling.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `data-engineering/rules/*` — load all for this spec
-4. `data-engineering/skills/*/SKILL.md` — load only the skill matching the current task
-5. `data-engineering/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from general
 
 - SDLC methodology and handoff contracts
@@ -27,7 +19,7 @@ Data pipeline engineering: dbt model development, data warehouse schema manageme
 ## Spec map
 
 ```text
-data-engineering/
+.agent/
 ├── rules/
 │   ├── data-governance.md      ← data ownership, access tiers, retention policy
 │   ├── pii-handling.md         ← classification, masking, pseudonymization requirements
@@ -50,10 +42,3 @@ data-engineering/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/frontend/AGENTS.md

@@ -4,14 +4,6 @@
 
 UI and component development: component architecture, accessibility (WCAG AA), performance budgets, state management, API integration, CSS architecture, visual regression, and bundle analysis.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `frontend/rules/*` — load all for this spec
-4. `frontend/skills/*/SKILL.md` — load only the skill matching the current task
-5. `frontend/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from general
 
 - SDLC roles and quality gates
@@ -27,7 +19,7 @@ UI and component development: component architecture, accessibility (WCAG AA), p
 ## Spec map
 
 ```text
-frontend/
+.agent/
 ├── rules/
 │   ├── accessibility.md    ← WCAG AA requirements, ARIA patterns, keyboard navigation
 │   ├── architecture.md     ← component hierarchy, coupling, folder structure
@@ -51,10 +43,3 @@ frontend/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/full-stack/AGENTS.md

@@ -4,14 +4,6 @@
 
 End-to-end product feature development spanning backend services and frontend interfaces: API design, backend architecture, database access, async processing, frontend integration, testing pipelines, and full project lifecycle management.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `full-stack/rules/*` — load all for this spec
-4. `full-stack/skills/*/SKILL.md` — load only the skill matching the current task
-5. `full-stack/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from general
 
 - SDLC methodology, role responsibilities, and handoff contracts
@@ -27,7 +19,7 @@ End-to-end product feature development spanning backend services and frontend in
 ## Spec map
 
 ```text
-full-stack/
+.agent/
 ├── rules/
 │   ├── api-design-guide.md            ← REST/GraphQL/tRPC conventions, versioning
 │   ├── backend-architecture-rule.md   ← layering, module boundaries, DI
@@ -60,10 +52,3 @@ full-stack/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/general/AGENTS.md

@@ -41,7 +41,7 @@ Specializations reference general guidance and keep only domain-specific overrid
 ## Guidance tree
 
 ```text
-general/
+.agent/
 ├── rules/
 │   ├── git-workflow-guide.md          ← branching, commit messages, PR conventions
 │   ├── github-workflow-guide.md       ← GitHub-specific CI triggers and branch protection
@@ -60,9 +60,3 @@ general/
     ├── code-review-workflow.md         ← /code-review
     └── development-cycle-workflow.md   ← /dev-cycle
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`

package/areas/software/mlops/AGENTS.md

@@ -4,14 +4,6 @@
 
 Machine learning operations: experiment tracking, model training pipelines, feature engineering, model evaluation, champion/challenger workflows, inference serving, model monitoring, and production safety gates. MLOps treats models as software artifacts with the same reproducibility and observability requirements as any production service.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `mlops/rules/*` — load all for this spec
-4. `mlops/skills/*/SKILL.md` — load only the skill matching the current task
-5. `mlops/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from general
 
 - SDLC methodology and handoff contracts
@@ -27,7 +19,7 @@ Machine learning operations: experiment tracking, model training pipelines, feat
 ## Spec map
 
 ```text
-mlops/
+.agent/
 ├── rules/
 │   ├── reproducibility.md      ← seed pinning, dependency locking, artifact versioning
 │   ├── data-integrity.md       ← training data lineage, validation, split discipline
@@ -48,10 +40,3 @@ mlops/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/mobile/AGENTS.md

@@ -4,14 +4,6 @@
 
 iOS, Android, and cross-platform mobile development (React Native, Flutter): offline-first architecture, platform compliance (App Store / Play Store), performance budgets, native module integration, push notifications, OTA update delivery, release builds, and crash triage.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `mobile/rules/*` — load all for this spec
-4. `mobile/skills/*/SKILL.md` — load only the skill matching the current task
-5. `mobile/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from general
 
 - SDLC methodology and handoff contracts
@@ -27,7 +19,7 @@ iOS, Android, and cross-platform mobile development (React Native, Flutter): off
 ## Spec map
 
 ```text
-mobile/
+.agent/
 ├── rules/
 │   ├── offline-first.md          ← local state, sync strategy, conflict resolution
 │   ├── performance-budget.md     ← frame rate, TTI, memory, crash rate thresholds
@@ -49,10 +41,3 @@ mobile/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/platform/AGENTS.md

@@ -4,14 +4,6 @@
 
 Internal platform engineering for software teams: Kubernetes manifests, Terraform patterns, CI/CD pipeline setup, secrets management, observability stack configuration, networking, cost governance, and production incident response. The platform area bridges software development and dedicated DevOps specializations.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `platform/rules/*` — load all for this spec
-4. `platform/skills/*/SKILL.md` — load only the skill matching the current task
-5. `platform/workflows/*` — load the workflow matching the triggered command
-
 ## Spec selection
 
 For deep platform specialization, prefer the dedicated DevOps area specs:
@@ -35,7 +27,7 @@ For deep platform specialization, prefer the dedicated DevOps area specs:
 ## Spec map
 
 ```text
-platform/
+.agent/
 ├── rules/
 │   ├── immutability.md        ← no manual infra changes; IaC-first discipline
 │   ├── reliability.md         ← SLO targets, incident severity, on-call expectations
@@ -58,10 +50,3 @@ platform/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/qa/AGENTS.md

@@ -4,14 +4,6 @@
 
 Test strategy, risk-based verification, and release confidence: test pyramid design, flakiness management, performance auditing, regression suite maintenance, test data management, and accessibility testing.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `qa/rules/*` — load all for this spec
-4. `qa/skills/*/SKILL.md` — load only the skill matching the current task
-5. `qa/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from general
 
 - SDLC role responsibilities and handoffs
@@ -27,7 +19,7 @@ Test strategy, risk-based verification, and release confidence: test pyramid des
 ## Spec map
 
 ```text
-qa/
+.agent/
 ├── rules/
 │   ├── test-strategy.md       ← pyramid ratios, coverage targets, risk classification
 │   ├── quality-gates.md       ← blocking vs advisory criteria, merge conditions
@@ -49,10 +41,3 @@ qa/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/software/security/AGENTS.md

@@ -4,14 +4,6 @@
 
 Application and infrastructure security: secure coding standards, dependency auditing, SAST/DAST interpretation, threat modeling, auth patterns, cryptography standards, security headers, secret rotation, and compliance reporting.
 
-## Guidance chain
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `software/general/rules/*` — always active
-3. `security/rules/*` — load all for this spec
-4. `security/skills/*/SKILL.md` — load only the skill matching the current task
-5. `security/workflows/*` — load the workflow matching the triggered command
-
 ## Inherited from general
 
 - Git / CI quality baseline
@@ -27,7 +19,7 @@ Application and infrastructure security: secure coding standards, dependency aud
 ## Spec map
 
 ```text
-security/
+.agent/
 ├── rules/
 │   ├── secure-coding.md          ← OWASP Top 10 mitigations, input validation, output encoding
 │   ├── secrets-policy.md         ← storage, rotation, access audit, emergency rotation
@@ -49,10 +41,3 @@ security/
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/areas/template/AGENTS.tmpl.md

@@ -12,15 +12,6 @@ Delete all AGENT INSTRUCTIONS comments before finalising.
 
 {{ONE_PARAGRAPH: what domain this spec covers, who uses it, and what kinds of work it guides agents through.}}
 
-## Guidance chain
-
-Load in this order:
-
-1. Project `.agent/` baseline (`AGENTS.md` + `.agent/*`)
-2. `{{domain}}/{{spec}}/rules/*` — load all rules for this spec
-3. `{{domain}}/{{spec}}/skills/*/SKILL.md` — load only the skill matching the current task (see "When to load" in each skill)
-4. `{{domain}}/{{spec}}/workflows/*` — load the workflow matching the triggered slash command
-
 ## Inherited from {{DOMAIN_NAME}} area
 
 <!--
@@ -45,7 +36,7 @@ Avoid advice-language: "consider", "try to", "ideally".
 ## Spec map
 
 ```text
-{{spec-name}}/
+.agent/
 ├── rules/
 │   ├── {{filename}}.md     ← {{one_line_description}}
 │   └── {{filename}}.md     ← {{one_line_description}}
@@ -58,10 +49,3 @@ Avoid advice-language: "consider", "try to", "ideally".
 └── prompts/
     └── *.md
 ```
-
-## Discovery patterns
-
-- `rules/*.md`
-- `skills/*/SKILL.md`
-- `workflows/*.md`
-- `prompts/*.md`

package/docs/agentic-lifecycle.md

@@ -22,7 +22,7 @@ theme=auto
 
 Supported values are `auto`, `dark`, and `light`.
 
-Target projects receive `.agentic.json`. It stores selected install settings, managed file paths, source paths, hashes, generated marker type, and skipped files from the latest rerun.
+Target projects receive `.agentic.json`. It stores selected install settings, optional project-level OpenCode plugin configuration, managed file paths, source paths, hashes, generated marker type, and skipped files from the latest rerun. When Telegram notifications are enabled, `.agentic.json` includes plaintext `botToken` and `chatId`; keep that file out of public repositories.
 
 ## Repository modes
 
@@ -109,6 +109,10 @@ When MemPalace MCP is enabled during interactive install, TUI install, or throug
 1. Python availability check
 2. pip availability check
 3. `pip install mempalace`
-4. Explicit skip log for automatic project initialization, plus optional manual `mempalace init`/`mempalace mine` instructions
+4. Project memory initialization with `mempalace init --yes --no-llm`
+5. Project mining with `mempalace mine <project> --wing <project-basename>`
+6. Optional shared docs mining with `mempalace mine <project>/docs --wing shared_docs`
 
-If auto-install or runtime checks fail, `agentic` prints manual setup instructions and continues. After setup, install checks that `mempalace-mcp` is present and leaves runtime startup/tool validation to the post-install doctor smoke check. Generated MCP configs invoke `mempalace-mcp` without arguments for all supported agent targets.
+If auto-install, initialization, mining, or runtime checks fail, `agentic` prints manual setup instructions and continues. When `pip install mempalace` fails, the warning includes the pip exit status, a temporary pip output log path, and the first non-empty pip output line as the likely reason. The full pip output is also copied into the main Agentic run log. After setup, install checks that `mempalace-mcp` is present and leaves runtime startup/tool validation to the post-install doctor smoke check. Generated MCP configs invoke `mempalace-mcp` without arguments for all supported agent targets.
+
+Each MemPalace init/mine command has a timeout controlled by `AGENTIC_MEMPALACE_TIMEOUT_SECONDS` and defaults to `60` seconds. Timeouts are reported as warnings and do not block MCP config generation.