holycodex 0.15.1 → 0.15.2

package/README.md

@@ -5,5 +5,6 @@ version, and workflow lifecycle commands. The normative command contract is
 in the repository [CLI contract](../../docs/CLI.md).
 
 The Codex plugin is installed officially with `codex plugin marketplace add`
-followed by `codex plugin add holycodex@holycodex`. Use `bunx holycodex` only for the
-standalone CLI, including diagnostics and legacy payload repair.
+followed by `codex plugin add holycodex@holycodex`. The standalone CLI performs
+the same native setup, enables Default-mode user input, installs native
+specialist agent profiles, and provides diagnostics and workflow commands.

package/dist/assets/plugin/agents/explorer.md

@@ -4,6 +4,9 @@ Authority: read-only repository mapping and local fact finding.
 
 Permitted tasks: `lookup` and `trace`. Inspect only the assigned workspace scope, its symbols, callers, tests, configuration, and repository rules. Do not edit files, research externally, delegate, or choose architecture or product policy.
 
+Dispatch the selected task as the native `Explorer.lookup` or `Explorer.trace`
+agent type; retain that same type when continuing the assignment.
+
 Return evidence as exact paths, symbols, relevant call flow, applicable constraints, and unanswered facts. Separate observations from inferences so Root can judge material choices.
 
 Escalate when the requested scope is ambiguous, a fact crosses the repository boundary, evidence conflicts, or answering would require a write or a policy decision.

package/dist/assets/plugin/agents/librarian.md

@@ -4,6 +4,10 @@ Authority: assigned current-fact research only.
 
 Permitted tasks: `lookup` and `research`. Use the expressly assigned official current-source route for library, API, release, standard, or toolchain facts. Do not inspect unrelated repository implementation, edit files, delegate, or settle architecture and product choices.
 
+Dispatch the selected task as the native `Librarian.lookup` or
+`Librarian.research` agent type; retain that same type when continuing the
+assignment.
+
 Return the source locator, access or version context, concise supported claim, uncertainty, and conflicts. Distinguish sourced facts from recommendations so Root retains judgment.
 
 Escalate when the source route is unavailable, the requested claim lacks authoritative support, sources disagree materially, or the question expands beyond the assignment.

package/dist/assets/plugin/agents/reviewer.md

@@ -4,6 +4,10 @@ Authority: adversarial inspection and repair of the assigned result.
 
 Permitted tasks: `plan`, `code`, and `artifact`. Inspect the actual diff, callers, contracts, tests, compatibility, and declared scope. Repair only reviewer-owned defects inside that scope, verify the repair, and repeat until the assigned surface reaches a fixed point. Do not delegate, expand the change, or make Root decisions.
 
+Dispatch the selected task as the native `Reviewer.plan`, `Reviewer.code`, or
+`Reviewer.artifact` agent type; retain that same type when continuing the
+assignment.
+
 Return structured findings with severity, exact evidence, repaired paths, verification results, residual risk, and a clean or blocked terminal judgment. Treat missing proof and boundary violations as findings rather than assumptions.
 
 Escalate architecture, product, scope, trust, interface, external-state, or contradictory-evidence decisions to Root.

package/dist/assets/plugin/agents/root.md

@@ -2,10 +2,8 @@
 
 Root is the user-facing authority for intent, scope, architecture, product choices, policy, risk, integration, external state, and the final readiness judgment. Specialist evidence informs Root; it never transfers those decisions.
 
-Do trivial, one-off work directly. For unresolved architecture, scope, coordination, or material risk, use `plan`; for substantive non-Go orchestration, use `workflows`. Go stays direct. Use the implementation and review skills at their stated seams, and keep current library/API research on the `context7-cli` route.
+Use the assigned current dossier and repository-native evidence under the clean-room boundary. Treat denied capability, invalid input, uncertain effects, and contradictory evidence as fail-closed outcomes.
 
-Keep the clean-room boundary active: use the assigned current dossier and repository-native evidence only. Repository-local inspection, editing, formatting, linting, typechecking, compilation, builds, tests, and their reruns are ordinary implementation mechanics and need no additional approval inside the assigned scope. Obtain approval immediately before an external effect, destructive action, permission change, dependency installation, commit, push, tag, publication, or deployment. Treat denied capability, invalid input, uncertain effects, and contradictory evidence as fail-closed outcomes.
+Root accepts one fixed-point review, inspects the integrated diff, and makes the final readiness judgment.
 
-Workflow create, workflow run, workflow resume, local repository edit, local repository check, local repository lint, and local repository format actions do not require Root approval. Implementation plans, origin mutation, and CI triggering require Root approval.
-
-After implementation, require one fixed-point review. Inspect the relevant final diff yourself for ownership, dependency direction, cohesion, scope, abstraction, repository-native taste, mergeability, and readiness. Link to owning skills and contracts instead of copying their procedures.
+Stay silent for queued work, transparent resume/recovery, telemetry, and unchanged checkpoints. Speak only for new user input, one material state change or decision, or a terminal result; do not repeat an unchanged blocker or decision request.

package/dist/assets/plugin/agents/worker.md

@@ -2,9 +2,11 @@
 
 Authority: the literal assigned seam for bounded implementation, integration, checks, and approved operations.
 
-Permitted tasks: `mechanical`, `implementation`, `integration`, and `operations`. Change only named files and behavior, preserve ownership and dependency direction, validate every boundary, run proportional checks, repair bounded defects, and report changed paths plus evidence. Repository-local formatting, linting, typechecking, compilation, builds, tests, and reruns need no extra approval. Do not delegate, broaden scope, make Root decisions, or perform an unapproved external effect.
+Permitted tasks: `mechanical`, `implementation`, `integration`, and `operations`. Change only named files and behavior, preserve ownership and dependency direction, validate every boundary, run proportional checks, repair bounded defects, and report changed paths plus evidence. Do not delegate, broaden scope, or make Root decisions.
 
-Workflow create, workflow run, workflow resume, local repository edit, local repository check, local repository lint, and local repository format actions do not require Root approval. Implementation plans, origin mutation, and CI triggering require Root approval.
+Dispatch the selected task as the native `Worker.mechanical`,
+`Worker.implementation`, `Worker.integration`, or `Worker.operations` agent
+type; retain that same type when continuing the assignment.
 
 Return a compact structured outcome containing status, changed and relevant files, verification commands and results, remaining risk, and any exact material choice that needs Root. A warranted clarity pass may simplify changed files without changing behavior, interfaces, ownership, or scope.
 

package/dist/assets/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "holycodex",
-  "version": "0.15.1",
+  "version": "0.15.2",
   "description": "Root-directed capabilities and deterministic installed assets for HolyCodex.",
   "author": {
     "name": "David Basile Filho",
@@ -24,7 +24,6 @@
     "category": "Developer Tools",
     "capabilities": [
       "Skills",
-      "Hooks",
       "Code Intelligence"
     ],
     "defaultPrompt": [

package/dist/assets/plugin/rules/holycodex.md

@@ -1,17 +1,18 @@
 # HolyCodex installed rule
 
-The Root authority owns scope, architecture, product decisions, trust, and
-external effects. Providers and specialist workers receive validated inputs
+Root owns scope, architecture, product decisions, trust, and material effects.
+Providers and specialists receive validated inputs
 and may not broaden authority. Missing capability or uncertain state fails
 closed with an actionable diagnostic.
 
-Repository-local formatting, linting, typechecking, compilation, builds,
-tests, and reruns are verification mechanics inside an assigned change and do
-not require an approval gate. They need no user approval. Approval remains
-immediate for external effects, destructive actions, permission changes,
-dependency installation, commits, pushes, tags, publication, and deployment.
+An explicit plan-first request enters a read-only planning state. Root may inspect, search, reason, read git state, run proven read-only commands, and request missing user input. Root must not write files, install dependencies, run fix mode or generators, execute mutating workflows, commit, mutate external state, or dispatch implementation Workers. Showing the plan does not exit this state; only a later explicit user instruction such as `continue` or `implement` authorizes implementation.
 
-Workflow create, workflow run, workflow resume, local repository edit, local
-repository check, local repository lint, and local repository format actions do
-not require Root approval. Implementation plans, origin mutation, and CI
-triggering require Root approval.
+When a material decision needs missing user information, use native `request_user_input` when available: prefer one question, group at most three related questions, give 2–3 mutually exclusive choices with the evidence-backed recommendation first, state each consequence briefly, and let Codex supply the free-form choice. Derive safe answers from repository or authoritative evidence without interrupting the user. Fall back to one plain question only when the installed Codex lacks the tool.
+
+Workflow create, workflow run, workflow resume, local repository edit, local repository check, local repository lint, local repository format, local repository commit, external read, and specialist dispatch actions do not require Root approval.
+
+Version-control-server mutation, version-control-server CI triggering, and unclassified effect require Root approval.
+
+Classify the actual effect. Unknown effects fail closed. Transport uncertainty
+after dispatch inspects or resumes the existing operation and never blindly
+duplicates an effect whose outcome may already exist.

package/dist/assets/plugin/skills/babysit-ci/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: babysit-ci
-description: Monitor required CI jobs after an approved push or tag and report terminal evidence.
+description: Use after an approved push or tag when required CI must reach a terminal state; monitor jobs and report evidence.
 ---
 
 Start only after the approved push or tag succeeds, because unchanged or pending checks are expected external state rather than a reason to mutate again.

package/dist/assets/plugin/skills/code-review/SKILL.md

@@ -5,6 +5,8 @@ description: Use exactly once after code or manifest implementation for adversar
 
 Review the actual result once to fixed point, because a separate adversarial pass catches boundary, scope, compatibility, and proof gaps before Root judges readiness.
 
+Judge new or modified tests against [testing quality](../testing-quality.md).
+
 Owner: Reviewer. Boundary: inspect the assigned diff, callers, contracts, tests, and artifact; repair only reviewer-owned defects in scope, verify repairs, and escalate architecture, product, scope, trust, interface, or external-state decisions.
 
 Completion: no reviewer-owned defect remains, verification evidence is recorded, and every residual risk or Root decision is explicit.

package/dist/assets/plugin/skills/commit/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: commit
-description: Prepare and execute an approved local commit with exact scope proof.
+description: Use when the user requests a local commit; verify scope, commit it, and report the identity.
 ---
 
-Owner: Worker. Boundary: commit only the approved local scope after immediate approval and status proof; do not push, tag, publish, or deploy.
+Owner: Worker. Boundary: commit only the assigned local scope after status proof; remote version-control mutation remains approval-gated.
 Completion: the commit identity and post-commit status are reported.

package/dist/assets/plugin/skills/compress/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: compress
-description: Shorten text while preserving meaning, constraints, and voice.
+description: Use when text must be shortened; preserve meaning, constraints, and voice.
 ---
 
 Owner: Worker. Boundary: remove repetition without changing requirements, technical terms, or product voice.

package/dist/assets/plugin/skills/handoff/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: handoff
-description: Produce one redacted resumable handoff when work pauses or transfers.
+description: Use when work must pause or transfer; produce one redacted resumable handoff.
 ---
 
 Owner: Worker. Boundary: retain scope, owner, permissions, decisions, evidence, and the exact next action; omit secrets and unchanged narration.

package/dist/assets/plugin/skills/lsp/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lsp
-description: Use a validated language-server boundary for type-aware code facts.
+description: Use when code work needs type-aware definitions, references, diagnostics, or rename; query the validated language-server boundary.
 ---
 
 Owner: Worker. Boundary: use only the configured LSP provider and assigned scope; unavailable providers fail closed.

package/dist/assets/plugin/skills/lsp-setup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: lsp-setup
-description: Configure one required language server with minimum verified setup.
+description: Use when a required language server is unavailable; configure and verify the minimum setup.
 ---
 
 Owner: Worker. Boundary: validate the requested tool and platform before configuration; unavailable tools fail closed with an actionable diagnostic.

package/dist/assets/plugin/skills/plan-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plan-review
-description: Review one complete plan for feasibility, order, risk, and proof.
+description: Use when a complete plan needs adversarial review; check feasibility, order, risk, and proof to fixed point.
 ---
 
 Owner: Reviewer. Boundary: inspect the complete plan once to fixed point and return findings; material product or architecture choices return to Root.

package/dist/assets/plugin/skills/ponytail/SKILL.md

@@ -1,18 +1,6 @@
 ---
 name: ponytail
-description: >
-  Forces the laziest solution that actually works, simplest, shortest, most
-  minimal. Channels a senior dev who has seen everything: question whether the
-  task needs to exist at all (YAGNI), reach for the standard library before
-  custom code, native platform features before dependencies, one line before
-  fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY
-  coding task: writing, adding, refactoring, fixing, reviewing, or designing
-  code, and choosing libraries or dependencies. Also use whenever the user
-  says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal
-  solution", "yagni", "do less", or "shortest path", or complains about
-  over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT
-  use for non-coding requests (general knowledge, prose, translation,
-  summaries, recipes).
+description: Use for coding work or explicit requests for the simplest solution; apply the shortest repository-native implementation that works.
 argument-hint: "[lite|full|ultra]"
 license: MIT
 ---

package/dist/assets/plugin/skills/ponytail/metadata.json

@@ -6,7 +6,7 @@
   "skill_path": "skills/ponytail/SKILL.md",
   "license_path": "skills/ponytail/LICENSE",
   "notice_path": "skills/ponytail/NOTICE",
-  "skill_sha256": "1316a2f3f95741d2300b116fe0c2d81ce4a9568656ed0a62643f54aaf09957f2",
+  "skill_sha256": "e3cd463e1bd68b084eaf83aa2668b5bce8536871bcb5a3433b0ccad23f9385ee",
   "license_sha256": "fb1bc6909ac3ef82d5c22106e32ef682b0cff66788fa915fb9b53b15c9d2f3ab",
   "notice_sha256": "63859c12f8df7a216f0e34110d6e69e881f1f157e563c2e5761ad75f70c13759"
 }

package/dist/assets/plugin/skills/programming/SKILL.md

@@ -5,6 +5,8 @@ description: Use for bounded implementation, fixes, tests, or manifests when the
 
 Implement only the assigned seam, because repository-native ownership and a proportional proof keep a small change reviewable.
 
+When implementation changes tests, apply [testing quality](../testing-quality.md) before adding or retaining them.
+
 Owner: Worker. Boundary: inspect required callers and tests, preserve typed boundaries and portability, edit only approved files, make one bounded clarity pass, and escalate material choices.
 
 Completion: the requested behavior and focused tests are present, changed files are inspected, diagnostics and proportional checks pass, and structured evidence names residual risk or a precise blocker.

package/dist/assets/plugin/skills/refactor/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: refactor
-description: Restructure one decided seam while preserving behavior and interfaces.
+description: Use when one decided seam needs restructuring; preserve behavior and interfaces.
 ---
 
 Owner: Worker. Boundary: change only the assigned seam and preserve ownership, dependency direction, and public behavior.

package/dist/assets/plugin/skills/rules/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: rules
-description: Trace repository rule discovery, validation, and application failures.
+description: Use when repository rules fail discovery, validation, or application; trace the owning rule path.
 ---
 
 Owner: Worker. Boundary: inspect the owning rule loader and preserve deduplication, limits, caching, and trust boundaries.

package/dist/assets/plugin/skills/stop-slop/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Hardik Pandya
+
+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.

package/dist/assets/plugin/skills/stop-slop/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: stop-slop
+description: Use when drafting, editing, or reviewing prose; remove predictable AI writing patterns.
+metadata:
+  trigger: Writing prose, editing drafts, reviewing content for AI patterns
+  author: Hardik Pandya (https://hvpandya.com)
+---
+
+# Stop Slop
+
+Eliminate predictable AI writing patterns from prose.
+
+## Core Rules
+
+1. **Cut filler phrases.** Remove throat-clearing openers, emphasis crutches, and all adverbs. See [references/phrases.md](references/phrases.md).
+2. **Break formulaic structures.** Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See [references/structures.md](references/structures.md).
+3. **Use active voice.** Every sentence needs a human subject doing something. No passive constructions. No inanimate objects performing human actions ("the complaint becomes a fix").
+4. **Be specific.** No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.
+5. **Put the reader in the room.** No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.
+6. **Vary rhythm.** Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.
+7. **Trust readers.** State facts directly. Skip softening, justification, hand-holding.
+8. **Cut quotables.** If it sounds like a pull-quote, rewrite it.
+
+## Quick Checks
+
+Before delivering prose:
+
+- Any adverbs? Kill them.
+- Any passive voice? Find the actor, make them the subject.
+- Inanimate thing doing a human verb? Name the person.
+- Sentence starts with a Wh- word? Restructure it.
+- Any throat-clearing, binary contrast, vague declaration, meta-joiner, em dash, or repeated rhythm? Cut or rewrite it.
+
+## Scoring
+
+Rate directness, rhythm, trust, authenticity, and density from 1-10. Below 35/50: revise.
+
+See [references/examples.md](references/examples.md) for before/after transformations.
+
+## License
+
+MIT

package/dist/assets/plugin/skills/stop-slop/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Stop Slop"
+  short_description: "Remove predictable AI prose patterns"
+  default_prompt: "Edit the assigned prose using the stop-slop rules and disclosed references."
+policy:
+  allow_implicit_invocation: true

package/dist/assets/plugin/skills/stop-slop/references/examples.md

@@ -0,0 +1,69 @@
+# Before/After Examples
+
+## Example 1: Throat-Clearing + Binary Contrast
+
+**Before:**
+
+> "Here's the thing: building products is hard. Not because the technology is complex. Because people are complex. Let that sink in."
+
+**After:**
+
+> "Building products is hard. Technology is manageable. People aren't."
+
+**Changes:** Removed opener, binary contrast structure, and emphasis crutch. Direct statements.
+
+---
+
+## Example 2: Filler + Unnecessary Reassurance
+
+**Before:**
+
+> "It turns out that most teams struggle with alignment. The uncomfortable truth is that nobody wants to admit they're confused. And that's okay."
+
+**After:**
+
+> "Teams struggle with alignment. Nobody admits confusion."
+
+**Changes:** Cut hedging ("most"), removed throat-clearing phrases, deleted permission-granting ending.
+
+---
+
+## Example 3: Business Jargon Stack
+
+**Before:**
+
+> "In today's fast-paced landscape, we need to lean into discomfort and navigate uncertainty with clarity. This matters because your competition isn't waiting."
+
+**After:**
+
+> "Move faster. Your competition is."
+
+**Changes:** Eliminated jargon entirely. Core message in six words.
+
+---
+
+## Example 4: Dramatic Fragmentation
+
+**Before:**
+
+> "Speed. Quality. Cost. You can only pick two. That's it. That's the tradeoff."
+
+**After:**
+
+> "Speed, quality, cost—pick two."
+
+**Changes:** Single sentence. No performative emphasis.
+
+---
+
+## Example 5: Rhetorical Setup
+
+**Before:**
+
+> "What if I told you that the best teams don't optimize for productivity? Here's what I mean: they optimize for learning. Think about it."
+
+**After:**
+
+> "The best teams optimize for learning, not productivity."
+
+**Changes:** Direct claim. No rhetorical scaffolding.

package/dist/assets/plugin/skills/stop-slop/references/phrases.md

@@ -0,0 +1,128 @@
+# Phrases to Remove
+
+## Throat-Clearing Openers
+
+Remove these announcement phrases. State the content directly.
+
+- "Here's the thing:"
+- "Here's what [X]"
+- "Here's this [X]"
+- "Here's that [X]"
+- "Here's why [X]"
+- "The uncomfortable truth is"
+- "It turns out"
+- "The real [X] is"
+- "Let me be clear"
+- "The truth is,"
+- "I'll say it again:"
+- "I'm going to be honest"
+- "Can we talk about"
+- "Here's what I find interesting"
+- "Here's the problem though"
+
+Any "here's what/this/that" construction is throat-clearing before the point. Cut it and state the point.
+
+## Emphasis Crutches
+
+These add no meaning. Delete them.
+
+- "Full stop." / "Period."
+- "Let that sink in."
+- "This matters because"
+- "Make no mistake"
+- "Here's why that matters"
+
+## Business Jargon
+
+Replace with plain language.
+
+| Avoid                 | Use instead            |
+| --------------------- | ---------------------- |
+| Navigate (challenges) | Handle, address        |
+| Unpack (analysis)     | Explain, examine       |
+| Lean into             | Accept, embrace        |
+| Landscape (context)   | Situation, field       |
+| Game-changer          | Significant, important |
+| Double down           | Commit, increase       |
+| Deep dive             | Analysis, examination  |
+| Take a step back      | Reconsider             |
+| Moving forward        | Next, from now         |
+| Circle back           | Return to, revisit     |
+| On the same page      | Aligned, agreed        |
+
+## Adverbs
+
+Kill all adverbs. No -ly words. No softeners, no intensifiers, no hedges.
+
+Specific offenders:
+
+- "really"
+- "just"
+- "literally"
+- "genuinely"
+- "honestly"
+- "simply"
+- "actually"
+- "deeply"
+- "truly"
+- "fundamentally"
+- "inherently"
+- "inevitably"
+- "interestingly"
+- "importantly"
+- "crucially"
+
+Also cut these filler phrases:
+
+- "At its core"
+- "In today's [X]"
+- "It's worth noting"
+- "At the end of the day"
+- "When it comes to"
+- "In a world where"
+- "The reality is"
+
+## Meta-Commentary
+
+Remove self-referential asides. The essay should move, not announce its own structure.
+
+- "Hint:"
+- "Plot twist:" / "Spoiler:"
+- "You already know this, but"
+- "But that's another post"
+- "X is a feature, not a bug"
+- "Dressed up as"
+- "The rest of this essay explains..."
+- "Let me walk you through..."
+- "In this section, we'll..."
+- "As we'll see..."
+- "I want to explore..."
+
+## Performative Emphasis
+
+False intimacy or manufactured sincerity:
+
+- "creeps in"
+- "I promise"
+- "They exist, I promise"
+
+## Telling Instead of Showing
+
+Announcing difficulty or significance rather than demonstrating it:
+
+- "This is genuinely hard"
+- "This is what leadership actually looks like"
+- "This is what X actually looks like"
+- "actually matters"
+
+## Vague Declaratives
+
+Sentences that announce importance without naming the specific thing. Kill these.
+
+- "The reasons are structural"
+- "The implications are significant"
+- "This is the deepest problem"
+- "The stakes are high"
+- "The consequences are real"
+
+If a sentence says something is important/deep/structural without showing the specific thing, cut it or replace it with the specific thing.