P: Published Folders renamed does not rename in Finder on macOS Ventura 13.0.1

This bug is still present in LrC 12.3. I used this feature all the time and since at least November 2022 it is no longer working! Please get rid of this bug asap!

This annoying bug, making a consistent use of Published Folders impossible, is still present in LrC 12.2! 

When I follow the recipe with LR 12.0.1:

- On Mac OS 12.6.1, the folder gets renamed in Finder.  Adding photos to the renamed publish-service folder in LR and then publishing causes those photos to appear in the renamed folder.

- On Mac OS 13.0, Windows 10, and Windows 11, the folder doesn't get renamed in Finder / File Explorer.  Adding photos to the renamed publish-service folder in LR and then publishing causes those new photos to appear in the renamed folder in Finder / File Explorer, but the the previously published photos appear in the originally named folder.  Deleting all photos from the publish service and then publishing deletes the photos in the renamed folder in Finder / File Explorer but not in the originally named folder.

If the behavior on Mac OS 13 and Windows is "as designed", it would be good to get a design rationale.

Some additional information:

1. The strange "behaviour" only seems to occur when newly-created Hard Drive Published Folders are involved. Newly-created meaning after installation of macOS Ventura or perhaps (I'm unable to test or confirm this) with the latest version of LrC running on any previous macOS. I have been able to successfully rename older Hard Drive Published Folders (older = created before installing macOS Ventura) without LrC creating a new folder in Finder with the new name whilst leaving the old folder in Finder unchanged and containing all the photos of that old folder in place, whilst the new folder with the new name stays empty until all photos are republished.
2. In my case, LrC has no issues renaming photo folders listed in its Folder panel of the Library module, but there is a difference (and that's why I said: "in my case"), as I have those Library photo folders on an external drive (HFS+ formatted) whilst the Hard Drive Published Folders are on my internal Fusion Drive (APFS formatted). I can therefore not really confirm there is no issue in the Folder panel of the Library module as there are two different drives involved.

Having "coded" myself in the Pleistocene of computers and software, I always give credit to software engineers and know that one piece of software created by one software engineer usually works fine by itself, until some other piece of software or upgraded operating system was changed "fot the better" by some other software engineer and makes the first piece of software misbehave. 🙂 

When I worked for Support at WordPerfect, there were basically only 3 files that could cause problems for the user. It usually only took a few minutes to find the culprit and solve the problem, unless it was some problem related to printer drivers (or a computer catching fire - no joke, it actually happened). Nowadays, well over 500 processes run all at the same time inside the processor and RAM... It's a miracle computers usually still run and do what they are expected to do.  

Would not be the first time Adobe changed something and did not document the change. Would not be the first time Adobe made a very bad decision. Would not be the first time Adobe made a workflow damaging change without customer involvement. And it would not be the first time that some coder fouled up.

I understood that. I just don't understand how changing the essence of the Hard Drive Publishing Service being able to manage folders within Finder, would be something that was done on purpose. If the Library Folder panel can still do the same, why or how would the Hard Drive Publishing Service not be able to do it anymore? The problem started with the upgrade from Monterey to Ventura. I don't suspect LrC to have changed anything about how it manages folders and files in Finder. I suspect macOS Ventura did. 🙂 

I fail to see how the Hard Drive Publish Service would be of any use from now on if such a "behaviour" (which is actually the privilege of living beings, not of machines or software) would be "by design" and introduced in total silence in the latest version of LrC. Logic and experience in IT tells me it's something that has to do with the interaction of LrC and macOS Ventura. But I'm happy it's being investigated. 

"To err is human - to really mess up things, you need a computer." (anonymous quote, hanging above the entrance door of WordPerfect's Support Department some thirty years ago...)

I don't want to sound impolite, but "as-designed behaviour" would mean that I am lying when I say that this started to happen with the latest version of LrC on macOS Ventura 13.0.1 and never happened before. I use this feature very often and it always worked flawlessly. 

By "as designed" The Adobe employee may not be refering to as always designed, but as in current design, as in they intentially changed someting. For example getting rid of the Done button that so many people are mad at. As in, they did something stupid.

Let's review what's happened in the thread so far:

1.  You reported behavior
2. Questions were asked and answered
3.  I can repeat the behavior
4.  A bug was written
5.  Status of the post moved from "No Status" to "Investigating"
6.  I've asked the team to comment on designed behavior so that we are certain that no change in behavior was initiated on the development side that would make this not a bug.  No one is disputing a change in behavior. What is not yet known is: was a deliberate change made?

I am struggling to see how any of  that disparages you but my apologies if you feel that way.