Fix link to engine docs (#167346)

docs/README.md

@@ -14,7 +14,7 @@ If you intend to contribute to Flutter, welcome! You are encouraged to start wit
 * [Cherrypick process](./releases/Flutter-Cherrypick-Process.md)
 * [Closing issues](./contributing/issue_hygiene/README.md#closing-issues)
 * [Dashboards](./infra/Dashboards.md)
-* [Debugging a broken engine autoroll](./engine/Debugging-the-engine.md#bisecting-a-roll-failure)
+* [Debugging a broken engine autoroll](../engine/src/flutter/docs/Debugging-the-engine.md#bisecting-a-roll-failure)
 * [Deprecations](./contributing/Tree-hygiene.md#deprecations)
 * [Design documents](./contributing/Design-Documents.md)
 * [Discord](./contributing/Chat.md)
@@ -31,7 +31,7 @@ If you intend to contribute to Flutter, welcome! You are encouraged to start wit
 * [Style guide for Flutter repo](./contributing/Style-guide-for-Flutter-repo.md)
 * [Submitting code, process for](./contributing/Tree-hygiene.md#overview)
 * [Support levels, definitions of](./about/Values.md#support)
-* [Symbolicating stack traces](./engine/Crashes.md)
+* [Symbolicating stack traces](../engine/src/flutter/docs/Crashes.md)
 * [Threading in the Engine](./about/The-Engine-architecture.md#threading)
 * [When will my bug be fixed?](./contributing/issue_hygiene/README.md#when-will-my-bug-be-fixed)
 * [Security best practices](./infra/Security.md#best-practices)

docs/contributing/Setting-up-the-Framework-development-environment.md

@@ -13,7 +13,7 @@
    Verify that `adb` is in your [PATH](https://en.wikipedia.org/wiki/PATH_(variable)) (that `which adb` prints sensible output).
 
    If you're
-   [also working on the Flutter engine](../engine/contributing/Setting-up-the-Engine-development-environment.md),
+   [also working on the Flutter engine](../../engine/src/flutter/docs/contributing/Setting-up-the-Engine-development-environment.md),
    you can use the copy of the Android platform tools in
    `.../engine/src/third_party/android_tools/sdk/platform-tools`.
 

docs/contributing/Tree-hygiene.md

@@ -140,7 +140,7 @@ feel empowered to ask for tests.
 ## Using git
 
 Assuming your environment has been configured according to the instructions in
-[Setting up the Engine development environment](../engine/contributing/Setting-up-the-Engine-development-environment.md),
+[Setting up the Engine development environment](../../engine/src/flutter/docs/contributing/Setting-up-the-Engine-development-environment.md),
 [Setting up the Framework development environment](Setting-up-the-Framework-development-environment.md), or
 [Setting up the Packages development environment](../ecosystem/contributing/Setting-up-the-Packages-development-environment.md),
 follow these steps to start working on a patch:

docs/contributing/testing/Running-and-writing-tests.md

@@ -47,7 +47,7 @@ runs them, run `dart dev/bots/test.dart` and `dart --enable-asserts dev/bots/ana
 
 ### Locally built engines
 
-If you've built your own flutter engine (see [Setting up the Engine development environment](../../engine/contributing/Setting-up-the-Engine-development-environment.md)), you
+If you've built your own flutter engine (see [Setting up the Engine development environment](../../../engine/src/flutter/docs/contributing/Setting-up-the-Engine-development-environment.md)), you
 can pass `--local-engine` to change what flutter shell `flutter test` uses. For example,
 if you built an engine in the `out/host_debug_unopt` directory, you can use:
 
@@ -120,8 +120,8 @@ The following is an example of what running the local engine command might look
 
 The above command would use the local Flutter engine located at `/Users/myname/flutter/engine` to execute the `external_ui_integration_test` test on an Android emulator, which is why the `android_debug_unopt_x86` version of the engine is used.
 
-Note that some tests may require `profile` mode instead of `debug` mode when running with local engine. Make sure to pass in the correct local engine. See [Compiling the engine](../../engine/contributing/Compiling-the-engine.md) for more details.
+Note that some tests may require `profile` mode instead of `debug` mode when running with local engine. Make sure to pass in the correct local engine. See [Compiling the engine](../../../engine/src/flutter/docs/contributing/Compiling-the-engine.md) for more details.
 
 ## For the engine
 
-See the [Testing the engine](../../engine/testing/Testing-the-engine.md) wiki.
+See the [Testing the engine](../../../engine/src/flutter/docs/testing/Testing-the-engine.md) wiki.

docs/infra/Rolling-Dart.md

@@ -49,12 +49,12 @@ If the script completes without errors, move on to step 10 in the next section t
 
 1. Set up your Engine and Flutter environments by following the instructions described in the pages
    linked to from [our contributing guide](../../CONTRIBUTING.md).
-2. Build the engine according to the instructions on the [Compiling the engine](../engine/contributing/Compiling-the-engine.md) page.
+2. Build the engine according to the instructions on the [Compiling the engine](../../engine/src/flutter/docs/contributing/Compiling-the-engine.md) page.
 3. Select a target Dart revision, typically use the [latest revision](https://github.com/dart-lang/sdk/commits/main). Check that the tests for that revision have all passed (all green) on the [Dart buildbot](https://ci.chromium.org/p/flutter/g/engine/console) and the [Internal Dart Flutter buildbot](https://ci.chromium.org/p/dart/g/flutter/console).
 4. Create a PR (see [Tree hygiene](../contributing/Tree-hygiene.md)) that updates `dart_revision` in [DEPS](../../DEPS) to your selected revision. Invoke `gclient sync` in the src directory to ensure versions corresponding to the DEPS file are synced up.
 5. Update all Dart-dependent DEPS entries using [`create_updated_flutter_deps.py`](../../engine/src/tools/dart/create_updated_flutter_deps.py) script. In case script complains that dart dependency was removed, remove entry from flutter DEPS file manually. If the list of library source files or patch files is modified, update the file [`libraries.yaml`](../../engine/src/flutter/lib/snapshot/libraries.yaml) and regenerate the corresponding json file.
 6. Invoke `gclient sync` in the src directory to ensure versions corresponding to the DEPS file are synced up.
-7. Build the debug, profile, and release versions of the engine, following the normal [Compiling the engine](../engine/contributing/Compiling-the-engine.md) instructions. You will need to build the host versions of the engine too. Here is a script with the build commands:
+7. Build the debug, profile, and release versions of the engine, following the normal [Compiling the engine](../../engine/src/flutter/docs/contributing/Compiling-the-engine.md) instructions. You will need to build the host versions of the engine too. Here is a script with the build commands:
 
 ```bash
 #!/bin/bash -e
@@ -88,7 +88,7 @@ cd $FLUTTER_HOME/packages/flutter
 flutter test --local-engine=host_debug --local-engine-host=host_debug
 ```
 
-> See [Running a Flutter app with a local engine](../engine/Debugging-the-engine.md#running-a-flutter-app-with-a-local-engine) for more information.
+> See [Running a Flutter app with a local engine](../../engine/src/flutter/docs/Debugging-the-engine.md#running-a-flutter-app-with-a-local-engine) for more information.
 
 8. Make sure your path contains `engine/src/third_party/dart/tools/sdks/dart-sdk/bin`, run the script `flutter/ci/licenses.sh` in the src directory, update `flutter/ci/licenses_golden/licenses_third_party` by copying `out/license_script_output/licenses_third_party` into it. Include this change in your pull request.
    **If any licenses changed, make sure to also update the actual `LICENSE` file.**