Fix some minor issues with the doc

Author: ZakaHaceCosas

docs/about/roadmap.md

@@ -10,12 +10,26 @@ This page also lists all minor and major releases since 2.X. Patches aren't list
 
 ## 4.X
 
+### Version 4.2 (Released)
+
+- [x] Add more system notification prompts.
+  - [x] Whenever a cleaning task (e.g. lint) fails.
+  - [x] When a build finishes.
+- [x] Bring back showing more details into the final report.
+  - [x] Show what features divineProtection prevented (if any).
+  - [x] (New idea) what features failed (if any).
+
+### Version 4.1 (Released)
+
+- [x] Add settings to enable/disable notifications and their thresholds.
+- [x] Always show the cleanup report.
+- [x] Remove verbose flags and live output.
+
 ### Version 4.0 (Released)
 
 - [x] New features
     - [x] `build`, to automate building. Especially useful in JavaScript. This would have a text-config file to define what tasks to run for building a project. It could be used in combination with `release`.
 - [x] `release` support for Cargo.
-- [ ] Dual release support: using the `FnCPF` from the interop layer to allow publishing the same JavaScript package to both npm and jsr. This would be really helpful as jsr downloads do not always work well with npm projects. (_Not done, rescheduled for v4.1_)
 - [x] Rebuild `commit`, so you tell it what files to commit and it:
     - [x] Un-stages anything else to avoid committing randomly staged files.
     - [x] Doesn't require you to stage the files _before_ (making it useless, as `git commit -a -m` is also just one command), and lets you stage files from the own command.

docs/learn/notifications.md

@@ -1,8 +1,16 @@
 # System notifications
 
-By default, `clean`, `migrate`, and `kickstart`, which are considered features that _can_ take a long time, will send a system UI notification if they _do_ take long. Unless you're on DND it should sound - which is the point of it. They're sent so you can safely move away from the terminal and know when we're done, so you can get back to whatever's next as soon as possible.
+By default, features considered as ones that _can_ take a long time, will send a system UI notification if they _do_ take long. Unless you're on Do Not Disturb or something, they should sound - which is the point of it. They're sent so you can safely move away from the terminal and know when we're done, so you can get back to whatever's next as soon as possible.
 
-These notifications are fired if the running task took more than 30 seconds to complete. This threshold can be disabled, so they're shown even if it takes 1 second. In future versions you'll be able to customize the threshold.
+We currently enable this for the following features:
+
+- `clean` (on finish)
+- `build` (on finish)
+- `migrate` (on finish)
+- `kickstart` (on finish)
+- `clean` (on error; remember errors don't stop execution here)
+
+On finish notifications are fired if the running task took more than 30 seconds to complete. This threshold can be disabled, so they're shown even if it takes 1 second. In future versions you'll be able to customize the threshold.
 
 Notifications are enabled by default, but can be disabled if you don't like them.
 

docs/manual/migrate.md

@@ -1,6 +1,6 @@
 # Using FuckingNode: Migrate a project
 
-> `fuckingnode migrate <project> <target>`, or `fklaunch <project> <target>`
+> `fuckingnode migrate <target> [project]`, or `fkmigrate <target> [project]`
 
 The `migrate` command automatically migrates your project from one JS stack to another. For example, from npm to Bun, or from npm to pnpm, or from npm to anything better.
 
@@ -13,7 +13,7 @@ As this can take time, **if it takes long, you'll receive a [system notification
 Just run the following:
 
 ```bash
-fuckingnode migrate <TARGET> <PROJECT>
+fuckingnode migrate <TARGET> [PROJECT]
 ```
 
 `TARGET` is the target package manager (the one to migrate to), can be either npm or pnpm or yarn or deno or bun. `PROJECT` is optional, specifies what project to be migrated, if not provided the CWD is used.

docs/manual/usage.md

@@ -16,7 +16,7 @@ fuckingnode clean <PROJECT | --> <INTENSITY | --> [--update] [--lint] [--pretty]
 
 When executed with no arguments, it'll do a cleanup using the default intensity (which is `normal` and can be changed from the [settings](configuration.md#settings)) across all of your projects.
 
-It'll iterate through all of your projects and clean them, showing status updates one by one in the terminal. Once it ends, a report is shown, telling how much time did it take us to clean each individual project. **You'll receive a [system notification](../learn/notifications.md) once done,** so you can switch tabs and focus on something else - you'll know when to come back.
+It'll iterate through all of your projects and clean them, showing status updates one by one in the terminal. Once it ends, a report is shown, telling how much time did it take us to clean each individual project, as well as what features were prevented by divine protection and what features errored, if any. **You'll receive a [system notification](../learn/notifications.md) once done,** so you can switch tabs and focus on something else - you'll know when to come back.
 
 ## Cleaner intensities, explained