The team layer's package manifests are set aside until the manifest fixes land, and its project directory becomes common - #821

Thread 3 detour, pushed from DANOBLE-WD11-3, where the first real writ deploy noblefactor found the manifest path broken four ways.

What changes

• The five Home/noblefactor*/packages-manifest.yaml files are removed. Their entries cannot be planned today: pwsh is a winget moniker where the driver needs an id (The team layer's Windows packages-manifest.yaml names pwsh, a winget moniker, where the driver needs the id Microsoft.PowerShell #818, driver side winget driver: names are ids only, so a moniker such as pwsh never resolves, and the failure quotes stderr while winget reports on stdout #817), the personal layer's purl form is refused by pkg (pkg.Resource rejects the canonical purl form its doc promises: "pkg:winget/Vim/Vim?scope=machine" fails as unknown package manager "pkg" #813), and the files collide with one another instead of combining (packages-manifest.yaml files collide like deployed files: the most specific one shadows the rest, so a layer's general packages are never planned #814).
• Home/common/packages-manifest.yaml is added with packages: [] — the one manifest form the current build plans as nothing (A zero-byte packages-manifest.yaml is refused as 'missing required field: packages'; a missing key, an empty file, and packages: [] must all mean no packages #820 rules that a missing key, an empty file, and packages: [] are equivalent; the build on the machine accepts only the last). It also keeps a tracked file under Home/, without which the layer fails the tree build instead of contributing nothing (A layer is admitted by its clone's working tree but planned from a HEAD snapshot: an emptied Home/ fails the tree build instead of contributing nothing #819).
• The team project directory is renamed from noblefactor to common, matching the personal repository's layout. writ deploy noblefactor selects by project name, so what the team layer contributes under that command is the next thing the Windows test measures.

Acceptance

• the branch carries exactly the six file changes above (compare against develop: ahead 3, behind 0)
• writ deploy noblefactor on DANOBLE-WD11-3 got past the tree build with the team clone at this branch (it then stopped at file.mkdir-6, file.mkdir ignores --conflict: anything that is not a directory at its path fails the deploy under every policy, while file.link and file.copy replace it #822)
• the suite passes on all five platforms — every test leg green on this PR

References #813, #814, #817, #818, #819, #820. Closes nothing: the manifests return when those land.

https://claude.ai/code/session_01SqQVFZz7AdiLZkGoAcUqRW