context documentation has unclear description about properties that are or are not always present

[kbinreallife]

Problem

The context object documentation is not explicit about WHICH properties are always present, which properties are not.

Context

is_scriptor is either present && true, or does not exist
is_brain is either present && true, or does not exist
calling_script is ALWAYS present, bool
...

[matr1x-hackmud]

calling_script is always present, either null or a string with the script name that called your script

[Fayti1703]

The documentation already has two lists; one for properties that are always present:

hackmud_wiki/docs/scripting/syntax/context.mdx

Lines 9 to 15 in 2041f28

	The context object always contains the following keys:
	- `caller`: the name of the user that initiated this script execution, as a string.
	- `calling_script`: the full name of the script that called this script, as a string. This is only filled if the script was called via [[subscript]]. If the script was called from the CLI or via scriptor, this value is (( %Vnull% )) instead.
	- `this_script`: the full name of this script, as a string.
	- `cols`: the width of the main shell in the client running this script in characters, as a number. If called by automation (such as a [[cron_bot]] execution), (( %V128% )) is used.
	- `rows`: the height of the main shell in the client running this script in characters, as a number. If called by automation, (( %V64% )) is used.

And one for properties that may or may not be present:

hackmud_wiki/docs/scripting/syntax/context.mdx

Lines 17 to 20 in 2041f28

	The following properties may also be present:
	- `is_scriptor`: (( %Vtrue% )) if the script is being run via a scriptor.
	- `is_brain`: (( %Vtrue% )) if the script execution was started by a [[cron_bot]].

I'm not sure how we could make this clearer. Maybe a note below the second list explicitly saying that if the conditions don't apply, the property is absent (and not e.g. false)?