* improve drippie & faucet tests and coverage

* Update packages/contracts-bedrock/test/periphery/faucet/Faucet.t.sol
Co-authored-by: smartcontracts <kelvin@optimism.io>

* Update packages/contracts-bedrock/test/periphery/faucet/Faucet.t.sol
Co-authored-by: smartcontracts <kelvin@optimism.io>

---------
Co-authored-by: smartcontracts <kelvin@optimism.io>

* ctb: Fix Holocene upgrade script

* improve README

* pass deploy-config as parameter to just run, other improvements

* remove commented-out variables

Co-authored-by: Michael Amadi <amadimichaeld@gmail.com>

Moves the task for linting test names to after the tests job so
that the contract artifacts actually exist. We don't compile
everything ahead of time and rely on forge test to do the
compilation in an effort to cut down total compile time.

lint-forge-tests-check-no-build was causing issues in CI because
it was running as part of contracts-bedrock-checks which depends
on contracts-bedrock-build. contracts-bedrock-build builds the
contract files EXCEPT for tests whenever contracts-bedrock has
changed. This means that contracts-bedrock-build would not build
any test files and therefore lint-forge-tests-check-no-build would
not find any test files to check and the job would do nothing.
However, when contracts-bedrock is NOT changed, the build job gets
the full set of artifacts INCLUDING test artifacts from the cache.
This would trigger the full check to actually be run and it would
properly fail.

This PR moves that particular check into contracts-bedrock-tests
so that it's guaranteed to have all of the compiled contracts.

The tests in the txmgr queue were asserting that calls complete within a certain time window. This was causing flakes, particularly when the CI runner was under load. Generally we should avoid tests that use fixed durations as a way of asserting that code functions correctly.

* op-node: log mgasps across block processing lifecycle

* op-node: add 'import_time' field to block processing log

* op-node: make log message more descriptive

* op-node: log legacy codepath for InsertUnsafePayload

* op-node: include final ForkchoiceUpdate in block insertion time

* op-node: remove unused BuildTime field from events

* op-node: encapsulate log logic in TryUpdateEngineEvent methods

* op-node: linter fix

* op-node: add comment and adjust sync log wording

* op-node: fix BlockHash, BlockNumber in log

* op-node: seq add BuildStarted to PayloadProcessEvent

* op-node: refactor getBlockProcessingMetrics, protect against divide-by-zero

This reverts commit 8f5c20ee.

* fix a deadlock

* add comment

* improve DeployerWhitelist test

* fix L1BlockNumber fallback test

* fixes

* cannon: Port go map tests

* cannon: Port pool_test.go

* cannon: Port a few more mutex tests

* cannon: Port waitgroup_test.go

* cannon: Port oncefunc_test.go (in progress)

* cannon: Port atomic_test.go (in progress)

* cannon: Port value_test.go (in progress)

* cannon: Fix atomic tests by using a test mock

* cannon: Fix test fail behavior

* cannon: Move test util to a shared module

* cannon: Use common testutil throughout

* cannon: Fix failing tests

* cannon: Add sanity check test program for test runner utils

* cannon: Add more util tests, fix step counts

* cannon: Rename test util method

* cannon: Fix panic, error handling in testutil

* cannon: Dedupe test running code

* cannon: Simplify testutil interface

* cannon: Mark mt tests as slow

* cannon: Cut debugging code from test

* cannon: Validate gc complete output

* cannon: Synchronize access to bool values

* build: add just modules

A lot of our build recipes share similar structures. Move some of
these to modules so we can control them centrally.

* build: add Makefile deprecation helper

This allows us to implement deprecated Makefiles as:

  DEPRECATED_TARGETS := ...
  include ../just/deprecate.mk

* build(docker): add just modules to docker context

We need to make sure our build framework is included in the docker build
context.
Also make sure just is part of the builder image.

* build(op-batcher): migrate build to just

This is adding op-program/v1.4.0-rc.1 with absolute prestate hash
0x03925193e3e89f87835bbdf3a813f60b2aa818a36bbe71cd5d8fd7e79f5e8afe
to the releases.json file.

This release contains Sepolia Holocene activation times for
OP, Base, Mode, Zora, BUT NOT Metal.

Test hard fork offset overrides
Co-authored-by: Vinod Damle <vinod@oplabs.co>

* make riscv compile without the optimizer turned on

* bump riscv.sol

* bump riscv.sol

- Enables support for deploying tagged versions against new chains, but behind a huge warning that requires user input to bypass. Since our tagged release versions do not contain all implementations, using op-deployer in this way will deploy contracts that haven't been governance approved. Since this workflow is useful for development but bad for prod, I've added support for it but users have to bypass a large warning that describes the risks.
- Validates the hashes of tagged version artifacts after downloading them. This prevents users from downloading tampered versions of the artifacts from GCS.

* op-node: Create metrics to record if sequencer is active

* op-node: Update transactions_sequenced_total metric

---------
Co-authored-by: protolambda <proto@protolambda.com>

Bumps [github.com/kurtosis-tech/kurtosis/api/golang](https://github.com/kurtosis-tech/kurtosis) from 1.4.1 to 1.4.2.
- [Release notes](https://github.com/kurtosis-tech/kurtosis/releases)
- [Changelog](https://github.com/kurtosis-tech/kurtosis/blob/main/CHANGELOG.md)
- [Commits](https://github.com/kurtosis-tech/kurtosis/compare/1.4.1...1.4.2)

---
updated-dependencies:
- dependency-name: github.com/kurtosis-tech/kurtosis/api/golang
  dependency-type: direct:production
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* improve dispute game tests and coverage

* fixes

* improve optimismportal(2) test coverage

* improve optimismportal(2) test coverage

* more tests, fixes

* contracts: remove op-nft

Remove the `op-nft` package from the contracts package. None of these
contracts are maintained and can be moved to another repo if necessary.
The purpose of this commit is to reduce compilation time. Less files
to compile means less compilation time.

* fix: semver lock step - ran pre-pr.

* fix: use added/modified filter for heavy fuzz

Updates the heavy fuzz filter for CI to only check for added or
modified contracts, now excluding deleted or moved contracts.

---------
Co-authored-by: Blaine Malone <blainemalone01@gmail.com>
Co-authored-by: Kelvin Fichter <kelvinfichter@gmail.com>

Bumps ethereum/client-go from v1.14.11 to v1.14.12.

---
updated-dependencies:
- dependency-name: ethereum/client-go
  dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* improve universal and libraries tests and coverage

* fixes

* improve delayedWeth test and coverage

* improve delayedWeth test and coverage

* fix DataAvailabilityChallenge failing fuzz test

* feat(ctb): `RISCV.sol`

semver-lock
Co-Authored-By: Minhyuk Kim <kimminhyuk1004@gmail.com>
Co-Authored-By: Taem Park <wwwee98@gmail.com>
Co-Authored-By: Park Changwan <pcw109550@gmail.com>
Co-Authored-By: protolambda <proto@protolambda.com>

* snapshots

* diff with remote in CI

* schedule diff job

* Update .circleci/config.yml
Co-authored-by: Matt Solomon <matt@mattsolomon.dev>

* remove check changed

---------
Co-authored-by: Minhyuk Kim <kimminhyuk1004@gmail.com>
Co-authored-by: Taem Park <wwwee98@gmail.com>
Co-authored-by: Park Changwan <pcw109550@gmail.com>
Co-authored-by: protolambda <proto@protolambda.com>
Co-authored-by: Matt Solomon <matt@mattsolomon.dev>

* migrate close-stale github action

* using external script

* completing script

* removing old github action

* example only

* removing versions

* removing tag-service