Module: Evilution::Feedback::Messages Private

Defined in:
lib/evilution/feedback/messages.rb

This module is part of a private API. You should avoid using this module if possible, as it may be removed or be changed in the future.

Class Method Summary collapse

Class Method Details

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future. 



9
10
11
12
 
# File 'lib/evilution/feedback/messages.rb', line 9

def cli_footer
  "> Hit friction with evilution v#{Evilution::VERSION}? " \
    "Share details: #{Evilution::Feedback::DISCUSSION_URL}"
end

.info_guidance ⇒ Object

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future. 



23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
 
# File 'lib/evilution/feedback/messages.rb', line 23

def info_guidance
  <<~GUIDANCE.chomp
    The maintainer welcomes feedback in four cases:
      1. Errors raised by evilution
      2. Usage problems (confusing behavior, unexpected output)
      3. Friction (slow runs, awkward workflow, hard-to-interpret output)
      4. Missing capabilities or features you wish were there

    CONSENT (required):
      Never post on the user's behalf without explicit user permission.
      Show the user exactly what you would post. Submit only after the
      user explicitly approves.

    PRIVACY (required):
      Never include secrets, tokens, environment variables, the project
      name, absolute or project-relative file paths, source code, or
      class/method names from user code. The feedback channel is public.
  GUIDANCE
end

.mcp_hint ⇒ Object

This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future. 



14
15
16
17
18
19
20
21
 
# File 'lib/evilution/feedback/messages.rb', line 14

def mcp_hint
  "Feedback welcome on errors, usage problems, friction, or missing " \
    "capabilities you wish were there. Do NOT post on the user's " \
    "behalf without explicit user permission. Show the user exactly " \
    "what you would post and only submit after their explicit approval. " \
    "Never include secrets, env vars, project name, file paths, source " \
    "code, or class/method names from user code."
end