modwright 0.1.0

package/knowledge/stardewvalley/game.versions.yaml

@@ -0,0 +1,202 @@
+game: stardewvalley
+topic: game.versions
+title: Game versions, the version axes, and the 1.6 data-format break
+facts:
+  - id: stardewvalley.game.versions.current-is-1-6-15
+    claim: The current Stardew Valley release is 1.6.15, published 20 December 2024 — twenty-one months
+      before this research. The preceding chain is 1.6.14 (12 November 2024), 1.6.13 (8 November
+      2024), 1.6.12 (7 November 2024), 1.6.11, 1.6.10, 1.6.9, and back to 1.6 in March 2024.
+    status: community
+    source: 'https://stardewvalleywiki.com/Version_History (read 2026-09-11): "Stardew Valley 1.6.15 was
+      released on 20 December 2024."'
+    verified_on: 1.6.15
+    tags:
+      - version
+      - cadence
+      - stability
+      - compat
+    detail: This is the most consequential fact about the surface. Every other game ModWright supports
+      is mid-motion; this one has been stationary for nearly two years, so a compat matrix has one
+      live row, the compatibility list is mature rather than churning, and work built now will not
+      rot before the game is installed.
+  - id: stardewvalley.game.versions.one-axis-no-marketing-split
+    claim: Stardew Valley has one public version axis. `1.6.15` is what the patch notes, the wiki and
+      the community all use, so it is the axis `verified_on` is written on, and
+      `InstalledComponent.marketingVersion` should stay undefined.
+    status: inferred
+    source: https://stardewvalleywiki.com/Version_History
+    tags:
+      - version
+      - axis
+      - verified-on
+      - compat
+      - marketingversion
+    detail: There is a second number in the install — the executable's assembly version, which SMAPI
+      reads only to decide whether a folder is a pre-1.6 install — but its relationship to `1.6.15`
+      was not established without the game, so a surface must not present it as the game version.
+  - id: stardewvalley.game.versions.smapi-floor-is-1-6-14
+    claim: Current SMAPI requires game version 1.6.14 or later and declares no maximum, so the installed
+      1.6.15 sits one patch above the floor with unbounded headroom.
+    status: inferred
+    source: 'SMAPI develop, src/SMAPI/Constants.cs: `MinimumGameVersion = new GameVersion("1.6.14")` and
+      `MaximumGameVersion = null`'
+    tags:
+      - version
+      - smapi
+      - compat
+      - rule
+      - floor
+    related:
+      - id: stardewvalley.smapi.loader.version-and-game-floor
+        detail: the same two constants, stated there from SMAPI's side
+  - id: stardewvalley.game.versions.1-7-is-announced-undated
+    claim: Stardew Valley 1.7 has been announced — new marriage candidates Clint and Sandy, an overhaul
+      of children, a possible farm map editor — with no release date and no window, and the modding
+      wiki also lists an upcoming 1.6.16.
+    status: community
+    source: https://gameinformer.com/2026/02/26/you-can-marry-clint-and-sandy-in-the-17-update-for-stardew-valley-concernedape-announces
+      and https://www.pcgamer.com/games/life-sim/stardew-valley-1-7-guide/ (both read 2026-09-11);
+      the two upcoming migration guides are listed on https://stardewvalleywiki.com/Modding:Index as
+      "Stardew Valley 1.6.16 — upcoming" and "Stardew Valley 1.7 — upcoming"
+    tags:
+      - version
+      - roadmap
+      - compat
+      - advisory
+    detail: The wiki reserving a 1.6.16 migration page means the community expects one more point
+      release before 1.7, and those pages are where the next round of breaking changes will be
+      written down before they ship — a cheap thing for a compat refresh to watch. ConcernedApe has
+      also said he is taking more of a creative-director role on Stardew so he can focus on his next
+      title, which argues against a near-term date.
+  - id: stardewvalley.game.versions.1-6-moved-data-to-string-keyed-models
+    claim: Stardew Valley 1.6 replaced the old delimited-string data assets with string-keyed model
+      lookups. `Data/Objects`, for example, "consists of a string -> model lookup, where the key is
+      the unqualified item ID" and the value is an object with named fields.
+    status: community
+    source: https://stardewvalleywiki.com/Modding:Object_data (read 2026-09-11), "Data format"
+    tags:
+      - data
+      - "1.6"
+      - format
+      - index
+      - contentpatcher
+    detail: 'This is why a Content Patcher `EditData` on `Data/Objects` in 1.6 sets named fields
+      (`"Fields": {"MossSoup": {"Price": 80}}`) rather than editing a slash-delimited string, and
+      why a field-name validator is meaningful at all. Content Patcher ships
+      `Migration_2_0.ForObjectInformation.cs` and a dozen siblings to rewrite pre-1.6 packs into the
+      new shape at load time.'
+  - id: stardewvalley.game.versions.unique-string-ids-convention
+    claim: 1.6 introduced unique string IDs throughout the game, and the documented convention is to
+      namespace every new content ID with the mod's own unique ID —
+      `Example.PufferchickMod_PufferchickPlushy`, or `{{ModId}}_PufferchickPlushy` in a Content
+      Patcher pack — using only alphanumerics, underscore and dot.
+    status: community
+    source: "https://stardewvalleywiki.com/Modding:Migrate_to_Stardew_Valley_1.6 (read 2026-09-11):
+      \"Use namespaced IDs prefixed with your mod's unique ID for all new content ... This
+      eliminates ID conflicts between mods, and makes it easy (for both troubleshooters and mod
+      code) to identify which mod added a particular content.\" and \"Only use alphanumeric (a-z,
+      A-Z, 0-9), underscore (_), and dot (.) characters in string IDs. This is important because
+      they're often used in places where some characters have special meaning (like file names or
+      game state queries).\""
+    tags:
+      - "1.6"
+      - ids
+      - convention
+      - validator
+      - contentpatcher
+      - conflict
+    detail: "Directly checkable from a content pack alone, because the pack's own `manifest.json` is
+      right there: every key a patch adds to a `Data/*` asset should start with the pack's UniqueID
+      or with `{{ModId}}_`. A `warn`-severity rule, since a pack may legitimately edit a vanilla
+      key."
+  - id: stardewvalley.game.versions.qualified-item-ids
+    claim: Items carry a type prefix in their qualified ID — objects are `(O)`, corresponding to
+      `ItemRegistry.type_object` in C# — so `(O)MossSoup` is the qualified form of the
+      `Data/Objects` key `MossSoup`.
+    status: community
+    source: 'https://stardewvalleywiki.com/Modding:Object_data (read 2026-09-11): "They have item type
+      (O) (or ItemRegistry.type_object in C# code), their data in Data/Objects, their icon sprites
+      in Maps/springobjects or TileSheets/Objects_2 by default, and their code in
+      StardewValley.Object."'
+    tags:
+      - "1.6"
+      - ids
+      - items
+      - index
+      - keying
+    detail: An index for this game should key on the qualified form with the unqualified id and display
+      name as secondary keys, because the qualified form is what 1.6 content and item queries use.
+      The console command `player_add` accepts it directly (`player_add (O)246`).
+  - id: stardewvalley.game.versions.smapi-4-0-changed-the-content-api
+    claim: SMAPI 4.0 (March 2024) replaced `IAssetLoader`/`IAssetEditor` with the `AssetRequested`
+      event, split `helper.Content` into `helper.ModContent` and `helper.GameContent`, made asset
+      names locale-sensitive, and added load and edit priorities. It shipped alongside Stardew
+      Valley 1.6.
+    status: community
+    source: 'https://stardewvalleywiki.com/Modding:Migrate_to_SMAPI_4.0 (read 2026-09-11): "The
+      IAssetLoader and IAssetEditor interfaces no longer exist. Both have been replaced by the
+      AssetRequested event" and "Asset names are no longer locale-agnostic. For example,
+      Data/Bundles and Data/Bundles.fr-FR are not equivalent."'
+    tags:
+      - smapi
+      - api
+      - "4.0"
+      - migration
+      - locale
+      - csharp
+    detail: "Relevant to a C# mod validator and to any advice about content interception: a mod still
+      using `helper.Content` or the old interfaces will not compile against current SMAPI. The
+      locale change is the one that bites content packs too, via `TargetLocale`."
+  - id: stardewvalley.game.versions.content-patcher-is-most-of-the-ecosystem
+    claim: Content Patcher is "the backbone for 41.1% of all mods" according to SMAPI's own 4.0
+      migration page — a period statement predating the March 2024 release of SMAPI 4.0, not a
+      current figure.
+    status: community
+    source: "https://stardewvalleywiki.com/Modding:Migrate_to_SMAPI_4.0 (read 2026-09-11): \"it's the
+      basis for Content Patcher which is now the backbone for 41.1% of all mods\""
+    tags:
+      - contentpatcher
+      - ecosystem
+      - prioritisation
+      - undated
+    detail: "The figure is undated on the page and should be treated as an order-of-magnitude statement,
+      not a metric. Its use here is only to justify prioritising the content-pack validator family
+      over the C# one: a large fraction of this ecosystem's mods are JSON, which is exactly what a
+      pre-build checker can check."
+  - id: stardewvalley.game.versions.no-eula-text-was-located
+    claim: No Stardew Valley EULA or terms-of-service text was located in any source read for this
+      research, so nothing is claimed in either direction about decompilation, asset extraction or
+      redistribution.
+    status: inferred
+    source: ModWright research
+    tags:
+      - legal
+      - licence
+      - unsourced
+      - gap
+    detail: This is an absence of evidence, recorded as such and not as permission. The one adjacent
+      operational norm that *is* sourced is that the ecosystem's own unpacking tool (StardewXnbHack)
+      runs against the user's own install and writes into it, never redistributing game content —
+      the same design the Valheim publicizer uses, and the same inference is available here.
+  - id: stardewvalley.game.versions.data-asset-doc-index
+    claim: The wiki documents roughly forty data assets individually — Items (with per-type pages for
+      big craftables, boots, furniture, hats, mannequins, objects, pants, shirts, tools, trinkets,
+      wallpaper and flooring, weapons), Crops, Fruit trees, Giant crops, Item queries, Machines,
+      Recipes, Wild trees, Maps, Farm data, Festivals, Fish, Location contexts, Locations, Movie
+      theater, Museum data, Passive festivals, Weather, Buffs, Buildings, Bundles, Farmer sprite,
+      Fences, Floors and paths, Fish ponds, Garbage cans, Jukebox tracks, Lost items shop, Mail,
+      Minecarts, Monster eradication goals, Phone calls, Shops, Special items and powers, Special
+      orders, Tailoring, Animals, Monsters, Pets, and the NPC pages for dialogue, events, gift
+      tastes, quests and schedules.
+    status: community
+    source: https://stardewvalleywiki.com/Modding:Index (read 2026-09-11), the "Specific topics" list
+    tags:
+      - index
+      - data
+      - documentation
+      - wiki
+      - schema
+    detail: "This list is the table of contents for a schema-level vanilla index that needs no game:
+      each page states its asset's field names, types and defaults. What it does not give is the
+      *values* — whether `MossSoup` exists, what `Universal_Love` currently contains — which need a
+      StardewXnbHack run against a real install."

package/knowledge/stardewvalley/install.layout.yaml

@@ -0,0 +1,277 @@
+game: stardewvalley
+topic: install.layout
+title: Where Stardew Valley installs, how SMAPI sits beside it, and where the data folder lives
+facts:
+  - id: stardewvalley.install.layout.steam-app-id
+    claim: Stardew Valley is Steam app `413150`, and its `steamapps/common` folder name is `Stardew
+      Valley` — with a space.
+    status: inferred
+    source: 'SMAPI develop, src/SMAPI.Toolkit/Framework/GameScanning/GameScanner.cs: `private const
+      string SteamAppId = "413150";` and the path literal `steamapps\common\Stardew Valley`
+      (https://github.com/Pathoschild/SMAPI/blob/develop/src/SMAPI.Toolkit/Framework/GameScanning/GameScanner.cs)'
+    tags:
+      - steam
+      - appid
+      - detect
+      - install
+      - folder-name
+    detail: 'The space matters: `findInSteam(["Stardew Valley"])` is correct and
+      `findInSteam(["StardewValley"])` finds nothing. The no-space spelling `StardewValley.exe` does
+      exist, but only as the pre-1.5.5 Linux/macOS executable name, not as a folder name.'
+  - id: stardewvalley.install.layout.default-paths
+    claim: "SMAPI's own scanner probes, in order on Windows: registry
+      `HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Steam App 413150` value
+      `InstallLocation`; registry `HKLM\\SOFTWARE\\WOW6432Node\\GOG.com\\Games\\1453375253` value
+      `PATH`; `HKCU\\Software\\Valve\\Steam` value `SteamPath` plus `steamapps\\common\\Stardew
+      Valley` and every library in that Steam's `steamapps\\libraryfolders.vdf`; then under each of
+      `C:\\Program Files` and `C:\\Program Files (x86)` the four paths `GalaxyClient\\Games\\Stardew
+      Valley`, `GOG Galaxy\\Games\\Stardew Valley`, `GOG Games\\Stardew Valley` and
+      `Steam\\steamapps\\common\\Stardew Valley`; then `<drive>:\\Program
+      Files\\ModifiableWindowsApps\\Stardew Valley` for drive letters C through H."
+    status: inferred
+    source: SMAPI develop, src/SMAPI.Toolkit/Framework/GameScanning/GameScanner.cs,
+      `GetDefaultInstallPaths()` and the `registryKeys` dictionary
+    tags:
+      - detect
+      - install
+      - registry
+      - steam
+      - gog
+      - xbox
+      - gamepass
+    detail: On Linux it is `$HOME/GOG Games/Stardew Valley/game`, then
+      `$HOME/.steam/steam/steamapps/common/Stardew Valley` falling back to
+      `$HOME/.local/share/Steam/steamapps/common/Stardew Valley`, then the Flatpak path
+      `$HOME/.var/app/com.valvesoftware.Steam/data/Steam/steamapps/common/Stardew Valley`. The same
+      branch then yields the two macOS paths, `/Applications/Stardew Valley.app/Contents/MacOS` and
+      `$HOME/Library/Application Support/Steam/steamapps/common/Stardew Valley/Contents/MacOS`. A
+      ModWright `detect` that mirrors this list is transcription, not design.
+  - id: stardewvalley.install.layout.targets-file-override
+    claim: A `stardewvalley.targets` file in the user's home directory (`%USERPROFILE%` on Windows,
+      `$HOME` otherwise) whose `<GamePath>` property names a folder is a first-party install
+      override that both SMAPI's scanner and the NuGet build package honour.
+    status: inferred
+    source: 'SMAPI develop, src/SMAPI.Toolkit/Framework/GameScanning/GameScanner.cs,
+      `GetCustomInstallPaths()`; documented for authors in docs/technical/mod-package.md ("Create a
+      `stardewvalley.targets` file with this content:
+      `<Project><PropertyGroup><GamePath>PATH_HERE</GamePath>...`")'
+    tags:
+      - detect
+      - override
+      - csproj
+      - developer
+      - install
+    detail: On a developer machine this is high-confidence and costs one file read, so it is worth
+      probing before Steam. No such file exists on the machine this research was done on.
+  - id: stardewvalley.install.layout.game-folder-heuristic
+    claim: '"Is this folder a game folder" has five distinct answers, not two. SMAPI decides: `Stardew
+      Valley.dll` present -> Valid; else no `Stardew Valley.exe` and no `StardewValley.exe` ->
+      NoGameFound; else exe assembly version below 1.6 -> LegacyVersion; else no
+      `MonoGame.Framework.dll` -> LegacyCompatibilityBranch; else InvalidUnknown.'
+    status: inferred
+    source: SMAPI develop, src/SMAPI.Toolkit/Framework/GameScanning/GameScanner.cs
+      `GetGameFolderType(DirectoryInfo)`, with the enum documented in
+      src/SMAPI.Toolkit/Framework/GameScanning/GameFolderType.cs
+    tags:
+      - detect
+      - validity
+      - phantom-install
+      - legacy
+    detail: "`LegacyVersion` is documented as \"contains Stardew Valley 1.5.6 or earlier, which isn't
+      compatible with current versions of SMAPI\" and `LegacyCompatibilityBranch` as \"the game's
+      legacy compatibility branch, which backports newer changes to the LegacyVersion format\".
+      Reporting these separately is much more useful than \"not found\", and it avoids the
+      Subnautica 2 phantom-install failure where a folder exists but holds nothing."
+  - id: stardewvalley.install.layout.executables
+    claim: The game ships `Stardew Valley.exe` on Windows and a `StardewValley` shell script on
+      Linux/macOS; SMAPI adds `StardewModdingAPI.exe` (Windows) or a `StardewModdingAPI` binary
+      (Unix) beside it, plus a `StardewModdingAPI.deps.json` copied from `Stardew Valley.deps.json`.
+    status: community
+    source: "SMAPI installer README
+      (https://github.com/Pathoschild/SMAPI/blob/develop/src/SMAPI.Installer/assets/README.txt):
+      \"The `StardewModdingAPI.exe` file should be right next to the game's executable\" and step 3,
+      \"Copy `Stardew Valley.deps.json` in the game folder, and rename the copy to
+      `StardewModdingAPI.deps.json`\""
+    tags:
+      - smapi
+      - executable
+      - install
+      - detect
+      - process-names
+    detail: "Three process names matter for a deploy's game-exit wait: `Stardew Valley`,
+      `StardewModdingAPI`, and `StardewValley` (the Unix launcher after renaming)."
+  - id: stardewvalley.install.layout.unix-rename
+    claim: "On Linux and macOS the SMAPI installer renames the launcher rather than adding a second one:
+      `StardewValley` becomes `StardewValley-original` and `StardewModdingAPI` becomes
+      `StardewValley`, so launching the game normally launches SMAPI."
+    status: community
+    source: SMAPI installer README, manual-install step 4; the same three paths are named in
+      src/SMAPI.Installer/Framework/InstallerPaths.cs as `VanillaLaunchScriptPath`,
+      `BackupLaunchScriptPath` and `UnixSmapiExecutablePath`
+    tags:
+      - smapi
+      - install
+      - unix
+      - detect
+      - launch
+    detail: 'Consequence for `detect`: on Unix, "is SMAPI what will launch" is readable from disk (does
+      `StardewValley-original` exist), and on Windows it is not — see the Steam launch-options
+      fact.'
+  - id: stardewvalley.install.layout.steam-launch-options-are-not-on-disk
+    claim: On Windows, Steam runs SMAPI only if the player pasted a launch-options string of the form
+      `"<path>\StardewModdingAPI.exe" %command%` into Steam's per-game properties. That string lives
+      in Steam's own configuration, not in the game folder, so whether pressing Play will run SMAPI
+      is not determinable from the filesystem.
+    status: community
+    source: 'https://stardewvalleywiki.com/Modding:Installing_SMAPI_on_Windows (read 2026-09-11):
+      "Default for most users is `\"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Stardew
+      Valley\\StardewModdingAPI.exe\" %command%` / The quotes - and %command% - are both necessary,
+      so include them!"'
+    tags:
+      - steam
+      - launch
+      - detect
+      - undeterminable
+      - guidance
+    detail: This is the single most common "my mods do nothing" cause on Windows and it leaves no trace
+      on disk. A surface must report it as undeterminable (architecture rule 2) rather than assert
+      either way. GOG Galaxy uses a hand-written `start.bat` in the game folder instead, which *is*
+      detectable.
+  - id: stardewvalley.install.layout.xbox-path-conflict
+    claim: "Two different Xbox/Game Pass install paths are documented and they were not reconciled:
+      SMAPI's scanner probes `<drive>:\\Program Files\\ModifiableWindowsApps\\Stardew Valley`, while
+      the wiki gives `C:\\XboxGames\\Stardew Valley` and instructs players to install SMAPI into
+      that folder's `Content` subfolder."
+    status: community
+    source: "SMAPI develop GameScanner.cs (in-source comment: \"The Xbox app saves the install path to
+      the registry, but we can't use it here since it saves the internal readonly path (like
+      C:\\Program Files\\WindowsApps\\Mutable\\<package ID>) instead of the mods-enabled path\");
+      versus https://stardewvalleywiki.com/Modding:Player_Guide/Getting_Started (\"Xbox App:
+      C:\\XboxGames\\Stardew Valley\") and
+      https://stardewvalleywiki.com/Modding:Installing_SMAPI_on_Windows (\"Open the Stardew Valley >
+      Content folder\")"
+    tags:
+      - xbox
+      - gamepass
+      - detect
+      - conflict
+      - unresolved
+    detail: Plausibly both are true of the same install reached by different paths, but that was not
+      established. Offer both candidates and report which exists; never hard-code one. The Xbox
+      install also requires renaming `Stardew Valley.exe` and copying `StardewModdingAPI.exe` over
+      it, which must be redone after every game update.
+  - id: stardewvalley.install.layout.mods-folder
+    claim: Mods live in `Mods/` inside the game folder, one subfolder per mod, and SMAPI searches
+      recursively — grouping subfolders are supported, so `Mods/Fruit
+      mods/PineapplesEverywhere/manifest.json` is a valid mod.
+    status: community
+    source: 'https://stardewvalleywiki.com/Modding:Player_Guide/Getting_Started (read 2026-09-11): "Make
+      sure each mod has its own subfolder, without trailing numbers" and "If you have a lot of mods,
+      you can optionally organize them into subfolders. SMAPI will automatically search inside each
+      folder until it finds one with files."; path from src/SMAPI/Constants.cs `DefaultModsPath =
+      Path.Combine(Constants.GamePath, "Mods")`'
+    tags:
+      - mods
+      - modroots
+      - layout
+      - nesting
+    detail: A `list_mods` implementation must walk to arbitrary depth looking for `manifest.json`, not
+      just enumerate immediate subdirectories. The wiki also warns about the
+      `PineapplesEverywhere-1234567890` wrapper folder that mod sites produce, which is a real and
+      common failure.
+  - id: stardewvalley.install.layout.dot-prefix-disables-a-mod
+    claim: Prefixing a mod folder's name with a dot disables it. SMAPI classifies it as
+      `ModType.Ignored` with the reason "ignored folder because its name starts with a dot." and
+      logs "  Skipped {path} (folder name starts with a dot)."
+    status: inferred
+    source: SMAPI develop, src/SMAPI.Toolkit/Framework/ModScanning/ModScanner.cs (`if
+      (folder.Name.StartsWith("."))`) and src/SMAPI/Framework/SCore.cs; documented for players at
+      https://stardewvalleywiki.com/Modding:Player_Guide/Getting_Started
+    tags:
+      - mods
+      - disable
+      - scanning
+      - modroots
+    detail: "The wiki adds the Windows workaround: \"If Windows doesn't let you do that, put a dot at
+      the end too and it'll let you (like `.disabled mods.`).\" A validator should report a
+      dot-prefixed folder as `info`, not an error — it is usually deliberate."
+  - id: stardewvalley.install.layout.smapi-internal-folder
+    claim: SMAPI's own files live in `smapi-internal/` in the game folder
+      (`Constants.InternalFilesPath`), holding `config.json`, `config.user.json`, `metadata.json`,
+      `blacklist.json`, `blacklist-updated.json`, `0Harmony.dll`, `SMAPI.Toolkit.CoreInterfaces.dll`
+      and the `StardewModdingAPI.crash.marker` / `.update.marker` one-shot files.
+    status: inferred
+    source: SMAPI develop, src/SMAPI/Constants.cs (`InternalFilesPath`, `ApiConfigPath`,
+      `ApiUserConfigPath`, `ApiMetadataPath`, `ApiBlacklistPath`, `ApiBlacklistFetchedPath`,
+      `FatalCrashMarker`, `UpdateMarker`) and src/SMAPI.ModBuildConfig/build/smapi.targets (the
+      `HintPath`s into `$(GamePath)\smapi-internal\`)
+    tags:
+      - smapi-internal
+      - config
+      - modroots
+      - compat
+      - never-deploy
+    detail: This is a mod root only in the sense that a mod wrongly shipped into it is visible; it must
+      never be a deploy target and prune must never touch it. `metadata.json` is a direct compat
+      input — it is SMAPI's internal known-broken list, on disk, readable with no network call.
+  - id: stardewvalley.install.layout.config-filename-conflict
+    claim: SMAPI's configuration file is `smapi-internal/config.json` according to the current source,
+      but two wiki pages and Content Patcher's troubleshooting guide still call it
+      `smapi-internal/StardewModdingAPI.config.json`. A detector must probe both names.
+    status: inferred
+    source: SMAPI develop names `config.json` in three places — src/SMAPI/Constants.cs `ApiConfigPath`,
+      src/SMAPI.Installer/Framework/InstallerPaths.cs `ApiConfigPath`, and three log lines in
+      src/SMAPI/Framework/SCore.cs that say "the 'smapi-internal/config.json' file"; versus
+      https://stardewvalleywiki.com/Modding:Modder_Guide/APIs/Logging and
+      https://github.com/Pathoschild/StardewMods/blob/develop/ContentPatcher/docs/author-guide/troubleshooting.md,
+      both of which say `smapi-internal/StardewModdingAPI.config.json`
+    tags:
+      - config
+      - conflict
+      - unresolved
+      - detect
+      - explain-missing
+    detail: Most likely a rename the wiki has not caught up with, but that was not established without
+      an install. Both `explainMissing`'s verbose-logging answer and the load-order override file
+      (`ModsToLoadEarly`) depend on finding this file, so getting it wrong silently disables both.
+  - id: stardewvalley.install.layout.data-folder
+    claim: The per-user data folder is `%APPDATA%\StardewValley`, with saves in `Saves/` and SMAPI logs
+      in `ErrorLogs/`. It is created the first time the game runs, which is why SMAPI's install
+      guide's first step is to run the game once without SMAPI.
+    status: inferred
+    source: 'SMAPI develop, src/SMAPI/Constants.cs: `DataPath =
+      Path.Combine(Environment.GetFolderPath(SpecialFolder.ApplicationData), "StardewValley")`,
+      `SavesPath = Path.Combine(DataPath, "Saves")`, `LogDir = Path.Combine(DataPath, "ErrorLogs")`;
+      the first-run instruction is from
+      https://stardewvalleywiki.com/Modding:Installing_SMAPI_on_Windows ("Run the game without SMAPI
+      at least once (so it can do first-time setup).")'
+    tags:
+      - appdata
+      - logs
+      - saves
+      - explain-missing
+    detail: "Two `explainMissing` answers fall out of this: no `%APPDATA%\\StardewValley` at all means
+      the game has never been run; the folder present with no `SMAPI-*.txt` inside `ErrorLogs` means
+      SMAPI is installed but was not launched. Those demand opposite next actions. SMAPI also
+      exposes `show_data_files` and `show_game_files` console commands that open these two folders."
+  - id: stardewvalley.install.layout.mods-path-argument
+    claim: "`StardewModdingAPI.exe --mods-path <path>` (or the `SMAPI_MODS_PATH` environment variable)
+      relocates the mod folder only; the loader stays in the game folder. A relative path is
+      combined with the game path."
+    status: inferred
+    source: 'SMAPI develop, src/SMAPI/Program.cs `Start(string[] args)`: `int pathIndex =
+      Array.LastIndexOf(args, "--mods-path") + 1;` and `modsPath =
+      !string.IsNullOrWhiteSpace(rawModsPath) ? Path.Combine(Constants.GamePath, rawModsPath) :
+      Constants.DefaultModsPath;`'
+    tags:
+      - launch
+      - mods
+      - deploy
+      - profiles
+      - developer
+    detail: "This is the Stardew analogue of an r2modman profile, and it is much weaker: it does not
+      relocate the loader and it is chosen at launch, so ModWright can offer a declared
+      `--mods-path` folder as a second deploy target but must never assert which mod folder is live.
+      The other documented arguments are `--developer-mode`, `--developer-mode-off` and
+      `--no-terminal`, with `SMAPI_DEVELOPER_MODE` and `SMAPI_NO_TERMINAL` as environment
+      equivalents."