railway up uploads the closest linked folder, not the current one
The Railway CLI resolves the linked project by walking up parent directories (get_closest_linked_project_directory in src/config.rs), and railway up with no path archives that linked project's folder, not the current working directory (get_deploy_paths in src/commands/up.rs). So a git worktree or subfolder nested inside an already-linked checkout uploads the parent checkout unless you run railway link inside it first, and railway status looks identical either way because it shows the inherited link. To deploy an exact folder regardless of where the link lives, use railway up <folder> --path-as-root.
Confirmed against railwayapp/cli master today: get_deploy_paths uses the path for both project_path and archive_prefix_path when --path-as-root is set. Extra caveat for worktrees: create_deploy_tarball honours .railwayignore, .gitignore and the global gitignore, includes hidden files, and hard-skips only .git and node_modules; it never reads .git/info/exclude, so anything ignored only there (common in worktrees, whose .git is a file) gets uploaded.