modwright 0.1.0

package/knowledge/stardewvalley/smapi.loader.yaml

@@ -0,0 +1,284 @@
+game: stardewvalley
+topic: smapi.loader
+title: SMAPI as the mod loader — versions, mod scanning, load order, and every skip reason
+facts:
+  - id: stardewvalley.smapi.loader.version-and-game-floor
+    claim: 'SMAPI 4.5.2 is the current release and it requires Stardew Valley 1.6.14 or later with no
+      upper bound: `MinimumGameVersion` is `new GameVersion("1.6.14")` and `MaximumGameVersion` is
+      `null`.'
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Constants.cs (`internal static string RawApiVersion = "4.5.2";`,
+      `public static ISemanticVersion MinimumGameVersion { get; } = new GameVersion("1.6.14");`,
+      `public static ISemanticVersion? MaximumGameVersion { get; } = null;`); corroborated by
+      docs/release-notes.md, "## 4.5.2 / Released 14 March 2026 for Stardew Valley 1.6.14 or later"
+    tags:
+      - smapi
+      - version
+      - compat
+      - floor
+      - rule
+    detail: "This is the one hard version floor in the whole matrix and it is a literal in SMAPI's
+      source, so a `CompatRule` with `min: \"1.6.14\"` and no `max` is exactly right. A surface that
+      invents a maximum would be wrong today: the installed game (1.6.15) is one patch above the
+      floor and SMAPI declares no ceiling at all."
+  - id: stardewvalley.smapi.loader.release-notes-date-differs-from-tag
+    claim: "SMAPI's release-notes date and its GitHub tag date differ by several days and consistently
+      so: 4.5.2 says \"Released 14 March 2026\" against a tag published 2026-03-22; 4.5.1 says 25
+      January 2026 against 2026-01-28; 4.4.0 says 10 January 2026 against 2026-01-11."
+    status: inferred
+    source: https://github.com/Pathoschild/SMAPI/blob/develop/docs/release-notes.md compared against the
+      GitHub releases API for Pathoschild/SMAPI, both read 2026-09-11
+    tags:
+      - version
+      - date
+      - conflict
+      - provenance
+    detail: Quote the release-notes date when citing a release and never treat the tag timestamp as the
+      release date. The same care is needed for Content Patcher, whose release notes carry dates
+      while its repository publishes no GitHub releases at all.
+  - id: stardewvalley.smapi.loader.a-mod-is-a-folder-with-a-manifest
+    claim: "A mod is any folder containing a `manifest.json`, found at any depth under `Mods/`. Its type
+      is decided entirely by the manifest: `isContentPack = ContentPackFor?.UniqueID` non-empty,
+      `isSmapi = EntryDll` non-empty, and `if (isContentPack == isSmapi) type = ModType.Invalid`."
+    status: inferred
+    source: SMAPI develop, src/SMAPI.Toolkit/Framework/ModScanning/ModScanner.cs `ReadFolder(...)`
+    tags:
+      - mods
+      - scanning
+      - manifest
+      - content-pack
+      - modroots
+    detail: So the same folder shape carries both kinds of mod, which is why this game has one mod root
+      rather than one per system. `readManifest` returning `undefined` here means "this folder is
+      not a mod", a stronger statement than on Valheim where a bare DLL is normal.
+  - id: stardewvalley.smapi.loader.scanner-ignore-lists
+    claim: "When deciding whether a folder is empty, SMAPI's scanner ignores filesystem entries matching
+      `^__folder_managed_by_vortex$`, `(?:^\\._|^\\.DS_Store$|^__MACOSX$|^mcs$)` and
+      `^(?:desktop\\.ini|Thumbs\\.db)$`, plus files with any of these extensions: .doc .docx .md
+      .rtf .txt .bmp .gif .ico .jpeg .jpg .png .psd .tif .xcf .rar .zip .7z .tar .tar.gz .backup
+      .bak .old .url .lnk."
+    status: inferred
+    source: SMAPI develop, src/SMAPI.Toolkit/Framework/ModScanning/ModScanner.cs, the
+      `IgnoreFilesystemNames` and `IgnoreFileExtensions` fields
+    tags:
+      - scanning
+      - mods
+      - packaging
+      - validator
+    detail: "Useful in two directions: a `list_mods` that mirrors it agrees with the game, and a
+      packaging validator can warn when a release zip carries `.DS_Store`, `__MACOSX`, `Thumbs.db`
+      or `desktop.ini` — harmless to SMAPI, but noise in a published download."
+  - id: stardewvalley.smapi.loader.xnb-mod-detection
+    claim: A folder holding only `.xgs`, `.xnb`, `.xsb` or `.xwb` files (optionally with
+      `.json`/`.yaml`) and no `manifest.json` is classified `ModType.Xnb` with the message "it's not
+      a SMAPI mod (see https://smapi.io/xnb for info)."
+    status: inferred
+    source: SMAPI develop, src/SMAPI.Toolkit/Framework/ModScanning/ModScanner.cs, the
+      `StrictXnbModExtensions` / `PotentialXnbModExtensions` sets and the `IsXnbMod(...)` branch
+    tags:
+      - xnb
+      - legacy
+      - scanning
+      - validator
+      - block
+    detail: "XNB mods replace files in the game's `Content` folder and are the deprecated pre-SMAPI mod
+      style. A validator that sees this shape in a build output should block: SMAPI will refuse the
+      folder outright."
+  - id: stardewvalley.smapi.loader.other-scanner-failure-texts
+    claim: "The scanner's other named failures, verbatim, are \"it's an empty Vortex folder (is the mod
+      disabled in Vortex?).\", \"it's an empty folder.\", \"the SMAPI installer isn't a mod (you can
+      delete this folder after running the installer file).\", \"it contains files, but none of them
+      are manifest.json.\", \"its manifest is invalid.\" and \"parsing its manifest failed:
+      {message}\"."
+    status: inferred
+    source: SMAPI develop, src/SMAPI.Toolkit/Framework/ModScanning/ModScanner.cs `ReadFolder(...)`
+    tags:
+      - scanning
+      - errors
+      - log
+      - signature
+    detail: "Each of these reaches the log as the `because {reason}` half of a skipped-mods line, so
+      they are matchable text, not just internal states. The \"SMAPI installer isn't a mod\" case is
+      a real user error: people unzip the installer into `Mods/`."
+  - id: stardewvalley.smapi.loader.load-order-is-a-dependency-sort
+    claim: There is no load-order file. SMAPI computes order as a depth-first topological sort over each
+      mod's `Dependencies`, preceded by `ApplyLoadOrderOverrides` which moves the ids listed in the
+      config's `ModsToLoadEarly` and `ModsToLoadLate` to the front and back.
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/ModLoading/ModResolver.cs, `ProcessDependencies(...)` and
+      `ApplyLoadOrderOverrides(mods, modIdsToLoadEarly, modIdsToLoadLate)`
+    tags:
+      - load-order
+      - dependencies
+      - modresolver
+    detail: "So `load_order` has a genuine but partial answer here, unlike Valheim where it has none:
+      the two override lists are real, file-backed and diffable, while the rest of the order is
+      derived and has no file."
+  - id: stardewvalley.smapi.loader.load-order-override-lists
+    claim: "`ModsToLoadEarly` and `ModsToLoadLate` in `smapi-internal/config.json` are lists of mod
+      UniqueIDs that force load order. They can be overridden by `smapi-internal/config.user.json`
+      and by `Mods/SMAPI-config.json`, and `smapi-internal/config.json` itself is reset on every
+      SMAPI update."
+    status: community
+    source: "The shipped file's own documentation comment
+      (https://github.com/Pathoschild/SMAPI/blob/develop/src/SMAPI/SMAPI.config.json): \"This lets
+      you manually fix the load order if needed, but this is a last resort — SMAPI automatically
+      adjusts the load order based on mods' dependencies\"; the three paths are `ApiConfigPath`,
+      `ApiUserConfigPath` and `ApiModGroupConfigPath` in src/SMAPI/Constants.cs"
+    tags:
+      - load-order
+      - config
+      - loadorderfile
+      - override
+    detail: "Entries are UniqueIDs, which resolve to installed mods with confidence, so a
+      `loadOrderFile` implementation can set `modId` on every entry — unlike BG3's UUID-in-a-pak
+      case. The override precedence matters: read the per-mods-folder file first, then the user
+      file, then the shipped one."
+  - id: stardewvalley.smapi.loader.load-order-override-warnings
+    claim: "SMAPI warns at startup when the override lists name mods that are not installed, or name the
+      same mod in both lists, with three distinct lines ending \"which aren't installed: '...'.\"
+      and \"These will be loaded early.\""
+    status: inferred
+    source: "SMAPI develop, src/SMAPI/Framework/SCore.cs: the three `The 'smapi-internal/config.json'
+      file lists mod IDs in ...` log calls at LogLevel.Warn"
+    tags:
+      - load-order
+      - validator
+      - log
+      - signature
+      - cross-check
+    detail: All three are checks ModWright can perform statically, before the game runs — the rare case
+      where a surface can report a load-order problem before the loader says anything.
+  - id: stardewvalley.smapi.loader.skip-reasons
+    claim: "Every reason SMAPI gives for skipping a mod is a sentence fragment designed to be appended
+      after \"failed loading <mod> because \". The dependency ones are \"it requires mods which
+      aren't installed ({names}).\", \"it needs newer versions of some mods: {name} (needs {version}
+      or later).\", \"it needs the '{name}' mod, which couldn't be loaded.\" and \"its dependencies
+      have a circular reference: {a} => {b} => {c}).\"."
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/ModLoading/ModResolver.cs, the
+      `SetStatus(ModMetadataStatus.Failed, ModFailReason.MissingDependencies, ...)` calls
+    tags:
+      - errors
+      - dependencies
+      - log
+      - signature
+      - triage
+    detail: "The first is the root cause and the third is the cascade, exactly the BepInEx pattern: one
+      Error naming the real problem, then one per downstream mod. `triage_logs` must rank the first
+      above the third or it will report the wrong mod."
+  - id: stardewvalley.smapi.loader.version-skip-reasons
+    claim: "The version-related skip reasons are \"it needs SMAPI {version} or later. Please update
+      SMAPI to the latest version to use this mod.\", \"it needs Stardew Valley {version} or later.
+      Please update your game to the latest version to use this mod.\", \"it's obsolete: {phrase}\"
+      and \"{phrase}. Please check for a newer version at {urls}\" (or \"... version newer than {v}
+      at ...\")."
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/ModLoading/ModResolver.cs `ValidateManifests(...)`; the
+      last two come from the mod's record in `smapi-internal/metadata.json`, not from anything on
+      disk in the mod folder
+    tags:
+      - errors
+      - version
+      - compat
+      - log
+      - signature
+    detail: "The last two are the important distinction: they are *curated* verdicts from SMAPI's
+      internal database, not detected incompatibilities. A triage verdict that reports them as a
+      version mismatch is misleading — the right next action is to look the mod up on the
+      compatibility list, not to change versions. `updateUrls` always ends with
+      `https://smapi.io/mods`."
+  - id: stardewvalley.smapi.loader.duplicate-and-dll-skip-reasons
+    claim: "Two more skip reasons are filesystem facts: \"its DLL '{EntryDll}' doesn't exist.\" and
+      \"you have multiple copies of this mod installed. To fix this, delete these folders and
+      reinstall the mod: {folders}.\"."
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/ModLoading/ModResolver.cs `ValidateManifests(...)` — the
+      `EntryDll` file-existence check and the `duplicatesById` grouping, which is case-insensitive
+      on `UniqueID`
+    tags:
+      - errors
+      - duplicate
+      - entrydll
+      - validator
+      - conflict
+    detail: "Both are checkable before the game runs. The duplicate check in particular is the reason
+      `find_conflicts` on this game must key on `UniqueID` rather than on file paths: two mods in
+      different folders with the same id genuinely contend, and two mods with the same file names in
+      different folders do not."
+  - id: stardewvalley.smapi.loader.rewrites-mods-for-compatibility
+    claim: SMAPI rewrites older mod assemblies at load time so they keep working against a newer game,
+      controlled by the `RewriteMods` setting (default true). Disabling it logs "You disabled
+      rewriting broken mods, so many older mods may fail to load. You can undo this by reinstalling
+      SMAPI."
+    status: inferred
+    source: 'SMAPI develop, src/SMAPI/SMAPI.config.json (`"RewriteMods": true`, with the comment
+      "Disabling this may prevent older mods from loading"),
+      src/SMAPI/Framework/Logging/LogManager.cs `LogSettingsHeader`, and the roughly one hundred
+      `*Facade.cs` files under src/SMAPI/Framework/ModLoading/Rewriters/StardewValley_1_6/'
+    tags:
+      - compat
+      - rewriting
+      - loader
+      - advisory
+      - guidance
+    detail: "No other loader ModWright supports repairs its mods. It inverts the usual compat advice: on
+      this game a mod that fails to load is more often on the curated broken list than genuinely
+      version-incompatible, so a `check_compat` advisory should say to read the skip reason before
+      assuming a version problem."
+  - id: stardewvalley.smapi.loader.harmony-is-bundled-and-opt-in
+    claim: SMAPI bundles Harmony at `smapi-internal/0Harmony.dll`, patches it to work with the game
+      (`FixHarmony`, default true), suppresses Harmony debug mode by default
+      (`SuppressHarmonyDebugMode`, default true), and the build package references it only when
+      `EnableHarmony` is set to true (default false).
+    status: inferred
+    source: SMAPI develop, src/SMAPI.ModBuildConfig/build/smapi.targets (`<Reference Include="0Harmony"
+      Condition="'$(EnableHarmony)' == 'true'" HintPath="$(GamePath)\smapi-internal\0Harmony.dll"
+      ...>`, `<EnableHarmony Condition="'$(EnableHarmony)' == ''">false</EnableHarmony>`) and
+      src/SMAPI/SMAPI.config.json
+    tags:
+      - harmony
+      - build
+      - compat
+      - config
+    detail: "`FixHarmony`'s own config comment is \"If you disable this, mods which use Harmony are
+      likely to cause game crashes\", and `SuppressHarmonyDebugMode`'s is \"Debug mode should never
+      be enabled by a released mod\". Both are readable from disk and both change what a log means,
+      so both deserve a compat rule. The console command `harmony_summary [S:search]` lists live
+      patches."
+  - id: stardewvalley.smapi.loader.console-is-stdin-only
+    claim: "SMAPI's console reads commands from standard input, gated by the `ListenForConsoleInput`
+      setting; there is no documented file-based channel for SMAPI console commands. The game's own
+      debug commands do have one: `debug runmacro <filename>` runs a list of slash-prefixed commands
+      from a `.txt` file in the game folder."
+    status: community
+    source: "https://stardewvalleywiki.com/Modding:Console_commands (read 2026-09-11): \"You can enter
+      console commands directly into the SMAPI console window\" and, under Macros, \"Instead of
+      entering each command directly into the SMAPI console, you can also use the `debug runmacro`
+      command to a list of debug commands from a text file. (This doesn't work with the non-debug
+      commands.)\"; `ListenForConsoleInput` from src/SMAPI/SMAPI.config.json"
+    tags:
+      - console
+      - bridge
+      - transport
+      - debug
+      - verification
+    detail: "`debug runmacro` is a payload transport, not a trigger — someone still has to type it once
+      — so it does not replace a bridge. It is still the cheapest way to get a batch of game state
+      changes into a test session."
+  - id: stardewvalley.smapi.loader.console-commands-mod-is-bundled
+    claim: 'The console commands are supplied by a bundled mod SMAPI installs into `Mods/`, with
+      manifest `{"Name": "Console Commands", "Author": "SMAPI", "UniqueId": "SMAPI.ConsoleCommands",
+      "EntryDll": "ConsoleCommands.dll"}`; the other bundled mod is `SMAPI.SaveBackup`.'
+    status: inferred
+    source: "https://github.com/Pathoschild/SMAPI/blob/develop/src/SMAPI.Mods.ConsoleCommands/manifest.\
+      json; both ids appear in src/SMAPI/SMAPI.config.json's `\"SuppressUpdateChecks\":
+      [\"SMAPI.ConsoleCommands\", \"SMAPI.SaveBackup\"]`"
+    tags:
+      - console
+      - bundled
+      - manifest
+      - validator
+    detail: Note the field is spelled `UniqueId` in that file, not `UniqueID`. SMAPI's JSON binding is
+      case-insensitive so it loads fine — which means a ModWright validator must be case-insensitive
+      on manifest field names too, or it will reject a file SMAPI itself ships.

package/knowledge/stardewvalley/smapi.logs.yaml

@@ -0,0 +1,329 @@
+game: stardewvalley
+topic: smapi.logs
+title: SMAPI-latest.txt — location, the exact line format, the startup lines, and SMAPI's own parser
+facts:
+  - id: stardewvalley.smapi.logs.path-and-name
+    claim: The SMAPI log is written to `%APPDATA%\StardewValley\ErrorLogs\SMAPI-latest.txt`. The crash
+      log beside it is `SMAPI-crash.txt`, and it is deliberately not deleted when SMAPI purges old
+      logs.
+    status: inferred
+    source: 'SMAPI develop, src/SMAPI/Constants.cs: `LogDir = Path.Combine(Constants.DataPath,
+      "ErrorLogs")`, `LogNamePrefix = "SMAPI-"`, `LogFilename = $"{LogNamePrefix}latest"`,
+      `LogExtension = "txt"`, `FatalCrashLog = Path.Combine(LogDir, "SMAPI-crash.txt")`;
+      `PurgeNormalLogs()` in src/SMAPI/Framework/SCore.cs skips `FatalCrashLog`'
+    tags:
+      - log
+      - path
+      - appdata
+      - logsource
+      - crash
+    detail: "The wiki states the same in prose: \"It's output to the game's ErrorLogs data folder ...
+      The log file is always created (even if there are no errors) and it's written continuously (so
+      you don't need to exit the game to see the log so far).\""
+  - id: stardewvalley.smapi.logs.player-numbered-fallbacks
+    claim: If `SMAPI-latest.txt` already exists and is in use, SMAPI walks `SMAPI-latest.player-2.txt`,
+      `SMAPI-latest.player-3.txt` and so on until it finds a free name, so a log source must declare
+      candidates rather than one path.
+    status: inferred
+    source: 'SMAPI develop, src/SMAPI/Framework/SCore.cs `GetLogPath()`: the loop `for (int i = 2; i <
+      int.MaxValue; i++)` over `$"{Constants.LogFilename}.player-{i}.{Constants.LogExtension}"`'
+    tags:
+      - log
+      - candidates
+      - logsource
+      - split-screen
+      - multi-instance
+    detail: "Same shape as BepInEx's `LogOutput.log.1`-`.4` fallbacks on Valheim, for a different
+      reason: here it is a second running instance (local co-op through two game processes), not a
+      file lock."
+  - id: stardewvalley.smapi.logs.one-file-per-run-autoflush
+    claim: "The log is opened as `new StreamWriter(path, append: false) { AutoFlush = true }` and every
+      line is written with an explicit `\\r\\n`, so it is one fresh file per run, complete up to the
+      instant it is read."
+    status: inferred
+    source: SMAPI develop,
+      https://github.com/Pathoschild/SMAPI/blob/develop/src/SMAPI/Framework/Logging/LogFileManager.cs;
+      the line-ending comment is "always use Windows-style line endings for convenience (Linux/macOS
+      editors are fine with them, Windows editors often require them)"
+    tags:
+      - log
+      - run-scope
+      - truncation
+      - autoflush
+    detail: "Good for `core/logs` run scoping: a plain whole-file read is already run-scoped, with none
+      of the Cyberpunk redscript in-place-truncation trap, and the file can be read while the game
+      is running without waiting for a flush."
+  - id: stardewvalley.smapi.logs.line-format
+    claim: 'Every line is `[HH:mm:ss LEVEL source] message`, built by `$"[{DateTime.Now:HH:mm:ss}
+      {levelStr}{(playerIndex != null ? $" screen_{playerIndex}" : "")} {source}]"` followed by a
+      space and the message. The timestamp is local time with no date.'
+    status: inferred
+    source: SMAPI develop,
+      https://github.com/Pathoschild/SMAPI/blob/develop/src/SMAPI/Framework/Monitor.cs,
+      `GenerateMessagePrefix(string source, ConsoleLogLevel level)` and `LogImpl(...)`'s `string
+      fullMessage = $"{prefix} {message}";`
+    tags:
+      - log
+      - format
+      - signature
+      - timestamp
+      - regex
+    detail: The wiki's own worked example agrees exactly — `[18:00:00 TRACE NameOfMod] a trace message`
+      through `[18:00:00 ERROR NameOfMod] an error message`. Because there is a timestamp,
+      `SourceStatus.timestamps` is true for this source, which is a first among ModWright's text-log
+      surfaces; but with no date it can only order lines within one run.
+  - id: stardewvalley.smapi.logs.level-padding-and-the-overflow
+    claim: The level is uppercased and right-padded to `MaxLevelLength`, which is computed over
+      `LogLevel` (Trace, Debug, Info, Warn, Error, Alert) and is therefore 5 — giving `TRACE`,
+      `DEBUG`, `INFO `, `WARN `, `ERROR`, `ALERT`. But the lookup is keyed on `ConsoleLogLevel`,
+      which also has `Critical` and `Success`, so `CRITICAL` (8) and `SUCCESS` (7) overflow the
+      column and are not padded.
+    status: inferred
+    source: "SMAPI develop, src/SMAPI/Framework/Monitor.cs: `MaxLevelLength =
+      Enum.GetValues<LogLevel>().Max(level => level.ToString().Length)` and `LogStrings =
+      Enum.GetValues<ConsoleLogLevel>().ToDictionary(level => level, level =>
+      level.ToString().ToUpperInvariant().PadRight(Monitor.MaxLevelLength))`; the two extra members
+      are in src/SMAPI.Internal/ConsoleWriting/ConsoleLogLevel.cs"
+    tags:
+      - log
+      - format
+      - signature
+      - gotcha
+      - regex
+      - critical
+    detail: "A signature written against fixed columns will miss exactly the lines that matter most:
+      `Monitor.LogFatal` emits `Critical`, and `LogManager` calls it for \"Malicious mod detected.\"
+      Match the level as `[A-Z]+` with one or more following spaces, exactly as SMAPI's own parser
+      does. Same class of trap as BepInEx's ten-character source padding on Valheim."
+  - id: stardewvalley.smapi.logs.source-is-the-display-name
+    claim: The bracketed source is one of `SMAPI`, `game`, or a mod's **display name** — never its
+      UniqueID. SMAPI registers monitors as `GetMonitor("SMAPI", "SMAPI")`, `GetMonitor("game",
+      "game")` and `GetMonitor(manifest.UniqueID, mod.DisplayName)`.
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/Logging/LogManager.cs (constructor) and
+      src/SMAPI/Framework/SCore.cs (`this.LogManager.GetMonitor(manifest.UniqueID,
+      mod.DisplayName)`)
+    tags:
+      - log
+      - source
+      - signature
+      - inventory
+      - uniqueid
+    detail: So a log-derived mod inventory is keyed on a human-facing name that can change between
+      versions, and joining it back to a manifest id requires the `Loaded N mods:` block or a bridge
+      probe over `helper.ModRegistry`. It is also why the manifest's `Name` field has its square
+      brackets rewritten.
+  - id: stardewvalley.smapi.logs.split-screen-field
+    claim: In split-screen the prefix gains a ` screen_<N>` field between the level and the source,
+      emitted only when the screen id is non-null.
+    status: inferred
+    source: "SMAPI develop, src/SMAPI/Framework/Monitor.cs `GenerateMessagePrefix`; SMAPI's own parser
+      matches it as `(?: +screen_(?<screen>\\d+))?` and sets `log.IsSplitScreen = true` when any
+      message has a non-zero screen id (src/SMAPI.Web/Framework/LogParsing/LogParser.cs)"
+    tags:
+      - log
+      - format
+      - split-screen
+      - signature
+      - regex
+  - id: stardewvalley.smapi.logs.console-input-and-blank-lines
+    claim: Console input the player typed is written to the log file only (not the console, where it
+      already appeared) as `{prefix} $>{input}`, and `Monitor.Newline()` writes genuinely empty
+      lines that separate the mod list, the content-pack list and the warning blocks.
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/Monitor.cs `LogUserInput(string input)`
+      (`this.LogFile.WriteLine($"{prefix} $>{input}")`) and `Newline()`; the section separations are
+      the `this.Monitor.Newline()` calls in src/SMAPI/Framework/Logging/LogManager.cs `LogModInfo`
+    tags:
+      - log
+      - console
+      - format
+      - parsing
+      - bridge
+    detail: The `$>` line means a console session is partially reconstructable from the log alone.
+      Whether a command's *output* also reaches the log was not confirmed without a real run — if it
+      does, `patch summary` becomes readable without a bridge, which would be the cheapest
+      verification win on this game.
+  - id: stardewvalley.smapi.logs.banner-line
+    claim: "The first line of every run is `SMAPI {ApiVersion} with Stardew Valley
+      {Game1.GetVersionString()} on {platform}` at Info, followed by `Mods go here: {path}` and `Log
+      started at {DateTime.UtcNow:s} UTC`."
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/Logging/LogManager.cs `LogIntro(...)`
+    tags:
+      - log
+      - banner
+      - version
+      - compat
+      - signature
+    detail: "This is where both live version axes come from in one line, and the `Log started at ...
+      UTC` line is the **only** absolute timestamp in the file — a run-scoping implementation should
+      anchor on it and treat every `HH:mm:ss` as an offset from it. When `--mods-path` was used, an
+      extra line reads `(Using custom --mods-path argument. Game folder: {path}.)`."
+  - id: stardewvalley.smapi.logs.mod-list-block
+    claim: Loaded mods are reported as `Loaded {N} mods:` (or `Loaded 0 mods.`) at Info, followed by one
+      indented line per mod of the form `   {DisplayName} {Version} by {Author} | {Description}`,
+      and then the same shape for `Loaded {N} content packs:` with an extra ` | for {parent mod}`
+      segment.
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/Logging/LogManager.cs `LogModInfo(...)`
+    tags:
+      - log
+      - inventory
+      - signature
+      - success
+      - content-pack
+    detail: The author and description segments are omitted when blank, so a pattern must make both
+      optional — SMAPI's own parser does exactly that. The list is ordered `OrderBy(p =>
+      p.DisplayName)`, i.e. **alphabetically, not in load order**; treating it as a load order is a
+      trap a naive implementation walks straight into.
+  - id: stardewvalley.smapi.logs.skipped-mods-block
+    claim: Failed mods appear under a fixed three-line header at Error — `   Skipped mods`, then three
+      spaces plus fifty hyphens, then `      These mods could not be added to your game.` — followed
+      by one line per mod of the form `      - {DisplayName} {Version} because {reason}`.
+    status: inferred
+    source: "SMAPI develop, src/SMAPI/Framework/Logging/LogManager.cs `LogModWarnings(...)`:
+      `this.Monitor.Log(\"   \" + \"\".PadRight(50, '-'), LogLevel.Error)` and `string message =
+      $\"      - {mod.DisplayName}{(\" \" +
+      mod.Manifest?.Version?.ToString()).TrimEnd()}{technicalInfo} because {mod.Error}\";`"
+    tags:
+      - log
+      - errors
+      - skipped
+      - signature
+      - triage
+    detail: "With `LogTechnicalDetailsForBrokenMods` enabled the line gains ` (ID: {UniqueID}, path:
+      {relative path})` before `because`, which is the only place the UniqueID appears alongside the
+      display name. A duplicate mod is logged once, without its version. Any `ErrorDetails` follows
+      on the next line as `        ({details})` at Trace."
+  - id: stardewvalley.smapi.logs.mod-warning-groups
+    claim: 'SMAPI prints named warning groups after the skipped list, each a heading plus a blurb:
+      "Broken mods" (Error), "Patched game code without Harmony fix" (Warn), "Changed save
+      serializer" (Warn), "Patched game code" (Info), "Bypassed safety checks" (Info), "Direct
+      console access" (Trace), "Direct system access" (Debug, paranoid mode only) and "No update
+      keys" (Debug).'
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/Logging/LogManager.cs `LogModWarnings(...)`, the
+      `LogModWarningGroup(...)` calls
+    tags:
+      - log
+      - warnings
+      - harmony
+      - signature
+      - triage
+    detail: '"Patched game code" is how the log alone tells a content pack, a plain C# mod, and a
+      game-patching C# mod apart — genuinely useful triage information no other supported game gives
+      for free. "Changed save serializer" is the one warning with a save-corruption consequence:
+      "They may corrupt your save files, or make them unusable if you uninstall these mods."'
+  - id: stardewvalley.smapi.logs.startup-progress-lines
+    claim: "The startup sequence's own markers are, in order, `Loading mod metadata...` (Debug),
+      `Loading mods...` (Debug), `Launching mods...` (Debug) and `Mods loaded and ready!` (Debug),
+      with one Trace line per mod in between of the form `   {DisplayName} (from {path}\\{EntryDll},
+      ID: {UniqueID}, assembly version: {version})...` or `   {DisplayName} (from {path}, ID:
+      {UniqueID}) [content pack]...`."
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/SCore.cs, the `Monitor.Log` calls in `LoadMods(...)` and
+      around it
+    tags:
+      - log
+      - startup
+      - signature
+      - success
+      - inventory
+    detail: "These Trace lines are the only place in the log where a mod's display name, folder path,
+      UniqueID and assembly version appear together, so they are the best source for a log-derived
+      inventory — better than the Info-level `Loaded N mods:` block. A failed mod's line is followed
+      by `      Failed: {ErrorDetails ?? Error}`."
+  - id: stardewvalley.smapi.logs.loose-files-error
+    claim: Files placed directly in `Mods/` rather than in a per-mod subfolder produce the Error line
+      "Detected mod files directly inside the '{Mods}' folder. These will be ignored. Each mod must
+      have its own subfolder instead.", followed by a Trace line listing them.
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/SCore.cs, in the mod-metadata loading block
+    tags:
+      - log
+      - errors
+      - mods
+      - signature
+      - common-failure
+    detail: One of the most common real installation mistakes and one of the few that SMAPI reports at
+      Error with an actionable instruction, so it should be a high-ranking triage finding.
+  - id: stardewvalley.smapi.logs.crash-and-update-lines
+    claim: "Crash and update lines worth signatures: \"The game crashed last time you played. If it
+      happens repeatedly, see 'get help' on https://smapi.io.\" (Error), \"The game failed to
+      launch: {summary}\" (Error), \"SMAPI failed to initialize: {summary}\" (Error), \"Malicious
+      mod detected.\" (Critical), \"You can update SMAPI to {version}: {url}\" (Alert) and \"You can
+      update {N} mods:\" (Alert)."
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Framework/Logging/LogManager.cs (`HandleMarkerFiles` for the crash
+      line, `MonitorForGame` for the launch failure, and `LogModInfo`'s `LogFatal("Malicious mod
+      detected.")`) and src/SMAPI/Framework/SCore.cs (`CheckForUpdatesAsync(...)` for the two Alert
+      update lines, and the `SMAPI failed to initialize` catch block)
+    tags:
+      - log
+      - crash
+      - update
+      - alert
+      - signature
+    detail: 'Alert is a level mods are told almost never to use — the wiki: "This is mainly meant for
+      SMAPI itself, and should almost never be used by mods" — so an Alert line from a mod source is
+      itself worth reporting.'
+  - id: stardewvalley.smapi.logs.first-party-parser-regexes
+    claim: "SMAPI publishes the parser behind smapi.io/log, and its message-header regex is
+      `^\\[(?<time>\\d\\d[:\\.]\\d\\d[:\\.]\\d\\d) (?<level>[a-z]+)(?: +screen_(?<screen>\\d+))?
+      +(?<modName>[^\\]]+)\\] ` compiled case-insensitively, with thirteen more patterns for the
+      banner, the mod list, the content-pack list, the skipped list and the update lists."
+    status: inferred
+    source: https://github.com/Pathoschild/SMAPI/blob/develop/src/SMAPI.Web/Framework/LogParsing/LogParser.cs,
+      the `MessageHeaderPattern`, `InfoLinePattern`, `ModPathPattern`, `GamePathPattern`,
+      `LogStartedAtPattern`, `ModListStartPattern`, `ModListEntryPattern`,
+      `ContentPackListStartPattern`, `ContentPackListEntryPattern`, `SkippedModListStartPattern`,
+      `SkippedModListEntryPattern`, `ModUpdateListStartPattern`, `ModUpdateListEntryPattern` and
+      `SmapiUpdatePattern` fields
+    tags:
+      - log
+      - parser
+      - signature
+      - smapi-io
+      - tooling
+    detail: "This is the single most valuable artifact for a Stardew `logSignatures` set: fourteen
+      patterns written by SMAPI's own author against the format SMAPI emits, already proven against
+      real uploads. Note the time pattern accepts `.` as well as `:` (some locales), the level is
+      `[a-z]+` with no length assumption (which is how it survives CRITICAL), and there is one or
+      more space before the source."
+  - id: stardewvalley.smapi.logs.multiline-messages-need-reassembly
+    claim: Multi-line messages are ordinary in this log — every stack trace, every `Technical
+      details:\n{ex}`, every `GetLogSummary()` — and their continuation lines carry no prefix at
+      all. SMAPI's parser reassembles them by treating any line that fails the message-header
+      pattern as a continuation of the previous message.
+    status: inferred
+    source: SMAPI develop, src/SMAPI.Web/Framework/LogParsing/LogParser.cs, `GetMessages(string
+      logText)` and the `MessageHeaderPattern` fallthrough
+    tags:
+      - log
+      - parsing
+      - multiline
+      - signature
+      - gotcha
+    detail: A ModWright implementation must do the reassembly before any signature runs. Without it, the
+      contents of a stack trace get scanned as if they were log lines, and a signature anchored on a
+      substring will fire on the wrong thing. What the continuation lines look like exactly —
+      indented, blank-separated or bare — was not established without a real log.
+  - id: stardewvalley.smapi.logs.no-real-sample-exists-here
+    claim: "No real Stardew Valley log was available when these facts were written: the game is not
+      installed on the research machine, `%APPDATA%\\StardewValley` does not exist, and every line
+      shape recorded here comes from source or from the wiki's constructed examples. Every derived
+      log signature is pending a real sample."
+    status: inferred
+    source: "Direct observation 2026-09-11: no `appmanifest_413150.acf` and no `steamapps/common/Stardew
+      Valley` under the machine's one Steam library, and no `%APPDATA%\\StardewValley` directory"
+    tags:
+      - log
+      - provenance
+      - unverified
+      - testing
+      - fixture
+    detail: The corroboration that does exist is strong — the wiki's five example lines agree exactly
+      with the source's format string, and SMAPI's own parser regexes agree with both — but no line
+      from a real run has been matched. The cheapest useful first step in a real run is capturing
+      one title-screen launch's `SMAPI-latest.txt` as a fixture.