Skip the manual K calibration the way the automatic one is skipped

Bambuddy already recognises the printer's automatic pressure-advance run,
    auto_pa_line_calib_mode, and leaves no archive and sends no notification
    for it. Started by hand rather than automatically before a print, the
    same calibration reports under a different name: it prints a pattern
    where the automatic one prints a line, and carries no auto_ prefix, so
    pa_pattern_calib_mode matched nothing.

    It arrives exactly the way the automatic one does -- a bare subtask name
    with no /usr/ path -- so it hit the same outcome the module was written
    to prevent: an FTP sweep for a 3MF that cannot exist, six candidate names
    across five directories with retries, and then a no-3MF archive named
    after the calibration, on a printer in the middle of calibrating.

    One entry on INTERNAL_JOB_NAMES covers it. That set is the single place
    both the print-start and print-complete callbacks consult, so archiving,
    the 3MF sweep and the notifications are all handled by the one line.

    Matching stays exact after normalising path, suffix and case. The
    negative cases are extended alongside the positive ones, so a file
    somebody deliberately named pa_pattern_calib_mode_v2.3mf is still
    archived as the print it is.

    The manual PA *line* method, if it reports its own name, is not covered
    here -- the list is deliberately limited to names that have actually been
    observed rather than ones that seem likely.

backend/app/utils/print_jobs.py

@@ -29,10 +29,17 @@ print-complete callbacks can share one answer.
 # ``auto_pa_line_calib_mode`` is the pressure-advance (K profile) line. This one
 # is reported as a *subtask name* with no ``/usr/`` path at all, which is why
 # the path rule alone was never enough.
+#
+# ``pa_pattern_calib_mode`` is the same calibration started by hand rather than
+# automatically before a print -- the manual flow-dynamics run prints a pattern
+# where the automatic one prints a line, and it carries its own name with no
+# ``auto_`` prefix. It reaches Bambuddy exactly the way the automatic one does,
+# so leaving it off the list produced the same no-3MF archive.
 INTERNAL_JOB_NAMES = frozenset(
     {
         "auto_cali_for_user",
         "auto_pa_line_calib_mode",
+        "pa_pattern_calib_mode",
     }
 )