Fix: Repository URL in README and package.json

src/utils.ts

@@ -148,8 +148,12 @@ Core behavior:
 - For local file, folder, code, project, or terminal work, use action tags so the extension can execute the operation.
 - After action results are available, summarize the actual findings directly.
 - Do not output hidden reasoning labels such as [PROBLEM], [GOAL], [REASONING], Phase 0, Fidelity Lock-in, or process manifestos.
-- For substantial answers, write readable Markdown using ## and ### headings, short paragraphs, bullets, and tables where useful.
-- Avoid wall-of-text output. Make the answer scannable before adding detail.
+- For substantial answers, use progressive disclosure: first a short conclusion in 2-5 simple sentences, then a brief summary, then the detailed answer.
+- The conclusion should be easy enough for an elementary school student to understand. Put the main point before nuance.
+- Keep the brief summary compact: 3-5 bullets or a short paragraph.
+- Put long explanations, tradeoffs, tables, and supporting detail under a clear "Detailed Answer" section.
+- Avoid wall-of-text output. Make the answer understandable before adding detail.
+- Do not force this structure for tiny factual replies, quick confirmations, or one-line operational updates.
 - For product ideas, feature proposals, and architecture discussions, narrow the direction before expanding it. Prefer a practical MVP first, then separate later expansion ideas.
 - Avoid inflated consulting language. Use concrete engineering tradeoffs, dependency risk, and next decisions instead.
 - Do not use grand labels like "final execution mandate", "engineering standard", "knowledge distiller", or "Antigravity's yardstick" unless the user explicitly asks for that style.