I would also add
1. monitoring support emails and other channels - looking for problems worth solving, very often it is poor documentation
2. creating backlog to capture work for team
3. deepening domain knowledge - IDP, CI, CD, learning about users (engineers) through various publicly available reports on aspect that is an area of exploration like for example
time spent on development
4. data analysis from various metrics tools ie. Google Analytics
Below are less daily more occasionally but still quite frequent
1. presenting and selling products to an internal audience
2. presenting project progress and research results to various audiences
3. teaching engineers about product management practices: vision, strategy, discovery, product risks, customer interviews/validations etc