docs: clarify V3 reporting exceptions (PR #28131 review)

Author: medvednikov

doc/docs.md

@@ -107,16 +107,18 @@ embedded in your `v`).
 ### Automatic bug reports
 
 To help close the remaining gaps, a successful fallback (V3 fails to build a
-program that the established compiler then builds) submits the V version, target
-OS/arch, and build options to `https://bugs.vlang.io`. When a source excerpt is
-included it is always a **bounded strict subset** of the failing file — a window
-around the failure, or a head+tail window — and the whole file is never uploaded.
+program that the established compiler then builds) normally submits the V
+version, target OS/arch, and build options to `https://bugs.vlang.io`. When a
+source excerpt is included it is always a **bounded strict subset** of the failing
+file — a window around the failure, or a head+tail window — and the whole file is
+never uploaded.
 An internal V3 compiler error on a short program (and any directory build such as
 `v .`) submits metadata only. A generated-C error, however, maps to a specific V
 file, so it can still upload a strict-subset excerpt of that file plus a few lines
-of context around the failing line, even when the file is short. Reporting is
-skipped for test compilations and in GitHub CI. You can turn it off entirely by
-setting the environment variable `V_C_ERROR_BUG_REPORT_DISABLED=1`.
+of context around the failing line, even when the file is short. Inline-assembly
+fallbacks are notice-only and do not submit a report; reporting is also skipped
+for test compilations and in GitHub CI. You can turn it off entirely by setting
+the environment variable `V_C_ERROR_BUG_REPORT_DISABLED=1`.
 
 ## Packaging V for distribution
 See the [notes on how to prepare a package for V](packaging_v_for_distributions.md) .

vlib/v/help/build/build-c.txt

@@ -18,13 +18,14 @@ see also `v help build`.
       `-old-compiler` bypasses it and compiles with the established compiler in
       vlib/v. V already falls back to this compiler automatically when V3 cannot
       build an eligible program, and (unless V_C_ERROR_BUG_REPORT_DISABLED=1 is
-      set) reports the failure to https://bugs.vlang.io so the gap can be fixed:
-      the V version, target and build options, plus a bounded snippet of the
-      failing V source when one is available (always a strict subset, never the
-      whole file). An internal V3 error on a short program or a directory build
-      such as `v .` submits metadata only, while a generated-C error can still
-      include a strict-subset excerpt. See `v help build` for the full
-      description of the default.
+      set) normally reports the failure to https://bugs.vlang.io so the gap can
+      be fixed: the V version, target and build options, plus a bounded snippet
+      of the failing V source when one is available (always a strict subset,
+      never the whole file). An internal V3 error on a short program or a
+      directory build such as `v .` submits metadata only, while a generated-C
+      error can still include a strict-subset excerpt. Inline-assembly fallbacks
+      are notice-only; test compilations and GitHub CI also submit no report. See
+      `v help build` for the full description of the default.
 
    -cflags <flag>
       Pass the provided flag as is to the C compiler.

vlib/v/help/build/build.txt

@@ -19,15 +19,16 @@ The default compiler:
   On macOS and Linux, `v` compiles with the experimental V3 compiler (vlib/v3)
   by default. When V3 cannot yet build an eligible program, V automatically falls
   back to the established compiler in vlib/v, so builds keep working. Unless the
-  environment variable V_C_ERROR_BUG_REPORT_DISABLED=1 is set, a fallback also
-  reports the V version, target, and build options to https://bugs.vlang.io, plus
-  a bounded snippet of the failing V source when one is available. Any snippet is
-  a strict subset and the whole file is never uploaded. An internal V3 compiler
-  error on a short program or a directory build such as `v .` submits metadata
-  only, while a generated-C error maps to a V file and can still upload a
-  strict-subset excerpt of it, even for a short file. Pass `-old-compiler` (see
-  `v help build-c`) to always use the established compiler and skip both the V3
-  attempt and the reporting.
+  environment variable V_C_ERROR_BUG_REPORT_DISABLED=1 is set, a reportable
+  fallback also sends the V version, target, and build options to
+  https://bugs.vlang.io, plus a bounded snippet of the failing V source when one
+  is available. Any snippet is a strict subset and the whole file is never
+  uploaded. An internal V3 compiler error on a short program or a directory build
+  such as `v .` submits metadata only, while a generated-C error maps to a V file
+  and can still upload a strict-subset excerpt of it, even for a short file.
+  Inline-assembly fallbacks are notice-only; test compilations and GitHub CI also
+  submit no report. Pass `-old-compiler` (see `v help build-c`) to always use the
+  established compiler and skip both the V3 attempt and the reporting.
 
 Use `v build script.vsh` to compile a `.vsh` script without running it.
 `v -skip-running script.vsh` works too.