bug: docs/concepts.md lists build as a public command but codealmanac build is rejected

[Priyanshubhartistm]

What happened?

The command-group table in docs/concepts.md says:

| Lifecycle | `init`, `build`, `ingest`, `garden`, `sync`, `jobs` | ... |

But build is deliberately not a public command — it is an internal run kind that init queues (that design is locked in implementation-tickets.md Ticket 13: "codealmanac build is not public", with a test that the parser rejects it). Running it confirms:

$ codealmanac build
◆ codealmanac

Unknown command
...

Anyone (human or agent) reading concepts.md as the product model will try a command that renders an error screen.

What did you expect?

The Lifecycle row to list only the real public commands: init, ingest, garden, sync, jobs. If it's useful to keep the concept visible, a sentence like "init queues an internal build run" matches the rest of the doc without advertising a fake command.

Reproduction

grep -n '`build`' docs/concepts.md
codealmanac build   # rejected with the Unknown command screen

Environment

• OS: any
• Python version: 3.12
• CodeAlmanac version: 0.3.7
• Install method: local checkout
• Agent provider, if relevant: none
• Almanac root, if relevant: almanac/

Logs or output

$ codealmanac build
◆ codealmanac

Unknown command

You ran:
  codealmanac build

Extra context

almanac/reference/cli/public-command-surface.mdh agree on the real surface; concepts.md is theonly doc out of sync.

[Priyanshubhartistm]

Hii @Adityakk9031 ,I have already created a PR to address this issue. I'm currently waiting for a maintainer's review and approval. Once it's approved then i'll be open a pr