Rollup misc doc and infrastructure tweaks (#58573)

This rolls up a couple of bug fixes with some tweaks to documentation
and AGENTS.md that came in useful getting the AI to do #58572.

Author: Keno

.gitignore

@@ -13,6 +13,7 @@
 /source-dist.tmp1
 /test/results_*.json
 /test/results_*.dat
+/test/deps
 
 *.expmap
 *.exe

AGENTS.md

@@ -19,7 +19,7 @@ will not be reflected, unless you use `Revise`.
 
 ## For all changes
 
-1. Run `make test-whitespace` before creating the PR to make sure you're not committing any whitespace errors.
+1. Run `make check-whitespace` before creating the PR to make sure you're not committing any whitespace errors.
 
 ## Building Julia
 
@@ -47,8 +47,18 @@ Do not terminate the doctests before completion. If you are ChatGPT, you may hav
 
 If you have changed a test (e.g. `foo`), you should run `make test-revise-foo` for the
 corresponding test to ensure that the test is still passing with your changes.
-If you are adding a new test, add it to an existing test file. Do not
-create a new test file unless explicitly instructed.
+- If you are adding a new test, add it to an existing test file. Do not create a new test file unless explicitly instructed.
+- Write one comment at the top of the test to explain what is being tested.
+  Otherwise keep comments minimal.
+
+### Writing code
+After writing code, look up the docstring for each function you used. If there
+are recommendations or additional considerations that apply to these functions,
+make sure to take them into account.
+
+#### Specific instructions
+- Do not `ccall` runtime C functions directly if there are existing wrappers for the function.
+- Do not explicitly add a module prefix if the code you're adding is in the same module. E.g. do not use `Base.` for code in Base unless required.
 
 ## Commit message formatting
 
@@ -58,3 +68,8 @@ of the purpose of the changes made. Do not specifically mention added tests, com
 documentation, etc., unless this is the main purpose of the change. Do not mention
 the test plan, unless it differs from what you were instructed to do in AGENTS.md.
 If your change fixes one or more issues, use the syntax "Fixes #" at the end of the commit message, but do not include it in the title.
+
+When creating pull requests, if the pull request consists of one commit only,
+use the body of the commit for the body of the pull request. If there are multiple
+commits in the pull request, follow the same guidelines for the pull request
+as for the commit body.

base/runtime_internals.jl

@@ -1306,8 +1306,14 @@ max_world(m::Core.CodeInfo) = m.max_world
 """
     get_world_counter()
 
-Returns the current maximum world-age counter. This counter is global and monotonically
+Returns the current maximum world-age counter. This counter is monotonically
 increasing.
+
+!!! warning
+    This counter is global and may change at any time between invocations.
+    In general, most reflection functions operate on the current task's world
+    age, rather than the global maximum world age. See [`tls_world_age`](@ref)
+    as well as the [manual chapter of world age](@ref man-world-age).
 """
 get_world_counter() = ccall(:jl_get_world_counter, UInt, ())
 

doc/src/manual/worldage.md

@@ -1,4 +1,4 @@
-# The World Age mechanism
+# [The World Age mechanism](@id man-world-age)
 
 !!! note
     World age is an advanced concept. For the vast majority of Julia users, the world age

test/Makefile

@@ -35,7 +35,7 @@ $(TESTS):
 	$(call PRINT_JULIA, $(call spawn,$(JULIA_EXECUTABLE)) $(TEST_JULIA_OPTIONS) ./runtests.jl $(TEST_SCRIPT_OPTIONS) $@)
 
 install-revise-deps:
-	$(call PRINT_JULIA, $(call spawn,$(JULIA_EXECUTABLE)) $(TEST_JULIA_OPTIONS) ./runtests.jl $(TEST_SCRIPT_OPTIONS) --revise)
+	$(call PRINT_JULIA, $(call spawn,$(JULIA_EXECUTABLE)) $(TEST_JULIA_OPTIONS) ./runtests.jl $(TEST_SCRIPT_OPTIONS) --revise --help-list install_revise_deps)
 
 $(addprefix revise-, $(TESTS)): revise-% :
 	@cd $(SRCDIR) && \