Feat/fix content err

[MarvelFisher]

Summary by CodeRabbit

• Documentation

  • Updated network performance documentation. The latest block tag confirmation timing has been revised from an estimated 2–4 seconds to 0.3 seconds, reflecting actual sequencer performance and providing more accurate expectations.

• Chores

  • Updated webpack dependency to version 5.105.4.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	pre-rail	93cc559	Apr 28 2026, 07:58 AM

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request contains two independent modifications: (1) a documentation update reducing the timing estimate for the latest block tag from 2–4 seconds to 0.3 seconds, and (2) a pnpm dependency override pinning webpack to version 5.105.4.

Changes

Cohort / File(s)	Summary
Documentation Timing Update docs/how-morph-works/general-protocol-design/3-transaction-statuses-on-morph-mainnet.md	Updates the timing estimate for the "sequencer confirmed / unsafe" (latest block tag) from 2–4 seconds to 0.3 seconds.
Dependency Override package.json	Adds a pnpm-specific dependency override to force webpack resolution to version 5.105.4 across all packages (direct and transitive).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• fix: add time within for safe, finized #124: Introduced the 2–4 second timing estimate for latest that this PR now updates to 0.3 seconds.
• update withdaw img and fix tx status desc #143: Makes the identical documentation change to the L2 latest tag timing estimate.
• feat: add transaction statues docs #123: Created the underlying documentation file now being updated with the new timing value.

Suggested reviewers

• twcctop
• tomatoishealthy

Poem

🐰 Three tenths of a second flies,
The latest block tag magnifies!
Webpack locked and tight in place,
Morph builds with steady grace—
Faster chains, stronger tools,
The rabbit hops with new rules! ⚡📦

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Feat/fix content err' is vague and does not clearly describe the actual changes made in the pull request, which involve updating a timing estimate in documentation and adding a webpack version override in package.json.	Revise the title to be more specific and descriptive, such as 'Update sequencer confirmation timing estimate and add webpack version override' to clearly convey the main changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/fix_content_err

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (2)

docs/how-morph-works/general-protocol-design/3-transaction-statuses-on-morph-mainnet.md (1)

27-27: Consider aligning the worst-case documentation with lines 28–29.

The qualifier "Typically" is already present, and the measurement context (L2 block production time) supports the ~0.3 second claim. However, lines 28–29 include "up to X in the worst case" scenarios, while line 27 does not. For consistency, either add a worst-case bound here or clarify why one is not applicable for the sequencer-confirmed state.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@docs/how-morph-works/general-protocol-design/3-transaction-statuses-on-morph-mainnet.md`
at line 27, The "Sequencer confirmed / unsafe (`latest`)" line currently states
"Typically within 0.3 seconds" but omits a worst-case bound unlike lines 28–29;
update the "Sequencer confirmed / unsafe (`latest`)" bullet to either add an
explicit worst-case latency (e.g., "Typically within 0.3 seconds, up to X
seconds in the worst case") or add a parenthetical explanation why a worst-case
bound is not applicable for the sequencer-confirmed state, ensuring the update
references the exact heading "Sequencer confirmed / unsafe (`latest`)" so the
change is consistent with the other status bullets.

package.json (1)

54-58: Add packageManager field to enforce pnpm and guard against accidental npm/yarn installs.

The pnpm.overrides at line 54 is pnpm-specific. While the Makefile build targets enforce pnpm usage, adding "packageManager": "pnpm@X.X.X" to package.json provides explicit toolchain enforcement that prevents developers from accidentally using npm or yarn directly. Consider also documenting this in the README setup instructions.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` around lines 54 - 58, Add a "packageManager" field to
package.json to lock the repository to pnpm (e.g., "packageManager":
"pnpm@X.Y.Z") so pnpm-specific fields like the existing pnpm.overrides are
enforced and accidental npm/yarn installs are prevented; pick the pnpm version
that matches your CI/Makefile/lockfile, add the field at the top-level of
package.json, and update README setup instructions to state the required pnpm
version and how to install it.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In
`@docs/how-morph-works/general-protocol-design/3-transaction-statuses-on-morph-mainnet.md`:
- Line 27: The "Sequencer confirmed / unsafe (`latest`)" line currently states
"Typically within 0.3 seconds" but omits a worst-case bound unlike lines 28–29;
update the "Sequencer confirmed / unsafe (`latest`)" bullet to either add an
explicit worst-case latency (e.g., "Typically within 0.3 seconds, up to X
seconds in the worst case") or add a parenthetical explanation why a worst-case
bound is not applicable for the sequencer-confirmed state, ensuring the update
references the exact heading "Sequencer confirmed / unsafe (`latest`)" so the
change is consistent with the other status bullets.

In `@package.json`:
- Around line 54-58: Add a "packageManager" field to package.json to lock the
repository to pnpm (e.g., "packageManager": "pnpm@X.Y.Z") so pnpm-specific
fields like the existing pnpm.overrides are enforced and accidental npm/yarn
installs are prevented; pick the pnpm version that matches your
CI/Makefile/lockfile, add the field at the top-level of package.json, and update
README setup instructions to state the required pnpm version and how to install
it.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8ee3ec22-19e7-4f2d-86b2-28dff2a6c074

📥 Commits

Reviewing files that changed from the base of the PR and between 6e1e554 and 93cc559.

⛔ Files ignored due to path filters (1)

• assets/docs/protocol/general/bridge/withdraw.png is excluded by !**/*.png

📒 Files selected for processing (2)

• docs/how-morph-works/general-protocol-design/3-transaction-statuses-on-morph-mainnet.md
• package.json