developlisted

develop is the operator for people who run their own copy of an open-source project and want to keep developing it. **You do this work with judgment** -- every project's build, test loop, and hosting differ, and adapting to them is the job. The scripts below are tested reference builds for the exact, safe git mechanics; use them when they fit, adapt or regenerate them when they do not (build-rule 1). What is yours is the understanding: reading an unfamiliar codebase, deciding fork vs separate tree, resolving a real merge conflict, judging whether a change is worth upstreaming. ## Understand how to iterate and test Read the project the way a new contributor would: its README, CONTRIBUTING, Makefile, CI config, and test files. Learn how it is built, how it is tested, and where the contribution path is, in the project's own terms. `guide.py <repo>` gives you a first harvest of that from ground truth (test commands, targets, CONTRIBUTING, CI) -- a starting point you refine by reading, not a substitute for reading. ## Own the tree: fork or keep it separate Decide with the user which they want, then set the remotes up. `tree.py adopt` does it safely (fork: origin = your fork, upstream = original; or separate: your own origin, upstream tracked). Fork when they mean to contribute back; separate tree when they mean to diverge privately. ## Pull from upstream, then verify `tree.py pull-upstream` fetches upstream and integrates it, reporting clean or conflict and leaving a conflic