IMO, 2 doesn't need code review by a human anymore. Agents can review each other. I add a broad code audit for DRY, YAGNI, KISS every once in a while and let agents fix the findings.
And for 1, code review was always too low-level. I have agents produce artifacts that are convenient for me to review. Often narrated demo videos, sometimes HTML pages with graphs and tables.
With this, code review is not a bottle neck, and I find myself working not as an engineer anymore but as an engineering director.
If a human spent the upfront effort to create and refine the right abstractions, the code would almost always be easier to reason about, test, and extend for agents. I pretty much never see AI doing this on its own—things like proposing to split the 1400 line class into 5 classes, make major changes to the data model, etc. It will most often just make the existing code a little bit worse to answer your prompts and move along.
So I think that the most valuable time spent when working with agents is to ensure that good abstractions are being created, and often this can involve doing this part by hand and asking it to fill out the skeleton. Then you end up with a better codebase that is easier for both humans and agents to work in.