cue-ai 0.3.0

package/resources/skills/skills/colony/colony-prompts/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: colony-prompts
+description: >-
+  Use when user says "Colony prompts" or "Colony handoff". Prompt boundaries, task readiness, handoff wording for Colony.
+---
+
+# Colony Planner Prompts
+
+Reusable workflow for turning "let's port feature X into colony" into a set
+of parallel-safe agent prompts that drop straight into the colony-hivemind
+planner UI. Each prompt is a self-contained instruction sheet for one agent
+running in its own `agent/*` worktree.
+
+## When to use
+
+Direct triggers:
+- "colony:prompts", "/colony-prompts"
+- "generate N agent prompts for ..."
+- "add to the recodee/colony planner"
+- "split this into parallel agent prompts"
+- "wave plan for colony"
+- "scaffold prompts for the colony planner"
+
+Indirect — implies this skill:
+- User just got a feature-integration recommendation (e.g. "best of mempalace
+  → colony") and says "do a plan with N agents that can run in parallel"
+- "Can you add prompts so the planner can dispatch this work?"
+
+## When NOT to use
+
+- Single-agent work, single-file fix, typo, version bump.
+- The user wants an OpenSpec change but no agent dispatch.
+- The user wants a doc, not executable agent prompts.
+- The work fits one `T0` lane — adding 15 prompts for a one-line fix is noise.
+
+## Canonical paths
+
+- Planner prompts directory:
+  `/home/deadpool/Documents/recodee/apps/frontend/public/colony-planner/prompts/`
+- File name shape: `agent-NN.md` (zero-padded only when ≤ 99; flat decimal
+  after that — match what's already there).
+- Status marker (read by the planner UI):
+  `<!-- colony-planner-status: todo -->` flips to `done` only when the agent
+  has merged proof.
+
+The planner page reads these markers and groups prompts into waves based on
+the order they're filed. The planner itself is at
+`/home/deadpool/Documents/recodee/apps/frontend/app/(app)/colony-hivemind/planner/`.
+
+## Required prompt format
+
+Every prompt is a single markdown file with exactly this shape:
+
+```markdown
+<!-- colony-planner-status: todo -->
+
+You are working in /home/deadpool/Documents/recodee/colony.
+
+Goal: <one-sentence outcome>.
+
+Read:
+- <source files this agent must understand before editing>
+- <existing-feature siblings for shape>
+- <the upstream OpenSpec change/context if any>
+
+Implement:
+- <concrete file path 1 + what to add/change>
+- <concrete file path 2 + ...>
+- <explicit DO-NOT lines for files claimed by sibling agents>
+
+Constraints:
+- File ownership: <exact paths this agent owns this wave>.
+- <invariants — perf budget, backward-compat, no-network, etc.>
+- <CLAUDE.md rule citations where relevant>
+
+Proof:
+- <pnpm filter test command>
+- <typecheck/build command>
+- <git diff <owned-paths>>
+```
+
+Do not invent extra sections. The planner UI parses this shape literally.
+
+## Numbering
+
+1. Read the directory once: list `agent-*.md` and find the highest number.
+2. Continue from `next = highest + 1`.
+3. Numbers are global across all themes — never reuse, never renumber.
+4. The just-finished mempalace track lives at 230–244. Pick after the
+   current highest (verify before writing — other sessions may have added
+   prompts since).
+
+## Parallel-safety model
+
+The planner can dispatch every prompt in a wave concurrently, so within a
+wave, no two prompts may write the same file. Across waves, dependencies
+are allowed.
+
+Concrete rules every prompt must respect:
+
+- **Each agent claims a disjoint file set.** State the claim explicitly in
+  the `Constraints` section under "File ownership".
+- **No two agents in the same wave touch the same file.** If a registration
+  file (e.g. `apps/mcp-server/src/server.ts`, `packages/hooks/src/index.ts`)
+  has to be edited by multiple features, schedule those edits in serial
+  waves with one owner per wave.
+- **New files > shared files.** Prefer `packages/<pkg>/src/handlers/foo.ts`
+  (new) over editing `packages/<pkg>/src/index.ts` (shared) in the same
+  wave.
+- **Pure modules first, wiring last.** Pure logic (scorers, validators,
+  reducers) goes in early waves. Pipeline/registration wiring goes in the
+  last impl wave before the conformance gate.
+
+## Wave layout heuristic
+
+For an N-agent feature port (typical N = 10–20), default to 5 waves:
+
+| Wave | Purpose | Sample agents |
+|---|---|---|
+| W1 | Capability context, umbrella OpenSpec change, package skeletons | 3–4 |
+| W2 | Per-feature isolated implementations (pure modules, new files) | 3–5 |
+| W3 | Schema migrations, MCP tool registration, config schema, hook exports | 3–5 |
+| W4 | Wiring (search pipelines, MCP handler args, sanitizer hooks) | 2–3 |
+| W5 | Conformance gate (single sequential agent) | 1 |
+
+The gate prompt is always last and always sequential. Model it on
+`scripts/check-symphony-conformance.ts` — the colony repo already has the
+pattern.
+
+## Required content per prompt
+
+- **Goal** — one verifiable outcome. Not "improve search" but "wire
+  applyTimeDecay into search/index.ts gated by `search.timeDecay.enabled`".
+- **Read** — the actual file paths the agent must read first. Include the
+  upstream source file under `examples/<thing>/` when porting.
+- **Implement** — concrete file paths. Every line is an action. Include
+  explicit `DO NOT touch <file>` lines for any shared file claimed by a
+  sibling agent in the same wave.
+- **Constraints** — `File ownership:` line listing exact paths, then the
+  invariants (perf budgets, backward-compat, local-first, no network calls,
+  CLAUDE.md rule numbers).
+- **Proof** — exact commands. At minimum: one `pnpm --filter <pkg> test ...`
+  matching the agent's owned tests; one typecheck or build; one
+  `git diff <owned-paths>`.
+
+## Hard guardrails (apply to every prompt)
+
+These come straight from `colony/CLAUDE.md` and `recodee/CLAUDE.md`:
+
+1. **Worktree discipline.** Every agent works inside an `agent/*` worktree
+   started via `gx branch start "<task>" "claude-code"` (or `bash
+   scripts/agent-branch-start.sh ...`). Never edit on `main`.
+2. **Read-before-edit.** The prompt's `Read` block must list every file the
+   agent will edit; Claude Code rejects `Edit` on unread files.
+3. **Compression-first.** No prompt may add a write path that bypasses
+   `@colony/compress` (rule #2). All persisted prose goes through the
+   `MemoryStore` facade. Reject ports that demand verbatim storage.
+4. **No technical-token compression.** Code blocks, URLs, file paths, shell
+   commands, version numbers, dates, numeric literals stay byte-for-byte
+   (rule #3). Reranker/sanitizer prompts that quote user content must
+   preserve these.
+5. **Hot-path budget.** Hook handlers stay under 150 ms p95 (rule #6). The
+   prompt must state the budget when the agent touches `packages/hooks/`.
+6. **No default network calls.** Local-first by default; remote providers
+   are BYOK opt-in (rule #8). State this explicitly when adding embedder or
+   reranker code.
+7. **Migrations are forward-only.** New SQL files are numbered, idempotent,
+   and never destructive on re-run (rule #5 in storage README).
+8. **Locked files.** `rust/codex-lb-runtime/src/main.rs` is integrator-only
+   per recodee/CLAUDE.md. `frontend/src/utils/account-working.ts` is
+   regression-locked. Reject prompts that touch them without explicit
+   integrator override.
+9. **Progressive disclosure in MCP.** New MCP tools return compact
+   list shapes; full bodies via a follow-up fetch (rule #5 in colony's
+   CLAUDE.md). State this when registering tools.
+10. **Conformance gate is non-bypassable.** The final prompt runs a script
+    that walks tasks.md checkboxes and exits 1 if any required item lacks
+    a `task_proof_record`. No manual checkmarks.
+
+## Workflow
+
+When the user invokes this skill:
+
+1. **Locate the planner.** Confirm
+   `/home/deadpool/Documents/recodee/apps/frontend/public/colony-planner/prompts/`
+   exists. List existing prompts to find the next number.
+2. **Read the source.** If the user references `examples/<thing>/`, read
+   the README, CLAUDE.md, MISSION.md, ROADMAP.md (whichever exist) before
+   proposing a breakdown. Do not skim — the breakdown depends on
+   understanding what's actually portable.
+3. **Propose a breakdown** in the chat first: list the candidate features,
+   the ones to reject, and the ones to adopt. Group adopted features into
+   waves with file-ownership invariants. Surface conflicts before writing
+   files.
+4. **Get a quick confirm or proceed** — if the user already said "without
+   stopping" or "just do it", continue.
+5. **Write all N prompts** in parallel `Write` tool calls (they're
+   path-disjoint). Each file goes to
+   `apps/frontend/public/colony-planner/prompts/agent-NN.md`.
+6. **Verify** with one `ls` confirming all files landed and sizes are
+   reasonable (1–3 KB each — much larger means the prompt is bloated).
+7. **Reply with a wave map table** and the file-ownership invariants list.
+   Do not paste the prompts back — they're durable on disk.
+
+## Working state
+
+If interrupted, post a Colony note:
+
+```
+task_post kind=note
+content="branch=<branch>; task=colony-prompts-<theme>;
+blocker=<blocker>; next=write agents NN-MM;
+evidence=apps/frontend/public/colony-planner/prompts/agent-NN.md"
+```
+
+Hand off the unfinished number range to the next agent rather than
+overlapping numbers.
+
+## Reference example
+
+The mempalace integration set (agents 230–244, written 2026-05-09) is the
+canonical reference for this skill. 15 agents, 5 waves, file-ownership
+invariants in every prompt, conformance gate at 244. Read any of those
+prompts to see the exact tone and density expected.

package/resources/skills/skills/content/doc/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/resources/skills/skills/content/doc/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: "doc"
+description: >-
+  Use when user says "write documentation", "make a DOCX", or "create a doc". Document structure, formatting, export.
+---
+
+
+# DOCX Skill
+
+## When to use
+- Read or review DOCX content where layout matters (tables, diagrams, pagination).
+- Create or edit DOCX files with professional formatting.
+- Validate visual layout before delivery.
+
+## Workflow
+1. Prefer visual review (layout, tables, diagrams).
+   - If `soffice` and `pdftoppm` are available, convert DOCX -> PDF -> PNGs.
+   - Or use `scripts/render_docx.py` (requires `pdf2image` and Poppler).
+   - If these tools are missing, install them or ask the user to review rendered pages locally.
+2. Use `python-docx` for edits and structured creation (headings, styles, tables, lists).
+3. After each meaningful change, re-render and inspect the pages.
+4. If visual review is not possible, extract text with `python-docx` as a fallback and call out layout risk.
+5. Keep intermediate outputs organized and clean up after final approval.
+
+## Temp and output conventions
+- Use `tmp/docs/` for intermediate files; delete when done.
+- Write final artifacts under `output/doc/` when working in this repo.
+- Keep filenames stable and descriptive.
+
+## Dependencies (install if missing)
+Prefer `uv` for dependency management.
+
+Python packages:
+```
+uv pip install python-docx pdf2image
+```
+If `uv` is unavailable:
+```
+python3 -m pip install python-docx pdf2image
+```
+System tools (for rendering):
+```
+# macOS (Homebrew)
+brew install libreoffice poppler
+
+# Ubuntu/Debian
+sudo apt-get install -y libreoffice poppler-utils
+```
+
+If installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally.
+
+## Environment
+No required environment variables.
+
+## Rendering commands
+DOCX -> PDF:
+```
+soffice -env:UserInstallation=file:///tmp/lo_profile_$$ --headless --convert-to pdf --outdir $OUTDIR $INPUT_DOCX
+```
+
+PDF -> PNGs:
+```
+pdftoppm -png $OUTDIR/$BASENAME.pdf $OUTDIR/$BASENAME
+```
+
+Bundled helper:
+```
+python3 scripts/render_docx.py /path/to/file.docx --output_dir /tmp/docx_pages
+```
+
+## Quality expectations
+- Deliver a client-ready document: consistent typography, spacing, margins, and clear hierarchy.
+- Avoid formatting defects: clipped/overlapping text, broken tables, unreadable characters, or default-template styling.
+- Charts, tables, and visuals must be legible in rendered pages with correct alignment.
+- Use ASCII hyphens only. Avoid U+2011 (non-breaking hyphen) and other Unicode dashes.
+- Citations and references must be human-readable; never leave tool tokens or placeholder strings.
+
+## Final checks
+- Re-render and inspect every page at 100% zoom before final delivery.
+- Fix any spacing, alignment, or pagination issues and repeat the render loop.
+- Confirm there are no leftovers (temp files, duplicate renders) unless the user asks to keep them.

package/resources/skills/skills/content/doc/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Word Docs"
+  short_description: "Edit and review docx files"
+  icon_small: "./assets/doc-small.svg"
+  icon_large: "./assets/doc.png"
+  default_prompt: "Edit or review this .docx file and return the updated file plus a concise change summary."

package/resources/skills/skills/content/doc/assets/doc-small.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" viewBox="0 0 16 16">
+  <path fill="currentColor" d="M2.468 10.467V5.533c0-.55 0-.997.029-1.357.03-.366.093-.69.247-.992l.097-.175a2.54 2.54 0 0 1 1.01-.932l.114-.053a2.77 2.77 0 0 1 .878-.194c.36-.03.806-.029 1.357-.029h2.808c.464 0 .783-.003 1.088.07l.192.055c.189.061.37.145.54.249l.099.064c.226.158.433.368.72.655l.792.792.227.23c.21.213.37.388.493.59l.097.173c.09.177.16.365.206.558l.024.116c.048.272.046.567.046.973v4.14c0 .552 0 .998-.029 1.358-.026.32-.078.61-.194.878l-.053.114a2.531 2.531 0 0 1-.932 1.009l-.175.097c-.301.154-.626.217-.992.247-.36.03-.806.03-1.357.03H6.2c-.551 0-.997 0-1.357-.03a2.761 2.761 0 0 1-.878-.193l-.114-.054a2.533 2.533 0 0 1-1.01-.932l-.097-.174c-.154-.301-.217-.626-.247-.992-.03-.36-.029-.806-.029-1.357ZM8.666 8.8l.108.011a.532.532 0 0 1 0 1.042l-.108.011H6A.532.532 0 0 1 6 8.8h2.666ZM10 6.135l.107.01a.532.532 0 0 1 0 1.043L10 7.199H6a.532.532 0 0 1 0-1.064h4Zm-6.468 4.332c0 .569 0 .963.026 1.27.024.3.07.47.134.596l.057.101c.14.23.343.418.585.54l.104.045c.115.041.266.072.492.09.307.025.701.026 1.27.026h3.6c.569 0 .964 0 1.27-.026.3-.024.47-.07.596-.134l.101-.057c.23-.141.418-.343.54-.585l.046-.104a1.94 1.94 0 0 0 .09-.492 18 18 0 0 0 .025-1.27V6.326c0-.386-.002-.579-.019-.716l-.022-.124a1.464 1.464 0 0 0-.12-.324l-.055-.1a1.433 1.433 0 0 0-.178-.226l-.387-.397-.792-.792a6.893 6.893 0 0 0-.52-.493l-.103-.072a1.47 1.47 0 0 0-.313-.145l-.111-.031c-.155-.037-.326-.04-.84-.04H6.2c-.569 0-.963 0-1.27.025a1.943 1.943 0 0 0-.492.09l-.104.045c-.242.123-.444.31-.585.54l-.057.1c-.064.127-.11.296-.134.597-.025.307-.026.702-.026 1.27v4.934Z"/>
+</svg>