pentesting 0.92.3 → 0.92.5

package/ARCHITECTURE.md

@@ -0,0 +1,409 @@
+# Architecture
+
+This document reflects the current `main` branch architecture. It is the single,
+detailed reference for how the runtime is structured; the [README](README.md)
+stays intentionally short and usage-focused.
+
+> **Engine vs product.** The orchestration engine is **`builder`** — a
+> general-purpose, local-first Rust agent runtime. **`pentesting`** is the
+> published, security-focused distribution of that same engine: the npm package
+> and the command you run. They share one binary; `pentesting` is `builder` with
+> a security skill set and banner. The model proposes actions, while the Rust
+> runtime owns routing, tool policy, evidence capture, verification, and
+> completion adjudication.
+
+## Design Pillars
+
+- **Runtime-Owned Adjudication** — Model output is a *candidate* until a runtime
+  acceptance-gate lattice verifies and closes the task (outcome: complete /
+  replan / blocked).
+- **Local-First State** — Runtime state and a markdown knowledge graph live on
+  disk. No external storage service.
+- **Weak-Model Hardening** — Rust-enforced classifiers, validators, and
+  self-reviews guard against hallucination.
+- **Lineage & Horizons** — Run lineage, objective IDs, and horizon-aware memory
+  reuse, all in local state.
+- **Policy-Gated Tools** — `Allow/Deny/Confirm` gates shell, file, and network
+  access (policy-based today; OS sandboxing is roadmap).
+- **Intelligent Queuing** — Queued inputs are deduplicated and prioritized live;
+  obsolete tasks are preempted, not FIFO-replayed.
+- **Lab Session Multiplexing** — `shell-listener` runs multiple authorized TCP
+  sessions with per-session routing and PTY upgrades.
+- **Dynamic Agent Profiles** — No fixed persona: the runtime *derives* a profile
+  per request from the prompt and can overlay a named autonomy profile, driving
+  tool scope, phase, and memory weighting.
+- **Ebbinghaus-Inspired Memory** — Memories carry a *strength* that fades like
+  human memory and reinforces on recall. Faded notes are de-referenced, never
+  destroyed.
+- **Git-Backed Rewind** — Working-tree checkpoint/restore keeps autonomous edits
+  reversible.
+
+## Runtime Flow
+
+```mermaid
+flowchart TD
+    U[User request] --> CLI[builder_main CLI / TUI]
+    CLI --> API[builder_api facade]
+    API --> APP[builder_app coordination]
+    APP --> CLS[Intent classifier]
+    CLS --> STR[Dynamic profile + execution strategy]
+    STR --> AG[Active agent]
+    AG --> DEC{Delegate?}
+    DEC -- no --> TOOLS[Policy-gated tools]
+    DEC -- yes --> SUB[Subagent task packet]
+    SUB --> TOOLS
+    TOOLS --> EV[Evidence + state cards]
+    EV --> VER[Verification gates]
+    VER --> DONE[Completion adjudication]
+    DONE --> STORE[Local runtime state]
+    STORE --> CTX[Next-turn context]
+    CTX --> APP
+```
+
+Plain view:
+
+```text
+user input
+  -> CLI / interactive prompt loop
+  -> BuilderAPI facade
+  -> BuilderApp classification and strategy
+  -> active agent or delegated subagent
+  -> policy-gated tool execution
+  -> evidence, workflow state, and verification records
+  -> completion adjudication
+  -> local state and next-turn context
+```
+
+Builder is a **domain-neutral** runtime with a security focus. Development,
+pentesting, CTF, audit, and release work layer in via skills — never baked into
+the core.
+
+## Dynamic Agent Profiles
+
+There is no fixed persona. The runtime derives a profile per request, optionally
+overlays a named autonomy profile, then reuses tool scope, phase, and memory
+weighting.
+
+```mermaid
+flowchart LR
+    R[Request] --> GEN["Derive<br/>dynamic profile"]
+    GEN --> REC["Overlay<br/>named autonomy profile"]
+    REC --> USE["Reuse<br/>tool scope · phase · memory weight"]
+```
+
+Request to closure:
+
+```mermaid
+flowchart TD
+    U[User request] --> C[Intent classifier]
+    C --> P[Dynamic profile<br/>task shape + tool scope + rigor]
+    P --> R[Runtime router]
+    R --> A[Active agent]
+    A --> T{Need delegation?}
+    T -- no --> O[Tool execution]
+    T -- yes --> D[Agent tool]
+    D --> CO[coordinator]
+    D --> I[investigator]
+    D --> OP[operator]
+    D --> RV[reviewer]
+    D --> V[verifier]
+    D --> W[report-writer]
+    CO --> O
+    I --> O
+    OP --> O
+    RV --> O
+    V --> O
+    W --> O
+    O --> G[Completion gates]
+    G --> M[Memory + artifacts]
+    M --> U
+```
+
+## Agent Team
+
+The core agent team is domain-neutral. Each agent ships as a markdown persona
+definition under `crates/builder_repo/src/agents/`.
+
+| Agent | Default role | Runtime profile |
+| --- | --- | --- |
+| `builder` | Hands-on implementation, refactoring, local file changes, tests | Implement + broad local write |
+| `planner` | Implementation plans and risk breakdowns | Plan + read-only |
+| `researcher` | Read-only codebase and reference research | Investigate + read-only |
+| `coordinator` | Splits broad work into owned packets and consolidates results | Coordinate + broad local write |
+| `investigator` | Evidence gathering across code, logs, commands, APIs, and behavior | Investigate + shell diagnostics |
+| `operator` | Builds, tests, packaging, service startup, and runtime workflows | Implement + broad local write |
+| `reviewer` | Findings-first technical review | Review + strict read-only |
+| `verifier` | Reproduction, build/test proof, and completion claim checks | Verify + strict read-only |
+| `report-writer` | Reports, handoffs, release notes, and reproducibility records | Implement + bounded write |
+
+> Distinct tool-scope is runtime-enforced for `builder`, `planner`, and
+> `researcher`; the remaining personas share a task-shaped generic profile
+> (read-only when the task shape is review/verify, broad local write otherwise)
+> and differ by their prompt instructions.
+
+## Named Autonomy Profiles
+
+Optionally pin the top-level profile (`autonomy_profile = "ctf-competition"`);
+leave unset for classifier-driven defaults. Delegated subagent contracts stay
+intact. Defined in `crates/builder_domain/src/autonomy_profile.rs`.
+
+| Profile | Purpose |
+| --- | --- |
+| `general-agent` | Broad autonomous local orchestration for mixed tasks |
+| `local-builder` | Hands-on implementation with fresh evidence retrieval |
+| `ctf-competition` | Competition/lab workflow backed by `ctf-competition` and `pentesting-methodology` skills |
+| `enterprise-review` | Strict, review-heavy profile with read-only dynamic scope |
+
+## Engagement Metadata
+
+Runs can attach typed engagement context — scope, phase, tags, and standard refs
+(PTES, MITRE ATT&CK, OWASP, CWE/CAPEC, NIST CSF, CIS Controls) — to workflow
+metadata. `/workflow report` exports it as a Markdown handoff.
+
+## Memory & Knowledge
+
+Local-first and split across two complementary layers, no vector DB, no cloud:
+
+- **Conversation memories** — facts/preferences/gotchas distilled from sessions,
+  persisted in local runtime state and recalled into each prompt by hybrid
+  retrieval. These carry a *strength* that fades like human memory, so the store
+  stays sharp instead of rotting.
+- **Knowledge vault** — an optional Obsidian-style set of markdown notes under
+  `.builder/knowledge` (wiki-links, backlinks, tags). The agent reads it on every
+  turn and grows it with the `write` tool; it is never auto-deleted.
+
+Both layers feed the same strength-weighted hybrid retrieval.
+
+**Storage** — Ebbinghaus lifecycle (decay · reinforce · floor, never deleted):
+
+```mermaid
+flowchart TD
+    N[New memory] --> S["strength = quality × recall × e^-λ·age"]
+    S --> U{recalled?}
+    U -- yes --> RE[reinforce ↑ · reset age]
+    U -- no --> D[decay over time]
+    RE --> S
+    D --> F{below floor?}
+    F -- no --> S
+    F -- yes --> AR[de-reference: archive / tombstone]
+    AR -. recoverable on disk .-> N
+```
+
+Kinds fade at different speeds (procedural outlives episodic); bi-temporal
+`event_time` vs `ingestion_time` lets newer facts supersede stale ones.
+
+**Retrieval** — hybrid fuse, strength-weighted, read-only:
+
+```mermaid
+flowchart LR
+    Q[Query] --> L[Lexical]
+    Q --> SE[Semantic]
+    Q --> G[Graph]
+    L --> RRF[RRF fuse]
+    SE --> RRF
+    G --> RRF
+    RRF --> RR[rerank: phase · recency · task]
+    RR --> W[weight by strength]
+    W --> P[Prompt context]
+```
+
+Faded, private, or unsafe memories are held back from the prompt. Lookups never
+write — reinforce/archive/supersede are explicit, never search side effects.
+
+## Storage Strategy
+
+Builder uses one operational storage strategy: local on-disk runtime state plus
+markdown-native knowledge artifacts.
+
+```mermaid
+flowchart LR
+    W[Workspace files] --> AD[Source adapters]
+    S[Skills] --> AD
+    M[Conversation memories] --> AD
+    N[Markdown notes] --> AD
+    AD --> IDX[Local lexical + semantic + graph index]
+    IDX --> RR[Contextual reranker]
+    RR --> PC[Prompt context]
+    PC --> RUN[Agent run]
+    RUN --> LS[.builder local state]
+    RUN --> ART[Local artifacts and reports]
+```
+
+Key invariants:
+
+- Runtime state is local-first and does not require an external data service.
+- The markdown knowledge graph is derived from local facts: notes, skills,
+  conversation memory, wiki-links, backlinks, and run artifacts.
+- Graph data is a derived retrieval view, not a second source of truth.
+- Workflow runs, evidence, state cards, memories, and large-output artifacts
+  persist through local repositories.
+- Domain methods such as development, CTF practice, pentesting methodology,
+  audits, and release work live in skills and task instructions; they do not
+  change the core runtime identity.
+
+## Crate Map
+
+| Layer | Crates | Responsibility |
+| --- | --- | --- |
+| Interaction | `builder_main`, `builder_ratatui`, `builder_select`, `builder_markdown_stream` | CLI, TUI, prompt flow, rendering, selector fallback |
+| Facade | `builder_api` | Thin application boundary used by entry points |
+| Coordination | `builder_app` | classification, routing, execution strategy, orchestration, completion gates |
+| Contracts | `builder_domain` | typed IDs, tools, workflow records, engagement metadata, policies |
+| Capabilities | `builder_services` | tool services, auth, provider support, file/search/shell/fetch operations |
+| Persistence | `builder_repo`, `builder_provider_repo` | local repositories, provider catalog, chat repository |
+| Knowledge | `builder_knowledge`, `builder_workspace_index`, `builder_embed` | markdown note adapters, graph parsing, hybrid retrieval, local semantic scoring |
+| Infrastructure | `builder_config`, `builder_infra`, `builder_fs`, `builder_walker` | config, environment, filesystem, process/runtime helpers |
+| Support | `builder_display`, `builder_stream`, `builder_template`, `builder_json_repair`, `builder_snaps`, `builder_brand`, `builder_tracker`, `builder_test_kit`, `builder_tool_macros` | formatting, streaming, templates, JSON repair, snapshots, branding/theming, version tracking, tests, tool macros |
+
+## Tool Surface
+
+The runtime tool catalog is file, shell, network-fetch, planning, skill, todo,
+and delegation oriented. Core tools:
+
+- `read`, `write`, `patch`, `multi_patch`, `undo`, `remove`
+- `fs_search`, `sem_search`
+- `shell`, `fetch`
+- `plan`, `skill`, `todo_read`, `todo_write`
+- `task` and dynamically registered agent tools
+
+The full catalog (`builder_domain/src/tools/catalog.rs`) also includes web
+search, memory, verification primitives (flag check, best-of-N verify, finding),
+session/process control, and compaction tools. Direct raw storage-query tooling
+is not part of the active runtime surface.
+
+## Verification And Completion
+
+Completion is runtime-owned:
+
+```text
+candidate answer
+  -> evidence check
+  -> verification record
+  -> acceptance-gate check
+  -> adjudication
+  -> complete / replan / blocked
+```
+
+The key rule is that a model response is not considered done until the runtime
+has enough recorded evidence to close the task.
+
+## Distribution — single source, two surfaces
+
+Pentesting and Builder share the **same Rust runtime binary**. The `pentesting`
+npm package is a thin distribution facade:
+
+```text
+npm install -g pentesting
+         │
+         ▼
+  pentesting CLI (Node.js shim)
+         │  resolves or downloads the matching Builder release asset
+         ▼
+  Builder binary (Rust)  ← single runtime engine
+         │  PENTESTING_PRODUCT_NAME=pentesting
+         ▼
+  Interactive TUI with "pentesting" banner
+```
+
+- The npm package installs a launcher, **not** a second agent runtime.
+- It resolves or downloads the correct release asset from
+  `agnusdei1207/pentesting-public`.
+- It forwards arguments directly into the Rust binary — no command translation
+  or compatibility shims.
+- If a change would add orchestration, memory, or prompt logic into the npm
+  layer, that change belongs upstream in the Rust runtime.
+
+## Supported Runtime Targets
+
+The npm launcher currently resolves managed native release assets for the
+targets below. Other operating systems can run the Docker image or use
+`PENTESTING_BIN` to point at a locally built compatible binary.
+
+| OS | CPU | Release asset |
+| --- | --- | --- |
+| Linux | x64 | `pentesting-x86_64-unknown-linux-musl` |
+| Android | arm64 | `pentesting-aarch64-linux-android` |
+
+`/update` (and the npm postinstall) resolves the matching asset for the current
+supported OS/CPU target from `agnusdei1207/pentesting-public`.
+
+## Configuration
+
+Pentesting reads a user-global config from `~/.pentesting/.pentesting.toml`,
+overridden by project-local `.pentesting.toml` files discovered by walking up
+from the working directory. The storage config is intentionally small:
+
+```toml
+[storage]
+backend = "local"                            # Local md/fs runtime state
+```
+
+The same shape is represented in `builder.schema.json`, `.pentesting.toml`, and
+the interactive `/config` UI.
+
+Environment variables use the `PENTESTING_` prefix, with `__` for nested keys —
+e.g. `PENTESTING_SESSION__MODEL_ID=...`. Set `PENTESTING_CONFIG` to override the
+global config directory.
+
+| Variable | Description |
+| --- | --- |
+| `PENTESTING_BIN` | Use an already-installed Builder binary instead of the managed download. |
+| `PENTESTING_PRODUCT_NAME` | Runtime banner label. The `pentesting` launcher sets this to `pentesting` automatically. |
+| `PENTESTING_REPO` | Override the public release repo used for binary downloads. Defaults to `agnusdei1207/pentesting-public`. |
+| `PENTESTING_SKIP_DOWNLOAD` | Skip the postinstall binary download. Useful in CI or when `PENTESTING_BIN` will be provided later. |
+| `PENTESTING_CONFIG` | Override the global config directory. |
+
+### Backward compatibility — `builder` ↔ `pentesting`
+
+The runtime engine is still `builder` under the hood, so legacy names keep
+working. Use whichever you like; the `PENTESTING_*` form wins when both are set.
+
+| Surface | Canonical | Legacy (still accepted) |
+| :--- | :--- | :--- |
+| Env vars | `PENTESTING_*` | `BUILDER_*` |
+| Config-dir override | `PENTESTING_CONFIG` | `BUILDER_CONFIG` |
+| Global config file | `~/.pentesting/.pentesting.toml` | `~/.builder/.builder.toml`, `~/builder/.builder.toml` |
+| Project config file | `.pentesting.toml` | `.builder.toml` |
+
+## Interactive Commands
+
+Inside an interactive session, these commands inspect and drive runtime state
+(`/help` lists the full set):
+
+```text
+/status        Show the current run phase, active tasks, gates, hooks, and budget signals
+/workflow      Show the current focus and recent workflow steps for the active conversation
+/workflow report
+               Export the active run, engagement metadata, evidence, and large outputs to Markdown
+/context       Show recent context-budget snapshots for the current conversation
+/memory        Show stored conversation memories for the current conversation
+/tools         List the currently available tools and schemas
+/agent         Switch the active agent
+/conversation  Browse conversations for the active workspace
+/goal <task>   Set the active goal
+/auto          Toggle autonomous mode for the current goal
+/update        Download and apply the latest public release asset for supported native targets
+/help          Show all commands
+/exit          Quit
+```
+
+## Security Domain Skills
+
+The `ctf-competition` and `pentesting-methodology` skills map authorized
+assessments to standard frameworks:
+
+- **PTES** (Penetration Testing Execution Standard)
+- **MITRE ATT&CK** tactics and techniques
+- **OWASP** Top 10 and Testing Guide
+- **CWE/CAPEC** weakness and attack pattern catalogs
+- **NIST CSF** and **CIS Controls**
+
+### Shell listener for authorized labs
+
+```bash
+pentesting shell-listener --bind 127.0.0.1 --port 4444
+```
+
+Manages multiple accepted TCP sessions with per-session routing, buffered
+output, raw byte logging, and PTY-upgrade helpers. Bound to loopback by default;
+`--allow-remote` is an explicit opt-in gate.

package/LICENSE

@@ -0,0 +1,28 @@
+MIT License
+
+Copyright (c) 2026 agnusdei1207
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+---
+
+Note: This MIT license covers the published `pentesting` npm wrapper (the
+launcher in `bin/` and `lib/` plus its install scripts). The Builder runtime
+engine that the wrapper downloads and executes is a separate, proprietary
+component and is not licensed under these terms.

package/README.md

@@ -13,24 +13,6 @@
 
 ---
 
-## 🎹 From the Developer
-
-<div align="center">
-  <img src="public/image.png" alt="Chopin Ballade No.4" width="600" />
-</div>
-
-<br/>
-
-> "I believe playing the piano is also a form of orchestration."
->
-> The harmony of polyphony — multiple voices — and homophony — a single melodic line.
->
-> Each voice sings its most beautiful song from its own place, yet when combined, they create one grand, beautiful melody. I believe this structure is no different from AI agents.
->
-> — *agnusdei1207*
-
----
-
 ## 🚀 Quick Start
 
 ```bash
@@ -59,7 +41,7 @@ pentesting shell-listener --bind 127.0.0.1 --port 4444   # Authorized lab listen
 pentesting --version
 ```
 
-Inside a session, `/help` lists every command and `/update` pulls the latest release for your OS/CPU.
+Inside a session, `/help` lists every command and `/update` pulls the latest release for supported native targets.
 
 ---
 
@@ -83,3 +65,21 @@ Environment variables use the `PENTESTING_` prefix (`__` for nested keys, e.g. `
 * [`ARCHITECTURE.md`](ARCHITECTURE.md) — Runtime flow, agent team, memory model, crate map, tool surface, and supported targets.
 * [Public site](https://agnusdei1207.github.io/pentesting-public/) — Landing page and public runtime entry surface.
 * [`compose.yaml`](https://github.com/agnusdei1207/pentesting-public) — Docker Compose facade for pentesting sessions.
+
+---
+
+## 🎹 From the Developer
+
+<div align="center">
+  <img src="https://github.com/user-attachments/assets/abe73474-f27b-4536-b358-fedef1e461f0" alt="Chopin Ballade No.4" width="600" />
+</div>
+
+<br/>
+
+> "I believe playing the piano is also a form of orchestration."
+>
+> The harmony of polyphony — multiple voices — and homophony — a single melodic line.
+>
+> Each voice sings its most beautiful song from its own place, yet when combined, they create one grand, beautiful melody. I believe this structure is no different from AI agents.
+>
+> — *agnusdei1207*

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pentesting",
-  "version": "0.92.3",
-  "builderReleaseTag": "v0.92.3",
+  "version": "0.92.5",
+  "builderReleaseTag": "v0.92.5",
   "description": "pentesting — security-focused agent runtime (internal engine: builder). Thin npm facade that downloads the managed Builder binary and forwards arguments.",
   "license": "MIT",
   "author": "agnusdei1207",
@@ -13,7 +13,9 @@
     "bin",
     "lib",
     "scripts/postinstall.mjs",
-    "README.md"
+    "README.md",
+    "ARCHITECTURE.md",
+    "pentesting-logo.svg"
   ],
   "engines": {
     "node": ">=18.18.0"
@@ -46,9 +48,28 @@
   "scripts": {
     "postinstall": "node ./scripts/postinstall.mjs",
     "prepublishOnly": "npm run verify",
+    "consistency": "bash scripts/check-project-consistency.sh",
+    "audit": "bash scripts/audit-project.sh",
     "test": "node --test tests/*.test.mjs",
     "preflight:local": "bash scripts/preflight-local.sh",
-    "verify": "npm run preflight:local && npm run test",
+    "verify": "npm run consistency && npm run test",
+    "pentesting:help": "bash scripts/pentesting-release-help.sh",
+    "pentesting:status": "bash scripts/pentesting-release-status.sh",
+    "pentesting:test": "npm run test",
+    "pentesting:verify": "npm run verify",
+    "pentesting:pack:dry-run": "npm pack --dry-run",
+    "pentesting:check": "bash scripts/check-pentesting-package.sh",
+    "pentesting:publish": "bash scripts/publish-pentesting-package.sh",
+    "pentesting:publish:dry-run": "DRY_RUN=true bash scripts/publish-pentesting-package.sh",
+    "release:npm": "bash scripts/publish-pentesting-package.sh patch",
+    "release:npm:minor": "bash scripts/publish-pentesting-package.sh minor",
+    "release:npm:major": "bash scripts/publish-pentesting-package.sh major",
+    "release:npm:dry": "DRY_RUN=true bash scripts/publish-pentesting-package.sh patch",
+    "release:npm:minor:dry": "DRY_RUN=true bash scripts/publish-pentesting-package.sh minor",
+    "release:npm:major:dry": "DRY_RUN=true bash scripts/publish-pentesting-package.sh major",
+    "public:sync": "bash scripts/sync-public-repo.sh",
+    "public:mirror-release": "bash scripts/mirror-public-release.sh",
+    "release:backfill": "bash scripts/backfill-release-local.sh",
     "check": "sh -c 'npm run docker:build && docker run -it --rm -v builder-workspace:/workspace -e ANTHROPIC_BASE_URL -e ANTHROPIC_AUTH_TOKEN -e ANTHROPIC_MODEL -e ANTHROPIC_API_KEY -e MINIMAX_API_KEY -e OPENAI_API_KEY -e OPENAI_BASE_URL -e GEMINI_API_KEY -e DEEPSEEK_API_KEY agnusdei1207/pentesting:latest'",
     "docker:build": "(docker image inspect agnusdei1207/pentesting-build-base:1.96 >/dev/null 2>&1 && docker image inspect agnusdei1207/pentesting-runtime-base:26.04 >/dev/null 2>&1 || npm run docker:base:build) && docker build --build-arg APP_VERSION=$(git describe --tags --abbrev=0 2>/dev/null || echo dev) -t agnusdei1207/pentesting:latest .",
     "docker:base:build": "docker build -t agnusdei1207/pentesting-build-base:1.96 -f docker/build-base.Dockerfile . && docker build -t agnusdei1207/pentesting-runtime-base:26.04 -f docker/runtime-base.Dockerfile .",

package/pentesting-logo.svg

@@ -0,0 +1,13 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true">
+  <g
+    fill="none"
+    stroke="#00d4aa"
+    stroke-linecap="round"
+    stroke-linejoin="round"
+    stroke-width="1.5"
+  >
+    <path d="m7 7l1.227 1.057C8.742 8.502 9 8.724 9 9s-.258.498-.773.943L7 11" />
+    <path d="M11 11h3" />
+    <path d="M12 21c3.75 0 5.625 0 6.939-.955a5 5 0 0 0 1.106-1.106C21 17.625 21 15.749 21 12s0-5.625-.955-6.939a5 5 0 0 0-1.106-1.106C17.625 3 15.749 3 12 3s-5.625 0-6.939.955A5 5 0 0 0 3.955 5.06C3 6.375 3 8.251 3 12s0 5.625.955 6.939a5 5 0 0 0 1.106 1.106C6.375 21 8.251 21 12 21" />
+  </g>
+</svg>