command-line-interface: Drop the 'version' command

This was added in ffa124c (Add a 'version' command, 2015-09-14) to
make it easy for callers to report which runtime they were using.  But
we don't have a use-case that makes it strictly necessary for interop,
so we're leaving it out for now [1].

[1]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2016/opencontainers.2016-07-20-21.03.log.html#l-75

Signed-off-by: W. Trevor King <[email protected]>

Author: wking

command-line-interface.md

@@ -18,33 +18,10 @@ If the runtime is invoked with an unrecognized command, it MUST exit with a nonz
 ## Character encodings
 
 This API specification does not cover character encodings, but runtimes SHOULD conform to their native operating system.
-For example, POSIX systems define [`LANG` and related environment variables][posix-lang] for [declaring][posix-locale-encoding] [locale-specific character encodings][posix-encoding], so a runtime in an `en_US.UTF-8` locale SHOULD write its [version](#version) to stdout in [UTF-8][].
+For example, POSIX systems define [`LANG` and related environment variables][posix-lang] for [declaring][posix-locale-encoding] [locale-specific character encodings][posix-encoding], so a runtime in an `en_US.UTF-8` locale SHOULD write its [state](#state) to stdout in [UTF-8][].
 
 ## Commands
 
-### version
-
-Print the runtime version and exit.
-
-* *Options* None are required, but the runtime MAY support options.
-* *Standard streams*
-    * *stdin:* The runtime MUST NOT attempt to read from its stdin.
-    * *stdout:* The runtime MUST print its name, a space, and its version as the first line to its stdout.
-      The name MAY contain any Unicode characters, but MUST NOT contain control codes or newlines.
-      The runtime MAY print additional lines to its stdout, and the format for those lines is not specified in this document.
-    * *stderr:* The runtime MAY print diagnostic messages to stderr, and the format for those lines is not specified in this document.
-* *Exit code:* The runtime MUST exit with zero.
-
-#### Example
-
-```
-$ funC version
-funC 1.0.0
-Built for x86_64-pc-linux-gnu
-$ echo $?
-0
-```
-
 ### create
 
 [Create][create] a container from a [bundle directory][bundle].
@@ -89,7 +66,7 @@ If you call `start` from a shell using a separate terminal, the container output
 
 #### Container process exit
 
-The [example's](#example-1) `block-on-exit-and-collect-exit-code` is platform-specific magic that is not specified in this document.
+The [example's](#example) `block-on-exit-and-collect-exit-code` is platform-specific magic that is not specified in this document.
 On Linux, it might involve an ancestor process which had set [`PR_SET_CHILD_SUBREAPER`][prctl.2] and collected the container PID [from the state][state], or a process that was [ptracing][ptrace.2] the container process for [`exit_group`][exit_group.2], although both of those race against the container process exiting before the watcher is monitoring.
 
 ### start
@@ -105,7 +82,7 @@ This command SHOULD exit as quickly as possible after triggering the execution,
     * *stderr:* The runtime MAY print diagnostic messages to stderr, and the format for those lines is not specified in this document.
 * *Exit code:* Zero if the container was successfully started and non-zero on errors.
 
-See [create](#example-1) for an example.
+See [create](#example) for an example.
 
 ### state
 
@@ -184,7 +161,7 @@ $ echo $?
     * *stderr:* The runtime MAY print diagnostic messages to stderr, and the format for those lines is not specified in this document.
 * *Exit code:* Zero if the container was successfully deleted and non-zero on errors.
 
-See [create](#example-1) for an example.
+See [create](#example) for an example.
 
 [bundle]: bundle.md
 [create]: runtime.md#create