As a UK contractor myself, would you be able to share some tips as to how to give reassurance to the client that you're not doing that? With easy, well-defined

As a UK contractor myself, would you be able to share some tips as to how to give reassurance to the client that you're not doing that? With easy, well-defined tasks it's easy - just do the work and the regular commits prove that you've done the work on time and aren't taking the piss. But in my case I'm sometimes stuck on long-running tasks that involve dealing with lots of legacy technical debt where I have a local branch going for 2 weeks that's a complete mess and doesn't pass CI or where I have to spend lots of time thinking about the solution and trying different approaches before settling on something I'm actually happy to commit and build upon. During that time, from the client's perspective it might look like nothing is happening, so I try to make up for it by taking on smaller, auxiliary tasks which don't take much time but can be completed and pushed to at least show some activity. Before remote you show up in the office and everyone assumes you're working so this wasn't a concern at all.