Fix README & template to match parser

Fix the examples in the template to match the form actually needed by the
parser, and remove the invalid `Proposed` status.

Document the flow for new ADRs starting in `Accepted` status, to reflect that
as soon as they've been merged they are Accepted.

Author: philpennock

.readme.templ

@@ -29,6 +29,8 @@ Please see the [template](adr-template.md). The template body is a guideline. Fe
 
 After editing / adding a ADR please run `go run main.go > README.md` to update the embedded index. This will also validate the header part of your ADR.
 
+Note that new ADRs are written with an initial state of `Accepted`, not `Proposed`, on the basis that once merged to `main` it is immediately Accepted.
+
 ## Related Repositories
 
  * Server [nats-server](https://github.com/nats-io/nats-server)

README.md

@@ -100,6 +100,8 @@ Please see the [template](adr-template.md). The template body is a guideline. Fe
 
 After editing / adding a ADR please run `go run main.go > README.md` to update the embedded index. This will also validate the header part of your ADR.
 
+Note that new ADRs are written with an initial state of `Accepted`, not `Proposed`, on the basis that once merged to `main` it is immediately Accepted.
+
 ## Related Repositories
 
  * Server [nats-server](https://github.com/nats-io/nats-server)

adr-template.md

@@ -4,7 +4,7 @@
 |--------|-----|
 |Date    |YYYY-MM-DD|
 |Author  |@<github user>, @<github user>|
-|Status  |`Proposed`, `Approved` `Partially Implemented`, `Implemented`|
+|Status  |Approved, Partially Implemented, Implemented|
 |Tags    |jetstream, client, server|
 
 ## Context and Problem Statement