Based on public Shuyang Home v1.2.2 source, test fixtures and release records. Existing behavior, recorded checks and proposed tests are distinguished; this update is a source review and write-up.
Find the entry points that depend on paths
Old business names at the source root made the project harder to understand. Renaming the directories to frontend and backend clarifies their purpose, but paths are also an interface shared by scripts, configuration and documentation.
The migration touched startup, preview, tests, versioning and packaging. Updating editor references alone can miss PowerShell scripts, CI working directories and paths assembled in Python.
- List startup scripts, package.json tasks, workflows, packaging scripts and README commands.
- Check whether each path is relative to the repository, the current working directory or the script itself.
- Run the real entry points from the new layout to check that they resolve correctly.
Keep current entry points accurate and historical evidence traceable
A migration inventory records the paths that existed before cleanup. Source links pinned to an older commit must also use paths from that commit; replacing only the directory name can create a 404.
An older working copy may contain ignored data, uploads and environment configuration. Upgrade instructions should help readers identify and migrate these files. A public source cleanup is not permission to overwrite a running application directory.
Working on Windows does not prove a Linux file is executable
After the v1.2.1 directory migration, v1.2.2 restored the executable bit on backend/mvnw. Its content was unchanged, but Git needed mode 100755 rather than 100644 for Linux workflows that invoke ./mvnw.
Windows builds can miss this because they use mvnw.cmd. Reviewing the target platform entry point is necessary in addition to reviewing content diffs.
git ls-files --stage -- backend/mvnw
# Expected mode: 100755
# If the tracked mode is wrong, repair it and review the diff:
git update-index --chmod=+x backend/mvnw
git diff --cached --summaryAttach verification to the version it describes
The release history records Web/mobile type checks, 68 frontend logic checks, 63 backend tests, three builds and verification of 140 packaged files for v1.2.1. Version 1.2.2 repairs file mode and version consistency while referencing those earlier business checks.
The practical lesson is to treat a directory rename as a small migration: it changes both the paths readers follow and the paths machines execute.
Sources & further reading
Compiled from code and documents, with AI-assisted drafting and translation. Examples and proposed checks are learning material; only linked evidence establishes what was run.